Article ID: 186645 - Last Review: December 22, 2010 - Revision: 3.0

Troubleshooting RDP Client connection problems

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q186645

Expand all | Collapse all

SUMMARY

This article summarizes the various causes for Terminal Server Client connection failures.

Terminal Server Client (Remote Desktop Client) connection failures such as "Unable to RDP, "Remote Desktop Disconnected," or "Unable to Connect to Remote Desktop (Terminal server)" are common problems that we have seen in product support. This article summarizes the various causes for such failures.

The following are some of the commonly seen symptoms:

You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session.
You may have a port assignment conflict.
You may have an incorrectly-configured Authentication and Encryption setting.
You may have a certificate corruption.

All the steps are documented in these articles, based on the server operating system:

Server 2003: http://support.microsoft.com/kb/2477023 (http://support.microsoft.com/kb/2477023)
Server 2008: http://support.microsoft.com/kb/2477133 (http://support.microsoft.com/kb/2477133)
Server 2008 R2: http://support.microsoft.com/kb/2477176 (http://support.microsoft.com/kb/2477176)

Additionally, we have more symptoms documented in the following Microsoft TechNet article:

Troubleshooting General Remote Desktop Error messages
http://technet.microsoft.com/en-us/library/cc780927(WS.10).aspx (http://technet.microsoft.com/en-us/library/cc780927(WS.10).aspx)