Windows Server TechCenter > Windows Server Forums > Management > Remote Desktop to Server questions
Ask a questionAsk a question
 

AnswerRemote Desktop to Server questions

  • Tuesday, November 03, 2009 3:27 PMJasonS134 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm trying to use the remote desktop connection to connect to a server (off site). it worked this morning, but this afternoon when I tried I get the following error message:

    Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.

    I've tried from different computers in my office, but they all give the same error message, leading me to believe that it is a problem with the server. But nothing has changed with the server since this morning (when rdp was working). I know the ip address of the server hasn't changed (both external or internal). I don't know what is causing this or how to fix it. Any ideas? Any help is greatly appreciated. Thanks.

Answers

  • Tuesday, November 03, 2009 4:00 PMKudrat Sapaev Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi,

    Have a look at this:

    http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html

    Also, do you have a physical access to the server or maybe somebody else, you need to check logs on the server.
    It is possible that there are some problems with the licensing.

    сила в справедливости
  • Wednesday, November 04, 2009 2:37 AMWilson JiaMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    You may refer to the following KB to verify whether other processes have occupied the port.

     

    886209  Users cannot connect to remote desktops by using the Windows Small Business Server 2003 Remote Web Workplace

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;886209

     

    This problem may also occur when eencryption levels defined on the RDP-TCP connection (or ICA, if appropriate), are set too high for the client to successfully negotiate. I suggest you do the following:

     

    1.            Open Terminal Service Configuration, open properties page of RDP-tcp.

    2.            In General tab, Encryption level section, please selects "Medium" or "Low".

    3.            Click OK to exit.

     

    In addition, please test whether this issue exists for clients in LAN. If not, it is related to network. It may be related to black hole router issue.

     

    How to Troubleshoot Black Hole Router Issues

    http://support.microsoft.com/?id=314825

     

    Best Regards,

    Wilson Jia


    This posting is provided "AS IS" with no warranties, and confers no rights.

All Replies

  • Tuesday, November 03, 2009 4:00 PMKudrat Sapaev Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi,

    Have a look at this:

    http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html

    Also, do you have a physical access to the server or maybe somebody else, you need to check logs on the server.
    It is possible that there are some problems with the licensing.

    сила в справедливости
  • Wednesday, November 04, 2009 2:37 AMWilson JiaMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    You may refer to the following KB to verify whether other processes have occupied the port.

     

    886209  Users cannot connect to remote desktops by using the Windows Small Business Server 2003 Remote Web Workplace

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;886209

     

    This problem may also occur when eencryption levels defined on the RDP-TCP connection (or ICA, if appropriate), are set too high for the client to successfully negotiate. I suggest you do the following:

     

    1.            Open Terminal Service Configuration, open properties page of RDP-tcp.

    2.            In General tab, Encryption level section, please selects "Medium" or "Low".

    3.            Click OK to exit.

     

    In addition, please test whether this issue exists for clients in LAN. If not, it is related to network. It may be related to black hole router issue.

     

    How to Troubleshoot Black Hole Router Issues

    http://support.microsoft.com/?id=314825

     

    Best Regards,

    Wilson Jia


    This posting is provided "AS IS" with no warranties, and confers no rights.