![rdp from mac to windows not working certificate not valid rdp from mac to windows not working certificate not valid](https://cdn.ttgtmedia.com/rms/onlineimages/Troubleshooting_RDP_1_mobile.jpg)
- #Rdp from mac to windows not working certificate not valid for mac#
- #Rdp from mac to windows not working certificate not valid password#
I have disabled RemoteFX on the RD/VPN server, and the RDC Mac client still does not connect. They are unable to connect using the Microsoft Remote Desktop client and temporary using CoRD as a band-aid. I would like this to be resolved soon as possible since I have several OSX notebooks that VPN/RD into the server outside the office, as of now My only guess is, it has to do with something in RemoteFX since this is the major new feature with RDP 7.1. In a different location, I have a 2008 R2 (without SP1) RD/VPN server running RDP 6.1 (7.0), it works fine with the RDC 2.1.1 mac client, this server has not been updated with the latest patches and updates. These are identical operating system versions and latest updates, So it has to do with the Remote Desktop Session Server running Microsoft RDP 7.1. Works with 2.1.1 RDC Mac Client, the remote desktop/vpn server does not work with the mac RDC client. The data server with administrative remote desktop Both servers are identical in 2008 R2 SP1 version with the latest patches & updates as of 9-16-12.
![rdp from mac to windows not working certificate not valid rdp from mac to windows not working certificate not valid](https://mycoder.pro/wp-content/uploads/2020/05/algo-trading-on-apple-mac.jpg)
I have a data server with administrative remote desktop on, and a Hyper-V RD/VPN server. I posted this in a different forum "Microsoft Answers". I'm having the same issue and narrowed down the possible cause.
![rdp from mac to windows not working certificate not valid rdp from mac to windows not working certificate not valid](https://techglimpse.com/wp-content/uploads/2021/10/dst-root-ca-x3-error.jpg)
#Rdp from mac to windows not working certificate not valid for mac#
In my eyes the problem is on the security requirements that the RDC for Mac needs but I can't find any inforamtion on MS sites about it. The only solution I've found on google is to use CoRD instead but we got problems with that connection since it keep crasching on our computer. We've also tried with CoRD and it works fine as RDP from a normal Windows based computer. We have installed the server certificate on the Mac client but it didn't help. I've tried all settings in the TS server and there is not much to change on the RDP client. Try to connect again" Where I can choose "Cansel" or "reconect"īut it just keeps poping up if i chose reconnect. Here I get anotherĮrror message which says something like: (We get it in Swedish). "Connection to the windows-based computer broke since there was a problem associated with the licensificationprotocol. I've changed the settings on the "configuration for host server for remote desktop sessions" under General from "RDP-Security Layer" to "Negotiate" and in this case I get a logon windows where i type in all my information click logon.
![rdp from mac to windows not working certificate not valid rdp from mac to windows not working certificate not valid](https://cdn.ttgtmedia.com/rms/onlineimages/Troubleshooting_RDP_7_mobile.jpg)
"Remote Desktop cannot verify the identity of the computer you want to connect to. The problem is that when using RDC to the external IP they get bellow: Their servers is not in any domain and it work for them to connect to another Windows Server 2008 that is located in their office when they use internal IP. They've just upgraded from Windows Server 2003 to 2008 and can't connect through RDP to their TS server on external IP. (It's as if Windows' RDP server is comparing your remote authenticationĪttempt against the previous physical authentication, and refusing if they don't match.)īest wishes.We have a customer that is using Mac and Microsoft's RDC for Mac to their servers.
#Rdp from mac to windows not working certificate not valid password#
Refuse your username/ password connection attempt via RDP. Non-password) credentials, then the RDP receiver/server on the Windows laptop will It seems that there is a caching issue, such that if the last/previous time you directly logged into Windows was via biometric or PIN (or other Thereafter, with the Windows laptop upĪnd running, go onto your Mac, fire up RDP, and use it to connect from Mac to Windows as you would expect to. I found a painless way of resolving this was to physically log in to the Windows laptop, using your password (ONLY, and NOT your face or fingerprint or PIN), and then log out (and if possible, then reboot).