- This topic is empty.
-
AuthorPosts
-
November 16, 2004 at 2:28 pm #3512
Anonymous
MemberHas anybody got winfax to work with XP sp2?
I have the Host set up on a 2000 pro machine, and after the sp2 update they won’t connect.
Joe
November 16, 2004 at 3:22 pm #7048Anonymous
Member@JoeJones wrote:
Has anybody got winfax to work with XP sp2?
I have the Host set up on a 2000 pro machine, and after the sp2 update they won’t connect.
Joe
The problem is the firewall built into XP2, it won’t allow the host to communicate with the client and vice versa.
Reconfiguring Windows XP security settings
To enable Fax Sharing, perform the following steps at the host computer, and then repeat sections 1-4 at the client computer. Do all of the sections in the order given.
Section 1: To ensure that the Windows Firewall is enabled
At the host computer, log on as a user with Administrative privileges. If you already performed sections 1-7 at the host computer, logon at the client computer instead.
From the Start menu, click Settings > Control Panel.
If using the Classic View, double-click Windows Firewall. Otherwise, click Security Center and then, in the “Manage security settings for:” section, click Windows Firewall.
Select On (recommended).Section 2: 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.
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.Section 3: To enable Remote Administration traffic through the Firewall by enabling RPC and DCOM
From the Start menu, select All Programs > Accessories > Command Prompt.
Type netsh
Type firewall
If the host and client are on the same subnet, type:
set service REMOTEADMIN ENABLE SUBNETotherwise, type:
set service REMOTEADMIN ENABLE ALLType show service and verify that Remote Administration is enabled.
Type exit and then type exit again.Section 4: To enable machine wide, remote access to COM for Anonymous Logon users
From the Start menu, click Settings > Control Panel.
If using the Classic View, double-click Administrative Tools. Otherwise, click Performance and Maintenance, and then double-click Administrative Tools.
Double-click Component Services.
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 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, and then click OK again.
Close the Component Services window and the Administrative Tools window.
If you are performing these steps at the host computer, continue with section 5. Otherwise, go to section 7.Section 5: To enable Anonymous Logon users to have machine wide, remote activation access to COM
From the Start menu, click Settings > Control Panel.
If using the Classic View, double-click Administrative Tools. Otherwise, click Performance and Maintenance and then double-click Administrative Tools.
Double-click Component Services.
From the Console Root, open Component Services > Computers > My Computer.
Right-click My Computer, and click Properties. This step opens the My Computer Properties dialog box.
Click the COM Security tab.
In the Launch and Activation Permissions group, select Edit Limits. .
In the Launch Permission dialog box, click Add, type ANONYMOUS LOGON and click OK.
Select ANONYMOUS LOGON, and select Allow on the “Remote Activation” entry. All other boxes should be deselected.
Click OK, and then click OK again.
Close the Component Services window and the Administrative Tools window.
Restart the computer.
Section 6: To enable Anonymous Logon users to have remote activation access to the WinFax.Attachment DCOM component
From the Start menu, click Settings > Control Panel.
If using the Classic View, double-click Administrative Tools. Otherwise, click Performance and Maintenance, and then double-click Administrative Tools.
Double-click Component Services.
From the Console Root, open Component Services > Computers > My Computer > 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.
Close the Component Services window and the Administrative Tools window.Section 7: Apply the changes
Restart the computer.If you are performing these steps at the host computer, repeat sections 1-4 at the client computer. Otherwise, stop here. You have completed all the steps. Fax Sharing should now work between the client and host.
Technical Information:
Explanation of specific SP2 changes and their effect on WinFax Fax Sharing
The Fax Sharing client cannot connect to the host because the SP2 installation turns on Network Protection Technologies, which prevent the client and host from communicating with each other. To solve this problem, the procedure in this document configures those technologies to permit WinFax communications. The procedure adds WinFax to the Windows Firewall Exceptions list of “Programs and services,” configures the firewall to permit ICMP echo requests, and configures the firewall to permit remote administration.SP2 also changes Windows DCOM. These changes prevent a program on a remote computer from communicating with the same program on a local computer unless the communication uses an authentication protocol. WinFax does not use an authentication protocol. To solve this problem, the procedure in this document disables the DCOM changes that cause this problem.
For a detailed explanation of how the SP2 changes affect your computer’s security, go to the Security Enhancements in Microsoft Windows XP Service Pack 2, article number 832490 Web page
Edited By Moderator on Nov. 16 2004 at 10:22
February 28, 2005 at 6:00 am #7049Anonymous
Memberhttp://service1.symantec.com/SUPPORT….4595304
Please see this Symantec document for more details on update 10.04
-
AuthorPosts
- You must be logged in to reply to this topic.