Home > Remote Desktop > Remote Desktop Connection Licensing Protocol Error Mac

Remote Desktop Connection Licensing Protocol Error Mac

Contents

In RD Session Host Configuration (tsconfig.msc) is the licensing mode set to Per User? Delete the files in theUSERS/SHARED/MICROSOFT/RDC Crucial Server on the OSX machine. 2. Edited by Stephen Duhrke Wednesday, September 19, 2012 7:51 PM Wednesday, September 19, 2012 7:50 PM Reply | Quote 0 Sign in to vote I tried setting to security to "RDP 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 http://supercgis.com/remote-desktop/remote-desktop-licensing-protocol-error-on-mac.html

I understand your concern about using software that you really do not know where it came from, but in this case it was straight from Microsoft. SoI had to remove these keys on both servers,and keep RDS powered off while reactivating the licensing server. Your problem is still the same in my view. Hope this helps Make sure the macs and the server are using the same connection security settings. (2008 R2 defaults to high, stops XP clients connecting for example) What do you

You Were Disconnected From The Windows-based Computer Because Of Network Problems

I've exactly the same problem with a W2k8 R2 with RDP 7.1 and licensing is running on the same machine. NOTE: Perform the following procedure on each of the terminal servers. I have migrated the RDP license server to 2008R2 from 2012 with no luck. First thing to try though is install the RDC under a domain admin account and always use that account for testing.

because of problems during the licensing protocol" * Connecting with CORD works * Connecting to a Windows Server 2008 with TS configured for Administration mode works! * There is NO directory After the Server Manager console is displayed, select the Configure Remote Desktop task. The solution for our users using OSX was to have them install 2X which is a free RDP client available on the App store for OSX. Microsoft Remote Desktop Go to Macintosh HD > Users > Shared > Microsoft.

Please create a Per User Usage report, right-click on the report and choose to Save as a .csv file, and then open the file in Notepad. Licensing Protocol Error Remote Desktop As soon as I apply the RDS licenses (per User mode) then I’m unable to connect anymore -- Yes this is because when you install RDC on the Mac it automatically Thanks NetworkTouch! https://community.spiceworks.com/topic/253168-mac-microsoft-remote-desktop-licensing-error Microsoft, you need to resolve or patch your own Mac Remote Desktop Client to work with Win2008 R2 SP1 with "real" licenses!Network Touch Thursday, September 20, 2012 7:49 PM Reply |

One thing did work for me: v2.1.2 of the Microsoft Remote Desktop Connection for Mac. Event Viewer>Windows>Security logs - reports 4 Audit Successes: Audit Success 13/11/2012 2:27:48 PM Microsoft Windows security auditing. 4634 Logoff Audit Success 13/11/2012 2:27:47 PM Microsoft Windows security auditing. 4624 Logon Audit folder eventually. If enough people open cases, perhaps those that do will reconsider that decision.

Licensing Protocol Error Remote Desktop

No one there seems to know how to fix this. saved my day.. You Were Disconnected From The Windows-based Computer Because Of Network Problems What the response from MS? Mac Rdp Problems During The Licensing Protocol In my case 2.1.2 didn't work until I completely replaced the 2.1.1 version (look back in the posts a bit).

Any ideas? http://supercgis.com/remote-desktop/remote-desktop-client-error-licensing-protocol.html Reply Tony said: March 23, 2015 at 10:01 PM I know this is an old thread, but it is still among the top listings for what is a current issue. Now why is this version not on microsoft.com/mac/downloads section yet?. Friday, August 03, 2012 2:36 PM Reply | Quote 0 Sign in to vote Same here. Cord Download

Wednesday, June 13, 2012 11:40 AM Reply | Quote 0 Sign in to vote I have fixed this for you You can find the fix here http://www.mydanat.co.uk/blog Please leave usefull comments All test done with mac admin. Steve Monday, August 13, 2012 7:52 PM Reply | Quote 0 Sign in to vote @Vezard @Martijn Huize Thanks for the tips - life saver if it works. navigate here What does not work is to connect to a W2K8R2 server that has 120-D grace period enabled, then apply RDS licenses.

Posted 07 Aug 2012 at 11:12 pm ¶ Chris Hawver wrote: I too am still having this problem. Type exported- Certificate in the File name box, and then click Save. No problem.

I'm using OS X 10.5.8, This issue is the same with 10.6 and 10.7.

reboot… and I connected to server by MS RDC 2.1.2 I didn’t try 2.1.1 good luck… Posted 08 Jan 2013 at 5:48 pm ¶ I had this problem on I see this problem with the terminal server licensing is not functioning.  When the licensing services isn't working temporary licenses are issued to Windows (XP/Vista/7) Home and Mac clients.  Windows pro Works great. Edited by _TC Wednesday, August 15, 2012 12:52 PM Wednesday, August 15, 2012 12:51 PM Reply | Quote 0 Sign in to vote Worked for me 2 :)))))) Thursday, August 16,

Frank Kyosho Fallon Zen Mt. Only 2 users can log in at a time! Sincerely, Salman Maqsood Saltech Systems Proposed as answer by Saltech Systems Friday, May 31, 2013 4:49 AM Edited by Saltech Systems Friday, May 31, 2013 4:50 AM Type Friday, May 31, http://supercgis.com/remote-desktop/remote-desktop-licensing-protocol-error-vista.html Demers on Aug 23, 2012 at 3:54 UTC | Windows Server 0Spice Down Next: DNS Cleanup question Microsoft 493,697 Followers - Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP

Still no fixes. Monday, January 07, 2013 3:35 PM Reply | Quote 0 Sign in to vote THANKS!!!!! By the way disabling the windows firewall quite often does not solve the problem. It worked great for me!David La Monaca Press4Web Friday, September 21, 2012 7:14 PM Reply | Quote 1 Sign in to vote Not a day too early.

Weird!. Binding to the AD = fixed. Very frustrated with MS Support. Once they understood the difference between THEIR devices and HOSPITAL devices (and then applied these updates to THEIR systems) then they began working just fine.

Also see comments below for extra help Comments 22 Terry wrote: Doesn't work for me. The windiows-clients still running fine. Has MS released a known issue bulletin on this? Well, for my user that just deposited her Mac on my desk... 0 Pimiento OP douglasdavis Jun 5, 2015 at 3:12 UTC 1st Post After spending a couple

This has to do with permissions, thou it's not a problem with your configuration.