[highlysceptical]

@JohnD wrote:

Version 10 will indeed work with XP. However, I am not sure how you are getting a 10.00 Host to work with 9.03 clients. I haven’t tried this before but under normal conditions it shouldn’t allow it.

Well, as I said, it most certainly does work. All I have done is to :-

apply the changes to the firewall, DCOM Config etc. as per the Symantec guidance
granted user permissions to HKLM/Microsoft/Windows NT/CurrentVersion/Print on the host
granted user permissions to HKLM/Microsoft/Windows NT/CurrentVersion/Winfax Ports on the host
granted user permissions to HKLM/Microsoft/Windows NT/CurrentVersion/Winfax Ports (Photo Quality) on the host
granted user permissions to c:windows on the host

And thanks for the additional information.

[highlysceptical]

To save anyone wasting any time on this, I have solved it myself!

From the Events log, I followed the link to Microsoft’s Help and Support and followed the instructions – which were basically the same as before.

In DCOM Config, I gave full rights to Anonymous Logon (Winfax.Attachment item), and then tried connecting again – it worked!

I then removed the rights one by one until just Remote Activation remained (which was how it was set before I started), and it still worked!

Just for reference, I would mention that my configuration is Winfax 10.0 on the Windows XP host (not 10.02, 10.03 or 10.04 – 10.0 was not supposed to work on Windows XP, but it most certainly does!), with Winfax 9.03 on the clients.

I hope this information helps someone else.

[highlysceptical]

Following on from my previous post, I have just tried resetting Winfax Fax Sharing on one of the problem clients and this generated the following error in the Events Log

The machine-default permission settings do not grant Remote Activation permission for the COM Server application with CLSID
{DA4E5220-FE02-11D0-BD2E-00805F98AB78}
to the user NT AUTHORITYANONYMOUS LOGON SID (S-1-5-7). This security permission can be modified using the Component Services administrative tool.

Since I have just reset the Anonymous Logon rights to the Winfax attachment in DCOM Config, how can this possibly be? Do the “machine-default permission settings” override the changes I have made? If so, can I change the “machine-default permissions”, whatever they are?

[highlysceptical]

@Pilot wrote:

The system was working fine until we came to work this morning and none of the clients were able to connect to the host. The host does not have any problems because it is receiving faxes as it normally does. I ran antivirus and antispyware scans but that didn’t help.

The exact error message is :Winfax Pro is unable to connect to the Winfax PRo Host station called (Host Station Name). Make sure an account has been created for you on the host station (using the same name/password used to login to your client station).

I have virtually exactly the same problem, except that in my case, fax sharing still works if, but only if, the client is a member of Administrators on the host computer (running XP Pro).

I also have loads of DCOM errors in the Events log saying

The launch and activation security descriptor for the COM Server application with CLSID
{17EAB2A0-70E2-11CE-A7FB-008029E0ABE9}
is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool.

I have tried removing and re-adding Anonymous Logon rights to the winfax attachment but it has not made any difference.

Can you suggest anything else? I have spent hours trying to puzzle out what has gone wrong, but to no avail so far!

Thanks,

[Author]

Posts