Thanks Vera. I thought so too. I guess when the guy set up the
machine with W2k server. He activated terminal service licenses
workgroup). But, the weird thing is that it has been working
for a year and a half like this. The other question will be: If
Post by Vera Noest [MVP]No, you should not have to hardcode the DefaultLicenseServer, I
only mentioned this because it is part of the troubleshooting
tips that you said you followed, and those are for 2003.
"we don't have a license server on any Domain Controller"
If so, that's your problem. You must install and activate a TS
Licensing Server, and it must run on one of your Domain
Controllers. As soon as it is activated, it will issue free TS
CALs to your W2K Pro and XP Pro clients, from the built-in pool
of licenses from the Licensing Server. All other clients need a
purchased TS CAL.
Windows 2000 Terminal Services Licensing FAQ
http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsf
aq ..asp
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Hi Vera,
Thanks for your response on this. The event ID is 1004 which
means the server failed to contact the license server to
renew a license. However, the event was generated only when
a client failed to connect (the one got the below error). If
a client was successfully connected, this event won't be
generated.
I didn't hardcode the "DefaultLicenseServer" and there is no
such key in the registry. Would it be better to specify one?
I also found that the key "UseLicenseServer" set to '0' that
means not being used. But, we definitely installed a
certificate for the server itself. This server is part of a
domain and we don't have a license server on any Domain
Controller. The person who set this up no longer with our
company and I'm not sure how he installed the licenses.
Any suggestion will be highly regarded.
Thanks,
Dom
Post by Vera Noest [MVP]Which Events do you see in the EventLog on the Terminal
Server?
Note: I hope that you didn't follow the instructions about
hardcoding the name of the Licensing Server into the
registry of the Terminal Server.
The instructions on the page that you found are specific for
Windows 2003.
239107 - Establishing Preferred Windows 2000 Terminal
Services License Server
http://support.microsoft.com/?kbid=239107
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by DHhi,
My clients tried to connect to our TS (a W2K server with
SP4) using RDP client. On 2 identical built machines
(e.g. Dell GX280) and both running WinXP SP2, one can and
"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."
I found from MS
http://www.microsoft.com/resources/documentation/WindowsServ/2
Post by Vera Noest [MVP]3
Post by DH/standard/proddocs/en-us/Default.asp?
url=/resources/documentation
Post by DH/WindowsServ/2003/standard/proddocs/en-
us/mstsc_tshoot_lic.asp
Post by Vera Noest [MVP]Post by DH, which got the exact error message. But, after tried the
solution, problem still there. I'm just wondering anyone
can help.
Thanks,
Dom