Resources Troubleshooting Connectivity Issues with Terminal Services

One of the biggest call generators has always been the dreaded "Remote Desktop Disconnected" or "Can't Connect to Remote Computer" error messages when trying to connect to a terminal server from a client. The problem with this issue is that there're a myriad of causes that all end up causing the same symptom.Since there're several […]

One of the biggest call generators has always been the dreaded "Remote Desktop Disconnected" or "Can't Connect to Remote Computer" error messages when trying to connect to a terminal server from a client. The problem with this issue is that there're a myriad of causes that all end up causing the same symptom.

Since there're several causes for the same thing, there's a lot of information out there on how to troubleshoot the various causes. The problem is, all of this troubleshooting matemrial is spread out in multiple Knowledge Base articles. Below you'll find a compilation of all the resources broken into three articles; one for each OS generation:

  • KB186645: Troubleshooting RDP Client Connection Problems (aggregate article that points to the three below)
  • KB2477023: Remote Desktop Disconnected or Can't Connect to Remote Computer or Remote Desktop Server (Terminal Server) running Windows Server 2003
  • KB2477133: Remote Desktop Disconnected or Can't Connect to Remote Computer or Remote Desktop Server (Terminal Server) running Windows Server 2008
  • KB2477176: Remote Desktop Disconnected or Can't Connect to Remote Computer or Remote Desktop Server (Terminal Server) running Windows Server 2008 R2
  • Port assignment issue: 1, 2, 3
  • This article talks about how to troubleshoot a remote desktop disconnected problem but doesn't cover all the symptoms.
  • Additionally, we've more symptoms documented under the following article: Troubleshooting General Remote Desktop Error messages.

[tags]terminal server[/tags]

[Source]