Select the product you need help with
Because of a security error, the client could not connect to the Terminal ServerArticle ID: 329896 - View products that this article applies to. This article was previously published under Q329896 SYMPTOMS After you upgrade a Microsoft Windows NT domain to Microsoft Windows 2000
or Microsoft Windows Server 2003, Windows 2000 Terminal Services
clients may be repeatedly denied access to the terminal server. If you are
using a Terminal Services client to log on to the terminal server, you may
receive one of the following error messages: 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. -or-
Remote desktop disconnected. Because of a
security error, the client could not connect to the remote computer. Verify
that you are logged onto the network and then try connecting again. Event ID: 50 Event Source: TermDD Event Description: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client. -and- Event ID: 1008 Event Source: TermService Event Description: The terminal services licensing grace period has expired and the service has not registered with a license server. A terminal services license server is required for continuous operation. A terminal server can operate without a license server for 90 days after initial start up.
-and-
Event ID: 1004 Event Source: TermService Event Description: The terminal server cannot issue a client license. -and- Event ID: 1010 Event Source: TermService Event Description: The terminal services could not locate a license server. Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running. -and-
Event ID: 28 Event Source: TermServLicensing Event Description: Terminal Services Licensing can only be run on Domain Controllers or Server in a Workgroup. See Terminal Server Licensing help topic for more information. CAUSE This issue may occur if a certificate on the terminal
server is corrupted. 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 WindowsTo resolve this issue, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Terminal Services Licensing server. To do this, follow these steps. NOTE: Perform the following procedure on each of the terminal servers.
MORE INFORMATION
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
306578
(http://support.microsoft.com/kb/306578/
)
How to deactivate or reactivate a License Server using Terminal Services Licensing
323597
(http://support.microsoft.com/kb/323597/
)
Windows XP clients cannot connect to a Windows 2000 Terminal Services Server
PropertiesArticle ID: 329896 - Last Review: February 28, 2007 - Revision: 3.7 APPLIES TO
| Article Translations
|


Back to the top








