Terminal Services Client Cannot Connect to a Server Running 128-bit Encryption (257894)

The information in this article applies to:

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server

This article was previously published under Q257894

SYMPTOMS

You may be unable to connect to a Terminal Services computer that is running 128-bit encryption with its Remote Desktop Protocol (RDP) encryption level set to High. In addition, the following error message may be displayed in the event log:

Event ID: 50
The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.

CAUSE

This behavior can occur if you install the Terminal Services client from the Terminal Services client folder before the 128-bit encryption pack is installed on the Terminal Services server computer.

RESOLUTION

To resolve this behavior, use one of the following methods:

Change the RDP encryption level on the Terminal Services computer to Medium or Low.
Uninstall the Terminal Services client, and then reinstall the Terminal Services client from the Windows 2000 Server computer on which the 128-bit encryption pack is installed.

To change the encryption level on the Terminal Server, follow these steps:

Open the Terminal Services Configuration snap-in.
Click the Connections folder, and on the right pane, right-click on the RDP-TCP connection, and then click Properties.
On the General tab of the property sheet, change the encryption level.

STATUS

This behavior is by design.

MORE INFORMATION

For additional information about Terminal Services connections, click the article numbers below to view the articles in the Microsoft Knowledge Base:

232514 Securing Terminal Server Communication Between Client and Server

270897 How Terminal Server Advanced Client Connects to a Terminal Server Computer

Modification Type:	Minor	Last Reviewed:	3/13/2006
Keywords:	kbenv kberrmsg kbprb kbTermServ w2000wts KB257894