Forum Discussion

jvalois's avatar
jvalois
Copper Contributor
Sep 19, 2019

connection terminated unexpected server authentication certificate windows 10

Hi Team, 

 

My windows 10 users keep getting this error message many times when they try to log into RDP sessions.

They get this error for about 7 times then logged in.

 

I've looked around but don't have a good answer or findings.

The connection has been terminated because an unexpected server authentication certificate was received from the remote computer.

Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

 

Were on 1903 

 

  • PaulaSillars's avatar
    PaulaSillars
    Iron Contributor
    Sep 19, 2019

    jvalois 

    Is there anything in the Eventlog on the machine they are RDPing to?  

    Is the machine they are RDPing to also Windows 10 1903 or are they connecting to and RDSH server?

    • jvalois's avatar
      jvalois
      Copper Contributor
      Sep 20, 2019

      PaulaSillarsWindows server 2008 SP1 

      The description for Event ID 54 from source RDPDR cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
      If the event originated on another computer, the display information had to be saved with the event.
      The following information was included with the event:
      \Device\RdpDrDvMgr
       
      The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: 10.1.2.34.
       
      This is what I get from the event viewer, is there another place I can look at?
      • HotCakeX's avatar
        HotCakeX
        MVP
        Sep 21, 2019
        Hi,
        can you remember what exactly triggered this issue? like after changing something on the server or installing a new role or program on it? or did the problem suddenly started happening?
  • bish0801's avatar
    bish0801
    Copper Contributor
    May 28, 2020

    jvalois had similar issue on Terminal server (2008R2) logging in from Win 10 1903. found out it was being caused by the RDP certificate. regenerated the Certificate and issue was resolved for us. 

    • WorkRelated's avatar
      WorkRelated
      Copper Contributor
      Jun 05, 2024

      bish0801 Can you please provide the instruction on how u have re-created the RDP Certificate?

       

  • kacjr53's avatar
    kacjr53
    Copper Contributor
    Jun 01, 2021
    I have the same issue, only I'm running a 5-server RD farm. I have several users with the exact same laptop running the exact same image. The laptops are configured to only allow the user to get into a remote desktop session through an RD broker server. One and only one of these laptops is exhibiting this error. I have tried reimaging the laptop but to no avail. The RD environment is using only self-signed certificates that are automatically implemented by RD services. I'm at a loss as to where else to look. What could be so "special" about this one laptop?
  • sandeeprajaiah's avatar
    sandeeprajaiah
    Copper Contributor
    Apr 25, 2023

    jvalois I faced the same issue but I could get over the issue by following the below steps :


    In the remote desktop connection dialogue box, Click on Experience and uncheck 2 options 
    - Persistent bitmap caching 
    - Reconnect if the Connection is dropped 

    Clearing the cache would solve the issue. 

     


    Worth giving it a try...!

Resources