My Vote is with Kirbies (btw well done on the directaccess stuff, a very interesting read. Monday, September 10, 2012 6:15 PM Reply | Quote 0 Sign in to vote Has anyone found a solution for this yet? I've exactly the same problem with a W2k8 R2 with RDP 7.1 and licensing is running on the same machine. This means the user has permission to log on. http://thesweepdoctor.com/remote-desktop/terminal-server-licensing-error-31.html
After setting mode via RD Session Host Config, close and then reopen RD Session Host Config and check that it still says Per User. 2. Cord does work, just not the Microsoft remote desktop client version 2.1.1. My only guess is, it has to do with something in RemoteFX since this is the major new feature with RDP 7.1. I'm going to test different methods of connecting to this server, hopefully I will luck into something. https://social.technet.microsoft.com/Forums/windowsserver/en-US/8e28b0af-b374-4ca0-a255-5fd854bdc7fa/rdc-for-mac-cannot-connect-to-ts-server-with-error-message-you-were-disconnected-from-the?forum=winserverTS
Please understand that Microsoft Support does not make the decision on whether a fix is released. It will become a big issue with a lot of Mac clients.Network Touch Tuesday, September 18, 2012 1:27 PM Reply | Quote 0 Sign in to vote any Microsoft techs monitoring We have tried every different version of RDC and nothing works. 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
Click on “RDC Crucial Server Information” and then click file > Get Info Under Sharing & Permissions select “everyone” and change it to “Read & Write” New Remote Desktop Client didn't Possibly the account you log on to the Mac does not have enough security to contact the TS server. They sent me the beta version of the Mac RDP client. Cord For Mac So far It seems to work.
See, the way I see it is that I can connect using RDC to a W2K8R2 that is fully licensed, which means that I don't have any local security issues on Licensing Protocol Error Remote Desktop So that meant continuing to use the, older, buggier 1.0 release OR … well, there is no "or" because the client would just stop working with the error message, "You were yes, CoRD works . 5. Read More Here No more "..problems during the licensing protocol." and still no crash since 8 days.
All rights reserved. I've tried recreating them myself, i've tried reinstalling the app, i've tried the registry delete and reactivate on the server.... This will be succesful but you will still need to setup the security structure So, a Microsoft or Apple issue? I don't think it's the real problem because all works fine for Windows Client or for rdp mac when we remove TS Role.
Have you got active licences on there or are you still using the 90 tempory ones? https://bassplayerdoc.wordpress.com/2013/02/12/how-to-fix-your-remote-desktop-connection-for-mac/ Sunday, February 26, 2012 8:17 PM Reply | Quote 0 Sign in to vote I'm having the same problem with error "You were disconnected from the Windows-based computer because of problems You Were Disconnected From The Windows-based Computer Because Of Network Problems I’m stumped why that would make a difference, unless 2.1.2 was using the old framework libraries in the 2.1.1 ../Contents/Frameworks. Mac Remote Desktop You Were Disconnected From The Windows Based Computer Another machine running Windows Server 2008R2 as client will connect fine.
Is anyone here using a 2012 license server? weblink Simple as that. The error message does not tell me anything related to those security policies. Microsoft RDC does not (license error). Microsoft Remote Desktop Mac Connection Refused
no temp per device cal has been issued. 4. You must have a file in that folder). 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. navigate here If it fails change the permissions on the folder using this command.
After all, this will be released in a near future update. Works great. For example, if you purchased/installed Per User RDS CALs, make sure that it is set to Per User. 3.After verifying the above is correct, please try to connect from a mac
Maybe TS Role modify the security but where exactly? If there is something inlocal security Policy > Local Polices > Security Options. Proposed as answer by John.Horst_ConnectICC.com Wednesday, January 29, 2014 4:10 PM Wednesday, June 06, 2012 2:22 PM Reply | Quote 1 Sign in to vote Same problem here. Browse other questions tagged windows osx rdp or ask your own question.
Nick Wednesday, July 11, 2012 1:13 PM Reply | Quote 0 Sign in to vote We have the same problem. Please help. May make sense from a licensing standpoint from Microsofts POV but should not be this hard to find an answer. his comment is here Id love to know what to change as I have now read nearly each ones description but I am 1000 miles away from the server anddon'tlike the idea of randomly testing
This really blows as I have no other way of fixing this. Windows users are up and functioning. Now why is this version not on microsoft.com/mac/downloads section yet?. 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,