- #RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID FOR MAC#
- #RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID FULL#
- #RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID TRIAL#
- #RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID WINDOWS#
#RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID FULL#
The mac RDP client does not recognize the full license, I think this was confirmed in the below link.
#RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID TRIAL#
This server is running RDP 7.1 and has the same issue with the Mac client not logging on.įrom my understanding the problem arises if your RDS server used the entire 90days of the trial license. It would be excellent if I can downgrade RDP 7.1 into 7.0, is there a way to downgrade so I can move on from this headache?.Īdd on: I also have a different 2008 R2 SP1 server I installed in June, this setup is a replica of the server installed this week. 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. 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 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.
#RDP FROM MAC TO WINDOWS NOT WORKING CERTIFICATE NOT VALID WINDOWS#
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.