Slow Performance with GSNW on Terminal Server

ID: Q215475

The information in this article applies to:

Microsoft Windows NT Server version 4.0, Terminal Server Edition

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you access NetWare resources or run a login script, the response is very slow.

Reading a trace using Microsoft Network Monitor shows the following items multiple times.

NCP Request: Read Property Value
NCP Reply: Read Property Value - No Such Object
NCP Disconnect

When Terminal Server does an NCP read property value, the NetWare server responds with No Such Object, and then the Terminal Server computer disconnects.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

After applying Service Pack 4 for Terminal Server, ensure that the following registry entry is configured:

HKEY_LOCAL_MACHINE\SYSTEM\CCS\Services\NwRdr\Parameters

Use the following information for configuring:

Disconnect REG_DWORD
1 Original Behavior, Disconnect (Default)
0 New Behavior, Do not Disconnect

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Additional query words: tse-sp4

Keywords : kbbug4.00 kbfix4.00 TSESP4Fix
Version : winnt:4.0
Platform : winnt
Issue type : kbbug