The information in this article applies to:
SYMPTOMSAfter upgrading an SNA Server 2.11 Windows NT or Windows 95 client workstation (attached via Netware IPX/SPX) to SNA Server 3.0, 3.0 Service Pack 1 (SP1) or SP2, the workstation may fail to obtain a sponsor connection to an SNA Server. CAUSEAn SNA Server 3.0 Windows NT or Windows 95 client may issue a Get General Server query in an attempt to locate a sponsor SNA server. When the client workstation receives the query reply, it will attempt to contact the first server in the list that is provided. The client will then create an IPX connection to the remote server and query the bindery for the address of the sponsor server. In certain situations, possibly due to SAP filtering strategies, the remote bindery based server will not have the IPX address and SAP type (0x444) registered for the intended SNA Server and the connection attempt will fail. STATUS
A correction has been made to the SNA Server client IPX interface
(SNANCP.DLL) which forces the SNA IPX client to query with a Get Nearest
Server request first before attempting to use a Get General Server query.
S E R V P A C KThis problem is fixed in the original retail release of SNA Server 4.0. MORE INFORMATIONWith this SNA Server client update applied, the following registry entry can be used to force the client to use only Get General Server queries if required. It also works with SNA Server version 4.0. For Windows NT Clients
For Windows 95 Clients
Additional query words:
Keywords : prodsna kbbug3.00 kbbug3.00.sp2 kbfix3.00.sp3 kbbug3.00.sp1 snabaseservice snawin95 snawinnt |
Last Reviewed: September 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |