Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

After you install the ISA Server 2004 Firewall Client program on a Windows 98-based computer, the Firewall Client program may stop responding, or Winsock programs may unexpectedly quit


View products that this article applies to.

Symptoms

After you install and configure the Microsoft ISA Server 2004 Firewall Client program on a Microsoft Windows 98-based computer, you may experience one or more of the following symptoms:
The Firewall Client program stops responding.
Winsock programs unexpectedly quit.
Winsock programs stop responding for about two or three minutes and then lose network connectivity.

↑ Back to the top


Cause

This problem occurs if the following conditions are true:
You configure a user-based policy. For example, you create an access rule that applies to a user set.
You add a user who uses the Windows 98-based computer to that user-based policy.
In this scenario, when ISA Server 2004 requires client authentication, the Firewall Client that is running on the Windows 98-based computer may cause Winsock programs to quit. Additionally, the Firewall Client program may not successfully authenticate.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, follow these steps:
1.Install ISA Server 2004 Service Pack 1 (SP1) on the computer that is running ISA Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
891024 How to obtain the latest ISA Server 2004 service pack
2.Reinstall the ISA Server Firewall Client program on any computers that are running Windows 98.
3.Configure ISA Server 2004 to permit non-encrypted Firewall Client connections. To do this, follow these steps:
a. Start the ISA Server Management program.
b. In the left pane, expand Servername.

Note Servername is the name of the computer that is running ISA Server 2004.
c. Expand Configuration, and then click General.
d. Under ISA Server Administration, click Define Firewall Client Settings.
e. On the Connection tab, click to select the Allow non-encrypted Firewall client connections check box, and then click OK.
4.Click Apply to apply your changes to the firewall configuration, and then click OK.

↑ Back to the top


Workaround

To work around this problem, configure your access rules to permit unauthenticated access for the users who run the Firewall Client program on Windows 98-based computers. For more information about how to create an access rule, see the Access rules topic in ISA Server 2004 Help.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about ISA Server 2004, visit the following Microsoft Web sites:

↑ Back to the top


Keywords: kbdeployment, kbbug, kbfix, kbqfe, kbwinserv2003presp1fix, kbpubtypekc, kbfirewall, KB893171

↑ Back to the top

Article Info
Article ID : 893171
Revision : 3
Created on : 7/24/2006
Published on : 7/24/2006
Exists online : False
Views : 397