Cause: If you upgraded a Windows NT domain to Windows 2000 or Windows Server 2003, then the certificate on the terminal server might be corrupt. As a result, Windows 2000 Terminal Services clients might be repeatedly denied access to the terminal server.
Solution: On each terminal server and client, perform the following steps:
|
1.
|
On each terminal server, create a backup of the registry.
|
|
2.
|
Navigate to the following registry subkey: HKLM\SYSTEM\CurrentControlSet\Services\TermServices\Parameters.
|
|
3.
|
On the Registry menu, click Export Registry File.
|
|
4.
|
In the File name box, type exported-parameters, and then click Save.
If you need to restore this registry subkey in the future, double-click exported-parameters.reg.
|
|
5.
|
Under the Parameters registry subkey, right-click each of the following values:
| • |
Certificate
|
| • |
X509 Certificate
|
| • |
X509 Certificate ID
|
|
|
6.
|
Click Delete, and then click Yes to confirm the deletion.
|
|
7.
|
Close Registry Editor, and then restart each terminal server.
|
|
8.
|
On the client, create a backup of the MSLicensing registry key and its subkeys, and then remove the original key and subkeys by doing the following:
| • |
Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
|
| • |
Click MSLicensing.
|
| • |
On the Registry menu, click Export Registry File.
|
| • |
In the File name box, type mslicensingbackup, and then click Save.
|
| • |
If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
|
| • |
On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
|
| • |
Close Registry Editor, and then restart the client computer.
|
|
Caution
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
Solution: If the client still cannot connect to the terminal server, perform the following variation of this procedure:
|
1.
|
Deactivate the license server.
|
|
2.
|
Reactivate the license server by using the Telephone connection method in the Terminal Server License Server Wizard.
When you activate Terminal Server Licensing by using the Telephone option, Terminal Server Licensing uses a different certificate.
|
|
3.
|
On each terminal server, create a backup of the registry, and then delete the Certificate, X509 Certificate, and X509 Certificate ID registry keys, as described in the preceding procedure.
|
|
4.
|
Close Registry Editor, and then restart each terminal server.
|
|
5.
|
On the client, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys as described in the preceding procedure.
|
|
6.
|
Close Registry Editor, and then restart the computer.
|
When the client is restarted, the missing registry key is rebuilt.
Cause: Windows XP-based clients might be attempting to connect to a Windows 2000-based Terminal Services server in a low-bandwidth network environment, in which client sessions are encrypted. In this case, IP packet fragmentation can cause encrypted frames that are sent by a client to be decrypted incorrectly.
Solution: Obtain the latest service pack for Windows 2000.
Cause: The Remote Desktop Protocol (RDP) encryption settings on the terminal server computer and the client might not be compatible. For example, the terminal server might be running 128-bit encryption with an encryption level set to High. When this occurs, "Event ID 50, Source: TermDD" appears in the system event log on the terminal server.
Solution: Change the RDP encryption level on the terminal server to Medium or Low.
Forums
Contact Us
Business Desktop Deployment (BDD) 2007
Windows 2003
Email
Print
Add Comment