Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services Server (323597)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows XP Professional
This article was previously published under Q323597 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 When you try to connect from a Windows XP-based client to a
Windows 2000-based Terminal Services server, the connection may not succeed and
you may receive the following error message: Because of
a security error, the client could not connect to the terminal server. After
making sure that you are logged on to the network, try connecting to the server
again. This error message may occur when you try to connect from a
Windows XP-based client to some or all of the Windows 2000-based Terminal
Services servers in your organization, or the error message may not occur at
all. When you try to connect from a Windows 2000-based client to a
Windows 2000-based Terminal Services server, the following error may be logged
on the Windows 2000 Teminal Server: Event
ID: 1003
Source: TermService
Type: Information
The terminal
service client has provided an invalid license. CAUSE This error message is caused by a change in the
certificates that are used by the Microsoft Clearinghouse to authorize Terminal
Services Licensing servers. RESOLUTIONWARNING: 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 problem, follow the steps in the
following section on the affected Windows 2000-based Terminal Services servers
and the Windows XP-based clients. On the Terminal Services Server- Start Registry Editor (Regedit.exe or
Regedt32.exe).
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters - In this registry key, delete the following values:
Certificate
X 509 Certificate
X 509 Certificate ID - Quit Registry Editor, and then restart the
server.
On the Windows XP-Based Client- Start Registry Editor (Regedit.exe).
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing - Delete the whole MSLicensing key from the registry.
- Quit Registry Editor.
- Connect to the Terminal Services server.
NOTE: If these steps do no resolve the problem, you must deactivate
and then reactivate the Terminal Services Licensing server. To do so, call the
Microsoft Clearinghouse at 1-888-571-2048. STATUSMicrosoft has confirmed that this is a problem
in Windows 2000.
MORE INFORMATION Because Windows XP Professional-based clients have a
built-in Terminal Services Client Access License (CAL) for accessing Windows
2000-based Terminal Services servers, deleting the MSLicensing key on the client does not adversely affect license allocation in
an organization.
| Modification Type: | Major | Last Reviewed: | 12/4/2003 |
|---|
| Keywords: | kbenv kberrmsg kbprb KB323597 |
|---|
|