How to resolve the issue “Remote Desktop Disconnected” or “Unable to Connect to Remote Desktop (Terminal Server)”

Rate This
  • Comments 16

One of the recurring issues seen in product support is why a client cannot connect.

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.

This article summarizes the various causes for Terminal Server Client (Remote Desktop Client) connection failures and how to fix them.

Some of the commonly seen Symptoms (order of frequency):

  1. You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session
  2. You may have a Port assignment conflict
    • Associated Error messages:
      Remote Desktop Disconnected.
      This computer can’t connect to the remote computer.
      Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
  3. You may have an incorrectly configured Authentication and Encryption setting
  4. You may have a corrupted Certificate
    • Associated Error messages:
      Remote Desktop Disconnected.
      Because of a security error, the client could not connect to the remote computer.
      Verify that you are logged on to the network and then try connecting again.
    • Associated Event IDs:
      Event ID: 50
      The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
    • Additionally, you may also see this error message:
      The client could not establish a connection to the remote computer.
      The most likely causes for this error are:
      1) Remote connections might not be enabled at the remote computer.
      2) The maximum number of connections was exceeded at the remote computer
      3) A network error occurred while establishing the connection
      4) The remote computer might not support the required FIPS security level. Please lower the client side required security level policy, or contact your network administrator for assistance.

We have provided step-by-step documentation on how to fix these issues in the following articles.

Main article:

Troubleshooting RDP Client Connection problems:

Please refer to any/all of the following articles based on your Remote Desktop Session Host Server OS:

More Information:

  1. The following posts discuss symptoms 2 & 3 from above caused due to port assignment conflicts and/or encryption level settings:
  2. The following article from talks about how to troubleshoot a remote desktop disconnected problem but only covers very basic issues.
    Ex: It asks you to check if the computer you are connecting to is powered ON and/or not in ‘Sleep’ mode.
    It also talks about some of the basic settings to enable remote desktop sessions which are covered in symptom 1 above.

Additionally, we have more symptoms documented under the following article:

Troubleshooting General Remote Desktop Error Messages

Note: This is a work in progress and we will constantly be updating these articles to reflect the latest issues and how to fix them.

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • Then again it might be a good idea to have the RDS client to provide with a better error message in the first place...

  • Can you please point me in the right direction for a major problem.

    I am forwarding a port on localhost to a remote server. The client will not connect to localhost:FWDPORT with the vague error about. I could not find any documentation on this.

  • how about connecting and dis connecting ?

  • I was having some many issue with the RDP client.  I could never understand the error messages it was giving me.  My friend told me about a third party service, ScreenConnect ( that worked.  I've used it since to help clients.

  • Very useful

  • how do remote client clients connect to a terminal server simalteniously to access the same application?i use remote desktop connection but when the other client connect to the same terminal server the other connection get do we enable concurrent connections?

  • We had to update the MSTCS on the client machines to resolve the "because of a security error..."

  • I had the computer cleaned and afterward I can not open the Remote Desktop Connection. It says that the Remote Desktop conection has expured and to download it or contact administrator. Can anyone tell me ether how to download it or how to fix it please.

  • Try to remotely logoff the user and her/his session ID.

    First try to get the session ID of the user:

    psexec \\remoteMachine -u user -p pswrd query session

    Then remotely logoff the session ID, for example session ID 1:

    logoff 1 /server:

  • I had the same problem with client WINDOWS XP could not connect to Windows 2012 R2 Remote Server.

    I solved the problem by unchecking this box : "Allow connections only for computers running Remote Desktop with Network Level Authentication (recomended)".

    To find this settings on the Windows 2012 R2 : right click on "My Computer", choose "Properties" then "Remote Settings".

    In the screen wich will pop-up, you will find that checkbox.

  • remote desktop disconnected in win xp pl soluation of this problem

  • Similar to Toni, I found the following settings were preventing remote login:

    require user authentication for remote connections by using Network Level Authentication

    set client connection encryption level

    Once I set them to "Not Configured", could log in from older systems (XP, Windows Server 2003)

  • Sir i am getting this error. how to resolve??

  • while connecting remote desktop connection( open user in desktop) - connecting to server ip addresss ; this mesaage appear :      [<Connection File>] [/v:<server[:port]>] [/console] | /?

    resolve it

  • My password had expired, that was the reason that it wasn't working for me.

Page 1 of 2 (16 items) 12

How to resolve the issue “Remote Desktop Disconnected” or “Unable to Connect to Remote Desktop (Terminal Server)”