NWRDR May Send Excessive GetNearestServer Requests

The NetWare redirector component (Nwrdr.sys) of Client Services for NetWare (CSNW) and Gateway Services for NetWare (GSNW) may send additional GetNearestServer Service Advertising Protocol (SAP) requests even after receiving a response to its first request.

NWRDR was originally designed to send a minimum of four SAP requests even if 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 the Microsoft Knowledge Base:
After the fix has been applied, there is a new registry parameter that will set the minimum number of SAP responses Windows NT must receive. This should be set to the number of servers that will be responding or set to four, whichever is less.

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" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

1. Start Registry Editor (Regedt32.exe).
2. Go to the following key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NwRdr\Paramete
3. From the Edit menu, click Add Value.
4. Enter the following value:
   Value: MinimumSapResponses Type: REG_DWORD Data: 1 to 4 (default is
5. Exit Registry Editor.

NOTE: This change to the Windows NT registry requires the computer to be restarted 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.