Mac Remote Desktop Licensing Error
Contents |
Please enter a title. You can not post a blank message. Please type your message and try again. ochieman2000 Level 1 (0 points) Q: RDP to Windows Server 2008 License Error
You Were Disconnected From The Windows-based Computer Because Of Network Problems
ERROR"You were disconnected from the Windows-based computer because of problems during the licensing protocol error remote desktop licensing protocol"I have scoured the Internet and have read it can be fixed...but no one has given me mac remote desktop you were disconnected from the windows based computer a working fix. I have tried many fixes but still no luck =(.Anyone know a FUNCTIONING fix for 10.7 and or 10.8I am using http://www.microsoft.com/mac/remote-desktop-client (the latest version) to connect
Cord Download
to Windows Server 2008 R2 Standard. Running RDS with a 5 User CAL. No Active Directory just basic accounts as the local IT team hasn't a clue how to use AD and I am a thousand miles away. OS X Mountain Lion (10.8), MAC OS X 10.7 Posted on Sep 10, 2012 11:03 AM I have this question too Close
Microsoft Remote Desktop
Q: RDP to Windows Server 2008 License Error All replies Helpful answers by Templeton Peck, Templeton Peck Sep 10, 2012 7:25 PM in response to ochieman2000 Level 9 (62,070 points) Sep 10, 2012 7:25 PM in response to ochieman2000 Your question has nothing to do with Apple Remote Desktop..the focus of this forum, and Apple's application for managing Macs on a network. Please post your question on Microsoft's own forums for their Mac software: http://answers.microsoft.com/en-us/mac Helpful (0) Reply options Link to this post by @dewarchris, @dewarchris Nov 20, 2012 7:04 AM in response to ochieman2000 Level 1 (0 points) Nov 20, 2012 7:04 AM in response to ochieman2000 This link was referenced as the fix from the Microsoft forumhttp://social.technet.microsoft.com/Forums/en-ZA/winserverTS/thread/8e28b0af-b37 4-4ca0-a255-5fd854bdc7fahttp://www.mydanat.co.uk/blog/ Helpful (0) Reply options Link to this post by Trane Francks, Trane Francks Dec 10, 2012 2:43 AM in response to @dewarchris Level 2 (230 points) Dec 10, 2012 2:43 AM in response to @dewarchris @dewarchris wrote:This link was referenced as the fix from the Microsoft forumhttp://social.technet.microsoft.com/Forums/en-ZA/winserverTS/thread/8e28b0af-b37 4-4ca0-a255-5fd854bdc7fahttp://www.mydanat.co.uk/blog/I can confirm that the first link carries the solution. Se
security, Windows Server 2008, Windows Server 2012 ≈ 2 Comments TagsRemote Desktop Connection for Mac, Remote Desktop Services Have you ever wondered why your Remote Desktop Connection on your Mac works well on one system but not on another? I was testing out my connectivity to some of my customers' network using Remote Desktop Connection on my MacBook Pro. This used to work on one of their environments but now it doesn't. I was under the impression that there must be something that changed on my system. So I did a quick check but couldn't find anything that has changed on my MacBook Pro (it simply means that I rely so much on VMs that my host machines - whether PC or Macs - don't get changed that often.) https://discussions.apple.com/thread/4282799?start=0 What's even more frustrating is that it works on one environment but not on another. This clearly means that there must be something that was changed on my customer's environment. After asking a bunch of questions, it appears that they have upgraded their server operating system from Windows Server 2003 to Windows Server 2008 R2. Since Windows Server 2008 R2 is secure by default, some of the security policies in place may be preventing the Remote Desktop Connection for Mac client from https://bassplayerdoc.wordpress.com/2013/02/12/how-to-fix-your-remote-desktop-connection-for-mac/ establishing a connection. But here's where my confusion lies. The error message does not tell me anything related to those security policies. You were disconnected from the Windows-based computer because of problems during the licensing protocol. I mean, seriously, how does that error message help me? The reason I ask is because I have configured a Windows Server 2008 R2 Terminal Services server in the past and I was able to connect from a MacBook using the Remote Desktop Connection for Mac client. Because I cannot do anything on the server to fix this issue, I decided to dig deeper (a.k.a do a Google search.) It seems that there are a lot of people who are experiencing this same issue. A very popular forum post regarding this issue is from Microsoft TechNet where the thread kept going for more than a year. Somebody pointed out a Microsoft KB article that outlines the steps that you need to do on the Terminal Server. As I mentioned, this is not the path that I can take unless I'm the server administrator. One thing did work for me: v2.1.2 of the Microsoft Remote Desktop Connection for Mac. I have searched for it on the Microsoft Download Center but could not find it anywhere. Technically, this is still an unsupported product so be aware that you might not get any help from Microsoft when using this. Install it on your Mac, run it and test your conne
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more http://stackoverflow.com/questions/12357178/rdp-from-mac-os-x-to-windows-server-2008-r2-license-error about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users http://mydanat.co.uk/blog/?p=59 Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up RDP from MAC OS X to Windows Server 2008 R2 License Error up vote 2 down vote favorite 2 ERROR "You were disconnected from the Windows-based computer because remote desktop of problems during the licensing protocol" I have scoured the Internet and have read it can be fixed...but no one has given me a working fix. I have tried many fixes but still no luck =(. Anyone know a FUNCTIONING fix for 10.7 and or 10.8 I am using http://www.microsoft.com/mac/remote-desktop-client (the latest version) to connect to Windows Server 2008 R2 Standard. Running RDS with a 5 User CAL. No Active Directory just basic accounts as the local mac remote desktop IT team hasn't a clue how to use AD and I am a thousand miles away. windows osx rdp share|improve this question asked Sep 10 '12 at 18:08 Dan 38118 Can you use Remote Desktop from a Windows client to the server in question? Have you tried an alternative client such as FreeRDP? –Harry Johnston Sep 10 '12 at 20:13 add a comment| 4 Answers 4 active oldest votes up vote 3 down vote Did you try Thinomenon RDC for Mac? It properly supports redirect token, which could be the problem. share|improve this answer answered Oct 23 '12 at 11:05 Arif Danani 312 add a comment| up vote 1 down vote I found these 2 links which seems to have fixed the issue (Hope it's not the same you tried !!!), esp follow vezard & Martijn Huizer's response: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/8e28b0af-b374-4ca0-a255-5fd854bdc7fa http://support.microsoft.com/kb/2477133 Hope it solves your issue ! share|improve this answer answered Sep 10 '12 at 18:20 Ron 5972722 add a comment| up vote 0 down vote Microsoft has released a new RDP client in the app store. So far It seems to work. share|improve this answer answered Nov 6 '13 at 19:02 user2765858 363 I updated the software and it still gave me the same error. Then I found the CoRD solution (mentioned below) –gnB Nov 21 '13 at 18:57 add a comment| up vote 0
post here http://social.technet.microsoft.com:80/Forums/en-US/winserverTS/thread/8e28b0af-b374-4ca0-a255-5fd854bdc7fa We have been having issues with getting Mac's to run on RemoteApp. We are the only people in the world at mydanat.co.uk that know how to get Teredo Tunnels to run behind NAT devices. So why are we involved? A customer uses DirectAccess to access RemoteApp services like Sims .Net on a Mac, well they did until the message popped up. So as our motto is lets not wait around for Microsoft to fix this, we fixed it in 2 days after a lot of research on the Internet. Error: "You were disconnected from the Windows-based computer because of problems during the licensing protocol" Cause: There is currently a bug in RDC 2.1.1 that does not allow the client to download the correct licensing info from a 2008 R2 license server. This means that after the standard 90 days the clients will get the error message above even though windows based connections will still work correctly. This is because when a user first runs the RDC client it sets up a folder structure that only contains read & wright access rights for the currently logged on user. All other users are read only. This means no other users can download the correct file when available. Fix: This is a simple fix but also a little headache, as at this moment to rush this fix out onto the Internet we have not found a way to automate the process. Please leave useful comments to help automate this fix. Go to Macintosh HD > Users > Shared > Microsoft. Go into RDC Crucial Server Information and you should see a folder and no files Go Back to Microsoft folder Click on "RDC Crucial Server Information" and then click file > Get Info Under Sharing & Permissions select "everyone" and change it to "Read & Write" Run your RDC connection again and it will start working fine. You will now notice a file in RDC Crucial Server Information folder that was not there before Notes: If there was a file in there back it up and try trashing it then run through the fix again. You may also need to set Read and Write for the