Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Remote Desktop : The remote computer disconnected the session because of an error in the licensing protocol

Posted on 2009-07-08
6
Medium Priority
?
699 Views
Last Modified: 2012-05-07
I normally have no issues remoting to our only server/domain controller. Today I notice the following issue

Remote Desktop : The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator
0
Comment
Question by:TALYOFFE
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 1

Accepted Solution

by:
etchy74 earned 1500 total points
ID: 24806136
Have you tried the below steps from Microsoft?  http://technet.microsoft.com/en-us/library/cc756826(WS.10).aspx

The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.

Cause:  The terminal server might not be able to locate the license server.

Solution:  Perform the following steps:

   1. Verify that the license server is correctly installed.
   2. Verify that the Terminal Server Licensing service is running on the license server.
   3. Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
   4. On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.

See also:   Install Terminal Server Licensing; Set preferred Terminal Server license servers; Terminal Server license server roles

Solution:  If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:

   1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
   2. Click MSLicensing.
   3. On the Registry menu, click Export Registry File.
   4. In the File name box, type mslicensingbackup, and then click Save.
   5. If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
   6. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
   7. Close Registry Editor, and then restart the computer.

When the client is restarted, the missing registry key is rebuilt.

Caution

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

See also:  Removing Terminal Server Licenses From an RDP Client (http://go.microsoft.com/fwlink/?LinkId=38560)
0
 

Author Comment

by:TALYOFFE
ID: 24806485
I believe it should be correctly installed as I have not experienced this issue before. I have been using RDP to this server for 6 months now with no issues.
0
 
LVL 1

Expert Comment

by:etchy74
ID: 24806782
I have had this error before and doing their solution (registry edit on the client to rebuild the MSLicensing key) fixed it.  Did you give that a shot?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:TALYOFFE
ID: 24806878
Yes I did try this. This is happening on multiple workstations. Not just on mine.
0
 
LVL 1

Expert Comment

by:etchy74
ID: 24806986
Oh ok, I thought it was just one station.

Are there any relative errors in the Application log on the server?  
0
 

Author Comment

by:TALYOFFE
ID: 24807538
nothing in event viewer except a few exchange related errors
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Suggested Courses

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question