Microsoft KB Archive/236098

= Local TCP/IP Client Fails--No SNA Servers Found in (Sub)domain =

Article ID: 236098

Article Last Modified on 9/22/2005

-

APPLIES TO

 Microsoft SNA Server 4.0, when used with:  Microsoft Windows 95

 Microsoft Windows 98 Standard Edition  Microsoft SNA Server 4.0 Service Pack 1, when used with:  Microsoft Windows 95

 Microsoft Windows 98 Standard Edition</li></ul> </li> Microsoft SNA Server 4.0 Service Pack 2, when used with:  Microsoft Windows 95</li></ul>

 Microsoft Windows 98 Standard Edition</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q236098

<div class="notice_section">

<div class="symptoms_section">

SYMPTOMS
When you configure an SNA Server 4.0 Windows 95 or Windows 98 client for Local client mode and the TCP/IP transport, the client SnaBase may fail to locate an SNA Server and displays the following error message:

SnaBase

ERROR: No SNA Servers found in (sub)domain DOMAINNAME

This intermittent problem started to occur at a customer site that had hundreds of SNA Windows 95 and Windows 98 clients and who had configured their TCP/IP routers to forward UDP broadcasts to five SNA Servers in the subdomain. At times, the clients would fail to receive a response from an SNA Server within the 3-second client timeout interval, causing client startup problems.

<div class="cause_section">

CAUSE
The server-side SnaBase service is improperly handling client UDP startup requests, delaying 200 ms before responding to a client discovery request. Under heavy client load, these requests can be queued on the server, resulting in a delayed server response past the 3-second client timeout interval.

<div class="resolution_section">

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

<div class="workaround_section">

WORKAROUND
Configure the SNA Server Windows 95 or Windows 98 clients for Remote client mode, where the client locates the server by name and does not rely on the UDP response from the server.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server version 4.0, 4.0 SP1, and 4.0 SP2. This problem was first corrected in SNA Server version 4.0 Service Pack 3.

<div class="moreinformation_section">

MORE INFORMATION
The server-side SnaBase has been changed to respond immediately to client discovery requests received over TCP/IP or IPX or Banyan (except on named pipes, used by old LAN Manager clients) instead of waiting 200 ms.

Keywords: kbbug kbfix kbsna400sp3fix kbqfe kbhotfixserver KB236098

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.