MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

The terminal server cannot issue a client license.

Page 1 of 1
Next:  Terminal Servers - General: Terminal Server in DMZ  
Author Message
chadnewman




Joined: Jan 20, 2010
Posts: 2



(Msg. 1) Posted: Wed Jan 20, 2010 3:08 pm
Post subject: The terminal server cannot issue a client license.

I have a client that I cannot connect to our 2000 Terminal Server.
They had connected fine from this machine before.
When they connect they get an error about the licensing protocal and in the error log on the server I see:

The terminal server cannot issue a client license.

On their computer I deleted the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing entry in the registry. One kink was 2 users were logged into the workstation (switching users) when I did the registry change.

What else am I missing? Other clients are connecting fine and other computers at their site are connecting fine. Do I have to reactive the Licensing Server?

Thanks,

Chad
Back to top
Send e-mail Login to vote
chadnewman




Joined: Jan 20, 2010
Posts: 2



(Msg. 2) Posted: Fri Jan 22, 2010 6:28 pm
Post subject: Re: The terminal server cannot issue a client license. [Login to view extended thread Info.]

Discovered the solution. I failed to mention this is a Vista Computer.
Found the answer under:

http://support.microsoft.com/kb/187614

Here is what I had to do:

If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message:
An Error occurred in the Licensing Protocol
To resolve this problem, right-click the Remote Desktop Connection shortcut, and then click Run as Administrator. By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.

Thanks,

Chad
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register