RDS and TS server connection occurred an error

Asked By 10 points N/A Posted on -
qa-featured

Hi,

I have Mac OS X installed and when trying to connect RDC for MAC to TS server I get an error. Any suggestions?

You were disconnected from the Windows-based computer because of problems during the licensing protocol

You were disconnected from the Windows-based computer because of problems during the licensing protocol.

Try reconnecting to the Windows-based computer or contact your administrator.

SHARE
Answered By 566215 points N/A #176379

RDS and TS server connection occurred an error

qa-featured

You are actually not the only one having this error when connecting to a Windows-based computer using Remote Desktop Connection. The reason why you receive the error “You were disconnected from the Windows-based computer because of problems during the licensing protocol” is because of a bug in RDC 2.1.1. This bug prevents the client from downloading the exact licensing information from a 2008 R2 license server.

Once the standard 90 days have passed, clients that are on Mac OS X will now get the above error but Windows-based connections will nonetheless work even if this happens. The reason is that when a user launches the RDC client for the first time, it sets up a structured folder.

This folder will only hold rights for read and write access for the presently logged in user and the rest of the users are set to read-only. This results on preventing other users from downloading the right file when available. This method already works on many users though there are still those failed to fix it.

Navigate to Macintosh HD, Users, Shared, Microsoft then RDC Crucial Server Information. It should only display 1 folder and no other files. Navigate back to Microsoft directory, click RDC Crucial Server Information folder then click File and then Get Info. In Sharing & Permissions, select Everyone then change it to Read & Write.

After this, run your RDC connection and it should work fine now. After doing this action, a file will be generated in the RDC Crucial Server Information folder which was not present before. In case this folder already has a file in there even before you started the procedure, backup the file and store it somewhere else, delete it after the backup, and then start the procedure.

You may also be required to set the Read & Write permission for the Everyone group for each of the folders inside Microsoft directory. If in case you don’t see the Microsoft folder inside Shared folder, just run the RDC client then connect to the server. It’ll work but you are still required to setup the security structure.

Login/Register to Answer

Related Questions