We help IT Professionals succeed at work.

The remote session was disconnected because there are no Terminal Server license servers available to provide a license

sammydlc
sammydlc asked
on
1,506 Views
Last Modified: 2008-08-06
I have the following setup.
1 Windows 2003 Terminal Licensing Server issuing licenses.
3 Windows 2003 Terminal Servers running application mode.
Recently one of my users started receiving this error message when trying to connect to any of the TS.
"The remote session was disconnected because there are no Terminal Server license servers available to provide a license"
I have over 300 users and none have the same error except this one. I deleted the MsLicensing Reguistry entry on the client's computer to try to refresh the temporary license but no luck. If I go to the licensing server I see this computer listed under the Temporary License but there is no way to deleteing direclty on the Licensing Server.
Any help is really appreciated
Comment
Watch Question

This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Ok this is what I did to solve the issue.
I logged into my Terminal Server and opended the Licensing Server MMC, (Start-Programs-Administrative Tools- Terminal Licensing).
I noticed that when it opened, it dscaned for LS but did not find any. I then clicked on ACTION - CONNECT and supplied the correct LS. It connected without any problems.
I closed the MMC and reopened and had the same issue where the LS was not identified.
I then edited the registry to specify my TS where my LS was.
On the TS went to REGEDIT-
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001Services\TermService\Parameters\LicenseServers\
Here I created a new KEY and named it as my LS.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001Services\TermService\Parameters\LicenseServers\LICENSESERVERNAME
Closed regedit and opened it.
WALLA, THE TS now could See the LS.
Then I went to the client and Deleted the MSLicensing registry key
Retried and the client was able to connect.
 
Thanks for all your help.

Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.