Winfax sharing on WinXP - my new contribution to the solution log
hocke...@gmail.com
know if it's still alive. So, here's a repost:
I've been all over hell's half-acre figuring out how to get my
existing
WinXP client to talk to the new WinXP fax server (was Win2k), when
both
were 10.03. <br>
<br>
I first upgraded both machines to 10.04, and performed the steps from
Symantec at
http://service1.symantec.com/SUPPORT/faxprod.nsf/docid/2004071911425704?Open&src=_w&docid=2004113014595304&nsf=faxprod.nsf&view=docid.<br>
<br>
After doing this DCOM/COM permissions thing, I was still getting an
error from the client that said "winfax server process could not be
started because the configured identity is incorrect". Ah, ok - user
accounts? Hrm. I *think* I got past this error by just double-checking
that I had the DCOM things above (all 5 steps) all right on the
server.<br>
<br>
THEN the error changed to:"The server process could not be started".
Hrm. Now what do to?<br>
<br>
REVIEW THE LOGS! The Server log said:<br>
"The application-specific permission settings do not grant Remote
Activation permission for the COM Server application with CLSID
{DA4E5220-FE02-11D0-BD2E-00805F98AB78}".<br>
<br>
Looking up this CLSID pointed to a "Winfax.HostControl", but with
further searching in the registry, repoints to "WinFax.Attachment"
entry, which in itself has a different CLSID
17EAB2A0-70E2-11CE-A7FB-008029E0ABE9. Now we're getting somewhere.<br>
<br>
The final step to ALLOWING "application-specific permission" to this
CLSID was to go back to the Symantec modification steps, and do:
Component Services / Computers / My Computer / DCOM Config /
WinFax.Attachment (right-click / Properties) / General /
AUTHENTICATION
LEVEL: NONE (down from "Default".<br>
<br>
My Security Permissions (2 tabs over) have "Launch and Activation
Permissions as "Anonymous logon" account with ticks only on
"remote Launch" and "Remote Activation". (I may not need "Remote
Launch" ticked)<br>
<br>
My "Access Permissions" have "Anonymous Logon" with only "Remote
Access" ticked.<br>
<br>
NOTE that I do not have any special logon accounts set up, other than
having a few shares with "Everyone" on the server that my client taps
occasionally. Relevant? Dunno. I DO NOT have my client Winfax Pro
service running under a different account.<br>
<br>
My KEY POINT here is that turning the AUTHENTICATION LEVEL: NONE (down
from "Default") was THE FINAL STEP for my install. <br>
<br>
Hope this helps somebody else... I blew ~6 hours on this, so if I can
help somebody else avoid this problem, my karma will recharge!<br>
<br>
<hr size="2" width="100%">Another tip:<br>
<br>
Faxtalk is coming out with a client/server of their Winfax Pro clone
in
'09. GOOD NEWS. <br>
<br>
I've also loaded up hylafax (cool-works well) on my linux server,
tried
most of the major commerical clients, and found that Cypheus works
decently; HylaFAX-client was a bit buggy, but the email-this-fax-to
feature works nice, and Hyfax was ok. Did not try the mysql supported
features, but generally, I think I'd take Cypheus out of the lot.
Major
criticism of the lot is there's no convenient way to sort/archive the
faxes in a meaningful way. We use Winfax folder to sort by suppliers.
That's why I am looking forward to ditching unsupported WINFAX PRO for
FAXTALK as soon as it's out!
Jd
windows xp on both the host and client, that was the purpose of the 10.04
update. something else was probably messed up. my host/client works with
10.03 (xp sp3) without having to set any authentication level to none.
Support from symantec is non-existant but the getfaxing.com site has support
forum and support services for winfax which may be of help,
<hocke...@gmail.com> wrote in message
news:6272be42-88ee-480a...@z1g2000yqn.googlegroups.com...
