Mac Rdp License Protocol Error
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 MAC you were disconnected from the windows-based computer because of network problems cannot connect to TS server with error message "You were disconnected from licensing protocol error remote desktop the Windows-based computer because of problems during the licensing protocol". Windows Server > Remote Desktop Services (Terminal cord download 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
Microsoft Remote Desktop
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 User. 3.After verifying the above is correct, please try to connect from
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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to https://www.experts-exchange.com/questions/28247878/OSX-Mac-RDP-Clients-cannot-connect-to-Terminal-Server-2012-because-of-problems-during-the-licensing-protocol.html Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > OSX Mac RDP Clients cannot connect to https://www.adminsys.ch/2013/08/21/remote-desktop-connection-mac-os-refuses-connect-problems-licensing-protocol/ Terminal Server 2012 because of problems during the licensing protocol Want to Advertise Here? Solved OSX Mac RDP Clients cannot connect to Terminal Server 2012 because of problems during the licensing protocol Posted on 2013-09-24 protocol error Windows Server 2012 Remote Access Mac OS X 2 Verified Solutions 5 Comments 6,324 Views Last Modified: 2013-10-02 Last month I replaced our old windows server with Windows 2012 Terminal Server. After the install, I installed Microsoft Remote Desktop 2.1.1 on all of my Apple Mac OSX 10.8 iMacs. All was working perfectly. After what I think is 45 days all my Apple Macs suffered the same problem when trying mac rdp license to establish a RDP connection. See attached Image: "You were disconnected from the windows-based computer because of problems during the licensing protocol." If I try connecting from a spare PC using Remote Desktop and the same user credentials I am able to log in fine. This means the user has permission to log on. The Terminal Server is refusing connections from all my Apple Macs. If this is really a Licensing Protocol issue, I wonder if the problem is caused by temporary Device CALS expiring? I am fully licensed with plenty of CAL's, It should be applying device cal's to Apple Macs. I need help diagnosing the problems here. Is there a log file I can read on the Terminal Server that tells me exactly why it refuses connections from my Apple Macs? Is there a way to flush out the device cals or check to see if they are allocated properly to my Apple Macs? Thanks mchallinor MacRDP.png 0 Question by:Mchallinor Facebook Twitter LinkedIn Google Active 2 days ago Best Solution byMchallinor For anyone else searching this problem I can summarize: The problem circulates around a special folder on the Mac: /users/Shared/Microsoft/RDC Crucial Server Information This folder and files are Go to Solution 5 C
Post navigation ← Previous Next → Remote Desktop Connection on Mac OS X refuses to connect because of problems during the licensing protocol Posted on 21/08/2013 by Florent B. — No Comments ↓ Today, we were blocked by a stupid message from Microsoft Remote Desktop Connection 2 on a user workstation's. RDC was showing this message : You were disconnected from the Windows-based computer because of problems during the licensing protocol. The problem was that the "windows-based" computer is a Mac OS X Terminal Server and there are enough licenses for dozens more users. The problem was system wide, others users on the same computer were affected by this error but the same user on another workstation was working fine. After some experimentation on the workstation, we noticed that the problem was from files in the directory "RDC Crucial Server Information" in the Shared directory. Simply remove the complete Microsoft folder and now RDC is working again. /Users/Shared/Microsoft This entry was posted in Others and tagged Mac OS X, Remote Desktop Connection by Florent B.. Bookmark the permalink. Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Prove that you are a human! Primary Sidebar Widget Area Recent Posts "Apache Directory Studio" hangs at 14% when connecting to an LDAP server HPE OneView 2.0.7: “Unable to retrieve asset tag information from the iLO.” Quick way to bind CentOS 7/Red Hat Enterprise Linux 7 to Active Directory vSphere ESXi upgrade is really slow (About to install…) vSphere Web Client has slow performances… Update to 5.5 Update 3! Ads Popular PostsInstall Reposado with Margarita on CentOS / Red Hat…When installing ClamAV f