Article ID: 214430
Article Last Modified on 9/22/2005
APPLIES TO
- Microsoft SNA Server 4.0
This article was previously published under Q214430
SYMPTOMS
If an SNA Server Windows NT client is configured to use the TCP/IP transport to communicate with a "local" SNA Server (that is, if the SNA client "locates" servers in an SNA Server subdomain), the SnaBase service may fail to start, and displays the following error message:
This problem can occur if the Windows NT computer is multihomed (that is, is configured with more than one IP address), where the first client IP address is not on the same IP network as an SNA Server.
NOTE: The above error can also occur if the client is separated from the server by an IP router. To solve that problem, configure the SNA Windows NT client as "remote" (that is, "Client locates server by name").
CAUSE
When configured to connect to a local SNA Server over TCP/IP, the SNA Windows NT client sends out its first client IP address. If the server or servers are located on a different IP network, the client fails to receive the server's response.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
WORKAROUND
If Windows NT 4.0 Service Pack 4 is being used, the following articles may help work around the problem by forcing TCP/IP to return a specific IP address to SNA Server:
171320 How to Change the IP Address ListOrder Returned
164023 Fix for Gethostbyname() IP AddressOrder on Local Multihomed Mac
STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server. This problem was first corrected in SNA Server version 4.0 Service Pack 3.
Keywords: kbbug kbfix kbsna400sp3fix kbqfe kbfea kbhotfixserver KB214430
