SNA Client Does Not Retry Other Sponsors After Error Response

• Microsoft SNA Server, versions 2.11, 3.0SP1, 3.0SP2, and 4.0

SYMPTOMS

When the SNA client attempts to get its sponsor connection from a specific SNA Server computer and it receives an error, the SNA client never tries to connect to another sponsor server listed in its sponsor server list. Instead, the SNA client repeatedly tries to connect to the first SNA Server computer that it attempted to connect to.

WORKAROUND

For SNA Server clients using Windows NT or Windows 95, a registry entry must be added in order for users to specify a SponsorRetryDelay time in case TerminateIfNoSponsors is disabled. This registry entry gives slow wide area networks or SNA Server computers time to recover from failure.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

To work around the problem, add the following registry entry:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SnaBase\Parameters:
   SponsorRetryDelay:REG_DWORD:<retry delay in seconds>

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 2.11, 3.0 SP1, 3.0 SP2, and 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.