This article was previously published under Q179190
IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information on how to do this, view the "Restoringthe Registry" online Help topic in Regedit.exe or the "Restoring a RegistryKey" online Help topic in Regedt32.exe.
The NetWare redirector component (Nwrdr.sys) of Client Services for NetWare(CSNW) and Gateway Services for NetWare (GSNW) may send additionalGetNearestServer Service Advertising Protocol (SAP) requests even afterreceiving a response to its first request.
NWRDR was originally designed to send a minimum of four SAP requests evenif it received a response to one of the previous requests.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
After the fix has been applied, there is a new registry parameter that willset the minimum number of SAP responses Windows NT must receive. Thisshould be set to the number of servers that will be responding or set tofour, whichever is less.
WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys AndValues" online Help topic in Registry Editor (Regedit.exe) or the "Add andDelete Information in the Registry" and "Edit Registry Data" online Helptopics in Regedt32.exe. Note that you should back up the registry beforeyou edit it.
Value: MinimumSapResponses Type: REG_DWORD Data: 1 to 4 (default is
Exit Registry Editor.
NOTE: This change to the Windows NT registry requires the computer to berestarted to take effect.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.