Article ID: 270588 - Last Review: March 1, 2007 - Revision: 3.3 Remote Desktop Protocol Clients Cannot Connect to Terminal Services ServerThis article was previously published under Q270588 SYMPTOMS Terminal Services clients may not be able to connect to a
Windows 2000-based computer that is running Terminal Services. When you use the Terminal Services Configuration snap-in (Tscc.msc), the transport (RDP-Tcp) appears to be present and working. However, when you view the transport by using Terminal Services Manager (Tsadmin.exe), the RDP-TCP listener is reported as "Down 65536." CAUSE This problem can occur if the server has been booted by
using the Last Known Good Configuration option more than once. When the server has been booted into the
last known good configuration more than once, the ControlSet001 registry key is
deleted. However, the following registry value is hard-coded to use the
ControlSet001 registry key:
Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\VIDEO\rdpdd\ Value name: \Device\Video0 Value type: REG_SZ Value data: \REGISTRY\Machine\System\ControlSet001\Services\RDPDD\Device0 RESOLUTIONImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 260910
(http://support.microsoft.com/kb/260910/EN-US/
)
How to Obtain the Latest Windows 2000 Service Pack
To resolve this problem:
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Windows 2000 Service
Pack 2. | Article Translations
|
Back to the top
