Terminal Server Licensing Server gets disconnected

[Guest]

I have a W2K3 server running Terminal Server. I setup the Licensing Server on another server with 25 device licenses and is active. It has been working for about 2 months, but yesterday I tried to connect another workstation and an error came up indicating that there were no Terminal server license server available to provide a license

When I go to my server and start Terminal Server licensing, it says that no TS Licensing server is available on the domain or Workgroup, however I type the name of the Licensing server and it shows me all the licences. If I exit and start the tool again it says the same thing. I added it to the registry, but still no one new can connect. There are still 11 licenses available

 

[Matthew Harris [MVP]]

Check you added it to the regsitry, did you follow this
protocol:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;279561&Product=winsvr2003

Also, did you try hardcoding the IP, or the NetBIOS name,
or the FQDN of the TS licensing server into the registry?

-M

-----Original Message-----
I have a W2K3 server running Terminal Server. I setup the

Licensing Server on another server with 25 device licenses
and is active. It has been working for about 2 months, but
yesterday I tried to connect another workstation and an
error came up indicating that there were no Terminal
server license server available to provide a license.

When I go to my server and start Terminal Server

licensing, it says that no TS Licensing server is
available on the domain or Workgroup, however I type the
name of the Licensing server and it shows me all the
licences. If I exit and start the tool again it says the
same thing. I added it to the registry, but still no one
new can connect. There are still 11 licenses available.

 

[Guest]

I did it as the article indicates and still doesn't work. However, I think that it may be an error on the article, because it says to put the server name as a new key. Shouldn't it be a value on a key or something like that

Still can't find a licensing server, even when I connect to it manually.

 

[Guest]

The Article leaves a little bit of detail out, but after reading it carefully a few times, I found that you need to put the ip address of you license server in the default key for the NETBIOS name. After that, it worked. Thanks for your help.

 

[angryblack]

I am just a little confused so i am hoping you come back
to the post and will be able to help me. I did exactly
what was specified on the client machines and it did nto
work. Also win2000 clints do not have the TERMSERVICE
key. The thing that is also puzzling is that there is a
win2000 machine that can connect to these 2003 servers
however no other one can. Help Please

-----Original Message-----
The Article leaves a little bit of detail out, but after

reading it carefully a few times, I found that you need
to put the ip address of you license server in the
default key for the NETBIOS name. After that, it worked.
Thanks for your help.

 

[Vera Noest [MVP]]

Since the beginning of this thread is gone, I have to do some
guessing, but it seems this is about hardcoding the address of the
Licensing Server in the registry.

Note that this must be done on the Terminal Server, not on the
clients! The clients *never* talk directly to the LS, all
communication is between the TS and the LS and between the TS and
the clients.
Note also that the exact format of the registry change depends on
if you are running W2K or 2003!

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561