Winfax and Windows XP SP2
Last Updated: 2/15/10Windows XP Service Pack 2 (SP2) was released by Microsoft recently to increase the security of the Windows XP operating system. Due to alot of changes made by SP2 to Windows alot of programs ceased to function properly. One of those programs was Symantec's Winfax. Winfax uses DCOM
(Distributed Component Object Model) which is one of the areas of Windows XP where Microsoft added additional security. What seems to have caused problems with winfax is this security increase in the DCOM area of Windows. This page will hopefully give you insight and a possible solution into the conflicts of Winfax and SP2. The conflict normally only occurs on Windows XP SP2 machines that are not on a domain.
Install Update
First of all, install the update from Symantec. It should bring your Winfax software up to version 10.04 or higher. This may fix your problem and prevent you from having to read this page. To get the update first run LiveUpdate to get version 10.03 then download the update from this page: Winfax Update 10.04
Be sure to follow the instructions carefully. You will have to write down a password from Symantec in order to extract the update from the zip file. If the update doesn't fix your problem then read the rest of this page.
Step 1: Configuring the Windows Firewall
To add the WinFax Controller program to the Windows Firewall Exceptions list.
On the Exceptions tab, click Add Program.
Select Controller. The "Path:" box displays a path that ends in Wfxctl32.exe.
or browse to the install location for winfax (i.e. C:\Program Files\Winfax) and select "Wfxctl32.exe"
If the host and client are on the same network (subnet), click Change scope and select My network (subnet) only.
Click OK, and then click OK again.
In the Programs and Services list, ensure that the box next to Controller is selected.
Click OK, and close the Windows Control Panel.
Step 2: Enable Remote Administration traffic through the Firewall
Go to Start Menu > Run > Type "cmd" > Type "netsh" > Type "firewall"
If the host and client are on the same subnet, type:
set service REMOTEADMIN ENABLE SUBNET
otherwise, type:
set service REMOTEADMIN ENABLE ALL
Type show service and verify that Remote Administration is enabled.
Type exit and then type exit again.
Step 3: Configuring DCOM
Start Menu > Run > Type "dcomcnfg"
From the Console Root, open Component Services > Computers > My Computer.
If you see a Security Alert dialog box, click Keep blocking.
Right-click My Computer, and click Properties.
In the My Computer Properties dialog box, on the "Default COM Security" tab, in the Access Permissions group, click Edit Limits.
In the Access Permission dialog box, choose ANONYMOUS LOGON, and select Allow on the "Remote Access" entry. Click OK
in the Launch Permissions group, click Edit Limits.
In the Launch Permission dialog box, choose ANONYMOUS LOGON (add it if it's not on the list), and select Allow on the "Launch Permissions" entry. Click OK
Then click OK again.
Step 4: Configuring WinFax.Attachment in DCOM
You should still see the Component Services screen. Double click on "My Computer" and then on "DCOM Config". From the menu, click View > Detail.
From the DCOM Config list, right-click WinFax.Attachment, and click Properties.
On the Security tab, in the Launch and Activation Permissions group, select Customize, and click Edit.
Click Add, type ANONYMOUS LOGON and click OK.
Choose ANONYMOUS LOGON, and select Allow on the Remote Activation entry. All other boxes should be deselected.
Click OK, and then click OK again.
Step 5: Final Instructions
All the instructions above should be applied to all computers. It may not be necessary to apply them to all computers, but it is thorough. Make sure that all computers are on the same workgroup and that all computers have file sharing enabled. I would share at least one folder on each computer to verify that file sharing is enabled. Check that you can see the shared folders on all the comptuers. To check go to Start Menu > Run > Type "\\PcName" where PcName is the name of the computer you want to view. If a window pops up with a list of shares on that computer then file sharing is properly enabled. You may also need to create a user on the host computer for each client. The new user must match the username and password of the client's currently logged in username and password. The users created must have administrator rights. Be sure to restart all computers have making these changes.
If you have trouble after following my steps please see below:
Optional Final Step: More DCOM Config
This step may also be needed to get winfax working.
Start Menu > Run > Type "dcomcnfg"
From the Console Root, open Component Services > Computers > My Computer.
Right-click My Computer, and click Properties.
In the My Computer Properties dialog box, on the "Default Properties " tab, make sure the box "Enable Distributed COM on this computer" is checked. Then set the "Default Authentication Level" box to "None" and the "Default Impersonation Level" to "Anonymous". Then click ok and restart. You may have to do this on all computers.
Registry Tweak That May Be Required
Cut and paste the following (between the lines) into notepad and save as something like RPC_ON.REG. Double click to activate file:
------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows NT\\RPC] \"EnableAuthEpResolution\"=dword:00000001
\"RestrictRemoteClients\"=dword:00000000
Re-boot the computer and good luck!
To Reverse the RPC changes later, if needed, use the following in a registry file called RPC_OFF.REG
--------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows NT\\RPC] \"EnableAuthEpResolution\"=dword:00000000
\"RestrictRemoteClients\"=dword:00000001
For more details and info regarding this issue please download the email I recieved from Mikey by clicking below
Email from Mikey
Sources of this page:
Salvage BV Support Page
Symantec's Page on SP2 and Winfax
If all else fails consider alternatives:
Impact ColorFax
