Advertisements

Archive

Archive for the ‘Remote Desktop Connection’ Category

Mac OS X not able to connect to Windows Server 2003 R2 running Terminal Services

September 3, 2008 Leave a comment
  • System Notes: Mac Pro, OS X 10.5, Microsoft RDP Client for Mac 1.0.3 and 2.0

Error Message: You were disconnected from the windows-based computer because there were problems during the licensing protocol. Try reconnecting to the Windows-based computer or ask your administrator if the license is properly configured.

Recently, we retired our old, outdated Windows 2000 Terminal Server, and replaced it with a Windows Server 2003 R2 server running Terminal Services. Terminal services are used for remote access only, not for application virtualization or anything extensive like that. We have three Mac clients in the office which also use terminal services for access to a Windows-only database application. This is where the problem came in. With the new terminal server, we reset the licensing database on our existing Licensing Server, which was running on one of our domain controllers. All three of the Mac clients started getting the above listed error message, even though there were plenty of licenses on the licensing server (15 total, to be exact).

After searching around the web, and finding lots of references to this being a “temporary license” not being issued, I eventually stumbled across this link, which led me to checking the directory permissions on Users/Shared/Microsoft/RDC Crucial Server Information/RDC GLOBAL DATA for the logged in Mac user, who was an Administrator on the Mac. We did originally have version 1.0.3 of the RDP client on this Mac, and we had upgraded it to the release version 2.0. The security permissions on this folder were not set to full for the user, and once they were corrected, the problem with the login went away. I still do not understand why the Administrator privileges were not correctly applied on this folder in the first place.

Advertisements