The information in this article applies to:
SYMPTOMSSNA Server clients are unable to get application sessions on SNA Servers configured through the OtherServers registry parameter when the Firewall registry entry is also configured on the client. The OtherServers registry entry is ignored if the Firewall entry is present. CAUSEThe OtherServers and Firewall registry entries are designed to be mutually exclusive. RESOLUTIONAn update is available that allows the Firewall parameter to be ignored when the client is trying to connect to a SNA Server defined in the OtherServers parameter. SNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:Q184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack SNA Server 4.0This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 2.11 SP1, 2.1 SP2, 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 4.0, and 4.0 SP1. This problem was first corrected in SNA Server 3.0 Service Pack 4. MORE INFORMATION
In addition to the hotfix, a registry parameter has to be added to
allow the Firewall parameter to be ignored. To add the registry value,
perform the following steps:
SNA Server Client for Windows NT
SNA Server Client for Windows 95
Q139508 Internet Firewall Support in SNA Server For additional information regarding the SNA Server OtherServers subkey, please see the online Help files. Additional query words:
Keywords : |
Last Reviewed: July 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |