Licensing Protocol Error Remote Desktop Mac
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: RDC for you were disconnected from the windows-based computer because of network problems MAC cannot connect to TS server with error message "You were cord download disconnected from the Windows-based computer because of problems during the licensing protocol". Windows Server > Remote
Microsoft Remote Desktop
Desktop Services (Terminal Services) Question 1 Sign in to vote the mac clients are running RDC for mac version 2.1 and they cannot connect to Windows 2008 R2 TS server. They get the error "You were disconnected from the Windows-based computer because of problems during the licensing protocol". really appreciated if someone have a fix for this. thanks, /dan Wednesday, November 09, 2011 10:53 PM Reply | Quote Answers 4 Sign in to vote Hi, If possible, please try the new Microsoft Remote Desktop app, available in the Mac App Store: https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417 Getting Started with Remote Desktop Client on Mac http://technet.microsoft.com/en-us/library/dn473012.aspx Thanks. -TP Proposed as answer by Barbara Joost Monday, November 04, 2013 8:21 AM Marked as answer by TP []MVP, Moderator Wednesday, January 29, 2014 4:19 PM Friday, October 18, 2013 1:46 PM Reply | Quote Moderator All replies 0 Sign in to vote Hi, Please check the following: 1.On your RD Licensing Server, please open RD Licensing Manager (licmgr.exe) and verify that the server is activated, your purchased RDS CALs are installed, and there are RDS CALs available. You may install the RD Licensing Role Service on the same server as the RD Session Host Role Service if desired. 2.In RD Session Host Configuration (tsconfig.msc), please make sure that your RD Licensing server is Specified and the Licensing mode matches the type of RDS CALs you purchased. For example, if you purchased/installed Per User RDS CALs, make sure that it is set to Per U
comment When connecting with a Mac using RDP (Remote Desktop Protocol) on a Windows server, you might encounter a message saying "You were disconnected from the Windows-based computer because of problems during the licensing protocol". This has to do with permissions, thou it's not a problem with your configuration. This is a bug with RDC for MAC Version 2.1.1 Thou there is no solution until now, it is suggested to install https://social.technet.microsoft.com/Forums/windows/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 the hot-fix below RDC for MAC v2.1.2 (Early Build Hotfix) After installing the hot-fix, you will be able to connect to your Terminal Server. (17435) Post navigation Previous PostHow to: Manually purge Exchange server logs safelyNext PostFix: The Certificate Status could not be determined because the revocation check failed Leave a Reply Cancel reply http://www.noelpulis.com/fix-mac-rdp-disconnected-windows-based-computer-problems-licensing-protocol/ Your email address will not be published. Required fields are marked *Comment Name * Email * Website Categories Azure Cisco Exchange Hyper-V Lync Server MAC Microsoft Network Office 365 OpenText eDocs Outlook Powershell Smartphones SQL Tools Uncategorized VBScript VMWare Windows Yosemite Backup Tag Cloudactive directory antispam azcopy azure backup blacklist blocklist browser cannot open cisco cloud configuration connector domain controller error esxi exchange exchange 2007 exchange 2010 firefox fix free gpo import installation lync lync deployment mailflow migration modification netlogon office 365 office 2003 outlook powershell printer pst public folders router schema sql switch timeout usb wireless device Technical help and scripts for everyday issues of a sysadmin day Recent Posts How to export mailboxes to PST in Exchange 2010 How to: Setup Import Export role in Office 365 Fix: AzCopy.exe Could not finish the operation within specified timeout Fix: Azure RemoteApp GPO login scripts not working Fix: Azure AD Connect unexpected error on sign in Proudly powered by WordPress
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' https://bassplayerdoc.wordpress.com/2013/02/12/how-to-fix-your-remote-desktop-connection-for-mac/ 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.) What's even more frustrating remote desktop 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 establishing a connection. But here's where licensing protocol error 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 connectivity to a Windows Server 2008 (or higher) Terminal Server. NOTE: Please rem