Link to home
Start Free TrialLog in
Avatar of gulfcoastnetworking
gulfcoastnetworking

asked on

MAC RDC connection problem

Scenario: TServer running Server 2012. All MS clients connect. MAC RDC gives the following error message "You were disconnected from the Windows-based computer because of problems during the licensing protocol".

Have downloaded and installed RDC for MAC V2.1.1 with no change

MAC running 10.8.3 Mountain Lion
Avatar of s3e3
s3e3
Flag of Canada image

Did you install and activate a terminal server licensing server in your domain ?

Here is a link for more details.
http://technet.microsoft.com/en-us/library/cc754309%28v=ws.10%29.aspx
ASKER CERTIFIED SOLUTION
Avatar of strung
strung
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of gulfcoastnetworking
gulfcoastnetworking

ASKER

@s3e3 Yes, MS licensing is set up and active. All MS clients connect without an issue.

@strung. Thanks, let me look those over. I'm not against using a third party client but this is an issue that I've found, while researching on the web, affects Server 2008 R2 and now 2012. Would prefer to solve it using the native client if possible, However I'm also a realist and know trying to get the two behemoths (MS and Apple) to move may be impossible.
Actually many people who have tried both prefer CoRD.
The link you gave me I had been looking at before, I just ran into search fatigue last night and didn't get to the bottom of the thread. "Network Touch" had a link to a V2.1.2 RDC client. I'm going to install it and test it. If it solves the problem great, if not we'll punt and go to one of the 3rd party apps. I'll let you know. Thanks.
Just be aware of the fact that the v. 2.1.2 that you are downloading does not seem to be an official MS release. It is not available on their website.
I noticed that, but "Network Support" said  "This is direct from Microsoft support.  I hope Microsoft does not get mad at me for posting this.  After all, this will be released in a near future update." so I'm hopeful. And it appears to have solved the issue for some others. Apparently since he posted that last September and it's now been over 6 months MS "near future" updates are different that what perhaps you and I categorize as "near future".
And no joy on the 2.1.2 version so coRD it is. Thanks strung.
Thanks for your follow ups on the issue. He's up and running and as happy as an Apple user can be running MS products.