The client could not establish a connection to the remote computer. The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.Īdditionally, you may also see this error message: Verify that you are logged on to the network and then try connecting again. You may have an incorrectly configured Authentication and Encryption settingīecause of a security error, the client could not connect to the remote computer.

If the problem continues, contact the owner of the remote computer or your network administrator. This computer can’t connect to the remote computer. You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session Some of the commonly seen Symptoms (order of frequency): This article summarizes the various causes for Terminal Server Client (Remote Desktop Client) connection failures and how to fix them.

Specifically, errors such as “Unable to RDP,” “Remote Desktop Disconnected,” or “Unable to Connect to Remote Desktop (Terminal server)” are common problems that we have seen come up in product support. One of the recurring issues seen in product support is why a client cannot connect. To learn about RDS in Windows Server 2016, please visit our First published on CloudBlogs on Jan, 10 2011

Remote desktop protocol error