Offline Servers Should Be Removed from Clients' Service Table (236578)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft Host Integration Server 2000
This article was previously published under Q236578 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SUMMARY
SNA Clients for Microsoft Windows NT versions 4.0 Service Pack 1 (SP1) and 4.0 Service Pack 2 (SP2), and SNA Clients for Microsoft Windows 95 and Microsoft Windows 98 version 4.0 SP2 may suffer long delays when trying to acquire an SNA resource from the subdomain if one or more configured sponsor servers are offline.
When configured for remote access, the SNA Clients listed above have their sponsor SnaBase entries created with a flag that guarantees that they are never removed from the client's service table. This is to avoid problems if the sponsor connection is lost and later reopened.
If the SNA Client tries to get an SNA resource from a configured server that is currently not available for any reason, it must wait for all connection retries to time out before trying another server from its list.
Modification Type: | Minor | Last Reviewed: | 6/5/2006 |
---|
Keywords: | kbHotfixServer kbQFE kbFEA kbinfo KB236578 |
---|
|