Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Christopher Brooks, 14 Aug 2014 Last updated: 15 Aug 2014 While setting up Ampere (Windows Server 2012R2), when connecting via Remote Desktop Connector on the Mac, we got Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. The problem was that the old version of 'Microsoft Remote Desktop Connection Client for Mac version 2.1.1 (110309)' did not work. 
Updating to Microsoft Remote Desktop App from the store helped. Also, in the interim, I modified the firewall rules, and rebooted, so that might have something to do with it, though after the reboot, the old version (2.1.1) still did not work. Next question ©2002-2018.
Mac remote desktop connection cannot verify the identity of the remote computer Last Updated: Mar 06, 2018 Symptom. In a remote connection to ECS Windows 2012 server from a Mac desktop, the system prompts “Remote desktop connection is unable to verify the identity of the remote computer you want to connect to”.
Hi, I had a similar problem, however I was trying to connect to a Win7 machine from an iMac running 10.6.6. All was working fine for the last few months then suddenly stopped allowing me to connect this morning.
I followed these instructions and now it's all back to normal so far. Both give the same info, just happened across them at the same time. Hope this helps. Same Issue with US, Solved by this.Need to update on Terminal Services Licensing Server and Terminal Server To resolve this issue, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Terminal Services Licensing server. To do this, follow these steps.
NOTE: Perform the following procedure on each of the terminal servers. • Make sure that the terminal server registry has been successfully backed up.
• Start Registry Editor. • Locate and then click the following registry subkey. I too was having the problem same as error on my mac clients (which had previously worked fine). However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security layer is negotiate and the certificate is the one selected on that screen. It was not licensing related. The certificate had expired and I didn't believe I needed it.
But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers) do not have IIS installed, I was a bit stumped on how to create a new certificate request.
I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template chosen was 'legacy key', and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client.
Popular Posts
Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Christopher Brooks, 14 Aug 2014 Last updated: 15 Aug 2014 While setting up Ampere (Windows Server 2012R2), when connecting via Remote Desktop Connector on the Mac, we got Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. The problem was that the old version of \'Microsoft Remote Desktop Connection Client for Mac version 2.1.1 (110309)\' did not work. 
Updating to Microsoft Remote Desktop App from the store helped. Also, in the interim, I modified the firewall rules, and rebooted, so that might have something to do with it, though after the reboot, the old version (2.1.1) still did not work. Next question ©2002-2018.
Mac remote desktop connection cannot verify the identity of the remote computer Last Updated: Mar 06, 2018 Symptom. In a remote connection to ECS Windows 2012 server from a Mac desktop, the system prompts “Remote desktop connection is unable to verify the identity of the remote computer you want to connect to”.
Hi, I had a similar problem, however I was trying to connect to a Win7 machine from an iMac running 10.6.6. All was working fine for the last few months then suddenly stopped allowing me to connect this morning.
I followed these instructions and now it\'s all back to normal so far. Both give the same info, just happened across them at the same time. Hope this helps. Same Issue with US, Solved by this.Need to update on Terminal Services Licensing Server and Terminal Server To resolve this issue, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Terminal Services Licensing server. To do this, follow these steps.
NOTE: Perform the following procedure on each of the terminal servers. • Make sure that the terminal server registry has been successfully backed up.
• Start Registry Editor. • Locate and then click the following registry subkey. I too was having the problem same as error on my mac clients (which had previously worked fine). However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security layer is negotiate and the certificate is the one selected on that screen. It was not licensing related. The certificate had expired and I didn\'t believe I needed it.
But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers) do not have IIS installed, I was a bit stumped on how to create a new certificate request.
I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template chosen was \'legacy key\', and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client.
...'>Remote Desktop For Mac Cannot Verify The Identity Of The Computer Windows 2012(12.01.2019)Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Christopher Brooks, 14 Aug 2014 Last updated: 15 Aug 2014 While setting up Ampere (Windows Server 2012R2), when connecting via Remote Desktop Connector on the Mac, we got Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. The problem was that the old version of \'Microsoft Remote Desktop Connection Client for Mac version 2.1.1 (110309)\' did not work.
Updating to Microsoft Remote Desktop App from the store helped. Also, in the interim, I modified the firewall rules, and rebooted, so that might have something to do with it, though after the reboot, the old version (2.1.1) still did not work. Next question ©2002-2018.
Mac remote desktop connection cannot verify the identity of the remote computer Last Updated: Mar 06, 2018 Symptom. In a remote connection to ECS Windows 2012 server from a Mac desktop, the system prompts “Remote desktop connection is unable to verify the identity of the remote computer you want to connect to”.
Hi, I had a similar problem, however I was trying to connect to a Win7 machine from an iMac running 10.6.6. All was working fine for the last few months then suddenly stopped allowing me to connect this morning.
I followed these instructions and now it\'s all back to normal so far. Both give the same info, just happened across them at the same time. Hope this helps. Same Issue with US, Solved by this.Need to update on Terminal Services Licensing Server and Terminal Server To resolve this issue, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Terminal Services Licensing server. To do this, follow these steps.
NOTE: Perform the following procedure on each of the terminal servers. • Make sure that the terminal server registry has been successfully backed up.
• Start Registry Editor. • Locate and then click the following registry subkey. I too was having the problem same as error on my mac clients (which had previously worked fine). However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security layer is negotiate and the certificate is the one selected on that screen. It was not licensing related. The certificate had expired and I didn\'t believe I needed it.
But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers) do not have IIS installed, I was a bit stumped on how to create a new certificate request.
I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template chosen was \'legacy key\', and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client.
...'>Remote Desktop For Mac Cannot Verify The Identity Of The Computer Windows 2012(12.01.2019)