Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Careers | About Us | Contact Us|

 

Case collection of Event ID 50 Source TermDD

Symptoms: 1. The Windows Event Viewer has this log:
Event Type: Error
Event Source: TermDD
Event ID: 50
Description: The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.
2. The Terminal Services client may also receive the following error message during a connection attempt: The terminal Server has ended the connection.
3. Because of a security error, the client could not connect to the Terminal server.
4. Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer.
5. The connection was lost due to a network error.

Case 1: The TermDD was damaged.
Resolution: Export it from a working computer and import it.

Case 2: To resolve this issue, follow these steps:
1. Run regedit.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following values:
o Certificate
o X509 Certificate
o X509 Certificate ID
4. Quit Registry Editor, and then restart the server.
Case 3: You may wan to delete and recreate RDP-tcp listener by following these steps:
1. Launch TSCC.MSC and delete the RDP-tcp listener.
2. Reboot.
3. Go back to TSCC.MSC and create a new listener.
4. Reboot

Case 4: Upgrading NIC drive fixes the problem.

Case 5: It could be the FIPS encryption issue. To disable level by changing the Encryption level setting in the RDP-Tcp Properties dialog box, follow these steps:
1. Click Start, click Run, type tscc.msc in the Open box, and then click OK.
2. Click Connections, and then double-click RDP-Tcp in the right pane.
3. In the Encryption level box, click to select a level of encryption other than FIPS Compliant.

Note If the Encryption level setting is disabled when you try to change it, the system-wide setting for System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing has been enabled, and you must disable this system-wide setting by using method 2.

 

 

 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

 

  This web is provided "AS IS" with no warranties.
Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.