Virtual machine connection - Remote desktop connection - The identity of the remote computer cannot be verified

All replies

• 

  

  0

  Sign in to vote

  How are you trying to connect? RDP? VMconnect? Programmatically? Telnet?

  It appears the remote computer is in a domain.  Is the local machine in the same domain?

  Have you installed the certificate from the remote computer into the local machine?

  ---

  . : | : . : | : . tim

  • Proposed as answer by John Lii Thursday, March 2, 2017 9:54 AM

  Saturday, February 18, 2017 1:16 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  Virtual machine connection enhanced session mode is enabled. If I click on Connect... in Hyper-V manager, that message is popping up.

  I checked there is self-signed certificate for Hyper-V Virtual Machine Management service installed, which has FQDN of my Hyper-V host and "Subject Name" does match FQDN of the machine as described in

  https://technet.microsoft.com/en-us/library/ff935311(v=ws.10).aspx

  However, VMConnect expect Machine name instead of FQDN:

  Requested remote computer name: HOST [MachineName]
  Name in the certificate from the remote computer: HOST.domain.local [FQDN]

  Saturday, February 18, 2017 1:37 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  Hi Slimglas,

  >> "The remote computer could not be authenticated due to problem with its security certificate. It may be unsafe to proceed."

  For this issue, please check link below to fix it:

  Resolving certificate name mismatches when managing a Hyper-V host in VMM

  https://blogs.technet.microsoft.com/m2/2010/09/01/resolving-certificate-name-mismatches-when-managing-a-hyper-v-host-in-vmm/

  Best Regards

  John

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  Wednesday, February 22, 2017 6:55 AM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  Hi Slimglas,

  Just want to confirm the current situations.

  Please feel free to let us know if you need further assistance.

  Best Regards,

  John

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  Thursday, March 2, 2017 9:54 AM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  I am running Hyper-V on domain joined Win10 1607 Enterprise host.

  Downloaded script from http://www.mcbsys.com/blog/2011/06/hyper-v-certificate-will-expire-within-30-days/, created new self signed VMMS certificate, deleted old one, restarted Hyper-V virtual machine management service, started VM.

  But I am still getting the same Name mismatch security warning when I press on Connect... in Hyper-V manager. If I click on View certificate..., newly generated certificate is displayed which has "CN=FQDN" subject. But security warning shows  that remote desktop connection expects Requested remote computer: "CN=hostname" instead:

  

  Saturday, March 25, 2017 7:51 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  Hi,

  >>If I click on View certificate..., newly generated certificate is displayed which has "CN=FQDN" subject.

  Please check link below to understand this error:

  You receive various certificate related error messages when connecting to a Terminal server that is running Windows Server 2008 or Windows Server 2008 R2

  https://support.microsoft.com/en-us/help/2000960/you-receive-various-certificate-related-error-messages-when-connecting-to-a-terminal-server-that-is-running-windows-server-2008-or-windows-server-2008-r2

  Best Regards

  John

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  Monday, March 27, 2017 3:09 AM

  Reply

  |

  Quote