OSX Mac RDP Clients cannot connect to Terminal Server 2012 because of problems during the licensing protocol
Last month I replaced our old windows server with Windows 2012 Terminal Server.
After the install, I installed Microsoft Remote Desktop 2.1.1 on all of my Apple Mac OSX 10.8 iMacs.
All was working perfectly.
After what I think is 45 days all my Apple Macs suffered the same problem when trying to establish a RDP connection.
See attached Image:
"You were disconnected from the windows-based computer because of problems during the licensing protocol."
If I try connecting from a spare PC using Remote Desktop and the same user credentials I am able to log in fine.
This means the user has permission to log on. The Terminal Server is refusing connections from all my Apple Macs.
If this is really a Licensing Protocol issue, I wonder if the problem is caused by temporary Device CALS expiring? I am fully licensed with plenty of CAL's, It should be applying device cal's to Apple Macs.
I need help diagnosing the problems here. Is there a log file I can read on the Terminal Server that tells me exactly why it refuses connections from my Apple Macs?
Is there a way to flush out the device cals or check to see if they are allocated properly to my Apple Macs?
Thanks
mchallinor
MacRDP.png
After the install, I installed Microsoft Remote Desktop 2.1.1 on all of my Apple Mac OSX 10.8 iMacs.
All was working perfectly.
After what I think is 45 days all my Apple Macs suffered the same problem when trying to establish a RDP connection.
See attached Image:
"You were disconnected from the windows-based computer because of problems during the licensing protocol."
If I try connecting from a spare PC using Remote Desktop and the same user credentials I am able to log in fine.
This means the user has permission to log on. The Terminal Server is refusing connections from all my Apple Macs.
If this is really a Licensing Protocol issue, I wonder if the problem is caused by temporary Device CALS expiring? I am fully licensed with plenty of CAL's, It should be applying device cal's to Apple Macs.
I need help diagnosing the problems here. Is there a log file I can read on the Terminal Server that tells me exactly why it refuses connections from my Apple Macs?
Is there a way to flush out the device cals or check to see if they are allocated properly to my Apple Macs?
Thanks
mchallinor
MacRDP.png
ASKER
Nope, I've tried CoRD and for some reason It will not connect to my Terminal Server.
CoRD will connect to some of my other Windows Servers, but just hangs when trying my Terminal Server.
No error message either.
iTap will work but I refuse to spend over £300 to get my Apple Macs working on Terminal Server when I believe the issue with is with Windows Terminal Server 2012.
CoRD will connect to some of my other Windows Servers, but just hangs when trying my Terminal Server.
No error message either.
iTap will work but I refuse to spend over £300 to get my Apple Macs working on Terminal Server when I believe the issue with is with Windows Terminal Server 2012.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Through many hours of trial and error I discovered a workaround solution myself.
http://cord.sourceforge.net