Article ID: 215475 - Last Review: November 1, 2006 - Revision: 2.2

Slow Performance with GSNW on Terminal Server

View products that this article applies to.
This article was previously published under Q215475

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  (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry
Expand all | Collapse all

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.
Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for 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:
152734  (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


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
Back to the top

STATUS

Microsoft has confirmed that this is 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.
Back to the top
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
Back to the top
Keywords: 
kbhotfixserver kbqfe kbbug kbfix KB215475
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations