Troubleshooting RDP Client connection problems
This article describes various symptoms for Remote Desktop Client connection failures.
Original product version: Windows Server 2012 R2
Original KB number: 186645
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: Remote Desktop disconnected or can't connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2003
- Server 2008: General Remote Desktop connection troubleshooting
- Server 2008 R2: Troubleshoot "Remote desktop disconnected" errors in Windows Server 2008 R2
Additionally, we have more symptoms documented in the following Microsoft TechNet article: