Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server

Article ID: 270588 - View products that this article applies to.
This article was previously published under Q270588
Notice
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)
is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
(http://support.microsoft.com/lifecycle/)
.
Expand all | Collapse all

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

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

RESOLUTION

Important 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:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\VIDEO\rdpdd\
    Note If you do not have this key, use Registry Editor to create it.
  3. Do one of the following:
    • If you did not have to create the key in step 2, change the following value
      Name:
      \Device\Video0

      Type:
      REG_SZ

      Value:
      \REGISTRY\Machine\System\ControlSet001\Services\RDPDD\Device0
      to the following:
      Name:
      \Device\Video0

      Type:
      REG_SZ

      Value:
      \REGISTRY\Machine\System\CurrentControlSet\Services\RDPDD\Device0
    • If you had to create the registry key in step 2, add the following value:
      Subkey name:
      RDPDD

      Name:
      \Device\Video0

      Type:
      REG_SZ

      Value:
      \REGISTRY\Machine\System\CurrentControlSet\Services\RDPDD\Device0
  4. After you change (or create) the value, restart the computer that is running Terminal Services.
Back to the top | Give Feedback

STATUS

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

Properties

Article ID: 270588 - Last Review: March 1, 2007 - Revision: 3.5
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
Keywords: 
kbbug kbenv kbtermserv KB270588
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top