Article ID: 323497
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows XP Professional
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
This article was previously published under Q323497
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 Description of the Microsoft Windows Registry
SYMPTOMS
After you install Windows 2000 Security Rollup Package 1 (SRP1), Terminal Services clients may not be able to connect to the Terminal Services server. You may also experience this problem when you use Remote Desktop Web Connection on a Windows XP Professional computer to connect to a Terminal Services server. When this problem occurs, event ID 50 is recorded in the system event log:
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
307454 MS01-052: Invalid RDP data can cause Terminal Services failure
The Terminal Services client may also receive the following error message during a connection attempt:
CAUSE
A potential race condition between the Icaapi.dll and Rdpwsx.dll dynamic-link libraries (DLLs) may cause the private certificate key on the Terminal Services server not to be synchronized.
RESOLUTION
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.
To resolve this issue, follow these steps:
- Start Registry Editor.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
- Under this registry subkey, delete the following values:
- Certificate
- X509 Certificate
- X509 Certificate ID
- Quit Registry Editor, and then restart the server.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbenv kbprb KB323497
