New remote client not ablelogin W2K Terminal services after AD upg

[Guest]

Hi,

I have a Windows 2000 server running Terminal services/Citrix and also
running Terminal licensing server for itself. We have recently upgrade our NT
4 Domain to Windows 2003 AD. I found out that last week when a new remote
client (exisiting remote client no problem) try to login to Terminal/Citrix.
It just not working at all.
I tried to launch Terminal licensing server from that box but it did not
even find the terminal license server anymore, i checked the terminal
licenses service and it stopped and i was not able to start it. I got bunch
of this error message in event viewer from below....

Event ID: 1004
Source: TermService
Type: Warning
The terminal server cannot issue a client license.

Event ID: 1010
Source: TermService
Type: Warning
The terminal services could not locate a license server. Confirm that all
license servers on the network are registered in WINS\DNS, accepting network
requests, and the Terminal Services Licensing Service is running.

Also got these messages after server being restarted.

Event ID: 29
Source: TermService
Type: Error
Terminal Services Licensing can only be run on Domain Controllers or Server
in a Workgroup. See Terminal Server Licensing help topic for more
information.

Event ID: 7024
Source: Service Control Manager
Type: Error
The Terminal Services Licensing service terminated with service-specific
error 29.


Is anything to do with my Windows 2003 AD server upgrade? I did a quick
fixed by changing the registry of default licensing server to another Windows
2003 Terminal license server. The new remote client is able to login right
away. But we will be running short of Terminal licenses very soon. Since we
have 30 of Windows TSCALs in the Windows 2000 Terminal services. Does anyone
know why is doing that?

Thanks.
Mugen

 

[Vera Noest [MVP]]

Your own post already contains the answer to why this has happened:

Event ID: 29
Source: TermService
Type: Error
Terminal Services Licensing can only be run on Domain
Controllers or Server in a Workgroup.

As long as your W2K server was a member of an NT4 domain, it could
run the Licensing service (since the W2K Licensing Service
obviously could not run on the DC then). When it became a member of
your 2003 Domain, it stopped working.

277917 - Terminal Server Licensing Service Failure
http://support.microsoft.com/?kbid=277917

You will have to call the Clearinghouse to get your licenses re-
issued, for installation on your 2003 LS.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

You will have to call the Clearinghouse to get your licenses re-

issued, for installation on your 2003 LS.

You mean i have to call Clearinghouse to buy upgrade licenses or they will
re-issue TSCALs? Can i reinstall on the same Windows 2000 Terminal server or
i have to install them on one of our 2003 Terminal server and have W2K
Terminal server point to Windows 2003 License server. I am very confuse here.

Thanks.

 

[Vera Noest [MVP]]

As I wrote, you cannot run the TS Licensing Service on your W2K
server, since that server is a member in a domain, and the W2K
Licensing Service must run on a Domain Controller.

So you have to install your licenses on a 2003 Licensing Server
(which can handle both W2K and 2003 TS CALs).
You can phone the Clearinghouse to get your current W2K TS CALs re-
issued for installation on your 2003 LS (without costs). Note that
these TS CALs can only be used when your clients connect to a W2K
Terminal Server.
Should you upgrade your Terminal Server to 2003 TS, then you have
to upgrade your TS CALs as well.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I currently have a Windows 2003 member server running Terminal
services/Citrix also running Terminal license services as well. If that's the
case, i would call MS Clearning house to re-issue my Windows 2000 TSCAL and
install it on that Windows 2003 license server.
I have another question regarding the Windows 2003 license server. Everytime
when i try to open "Terminal Server Licensing" progarm, it will give me an
error message instead of connecting to server directly. What i have to do
everytime is click OK for that error message and manually click action, click
connect to local. Any idea is why doing that and how do i fix that? Here is
the error message. (This is a W2k3 member server not DC)

"No Terminal Server license server is available in the current domain or
workgroup. To connect to another license server, Click Action, click connect,
and then type the server name."

Thanks.

 

[Vera Noest [MVP]]

Have you checked the EventLog on the Licensing Server?
No DNS related errors there?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I just checked the EventLog but no DNS related errors there. But i am still
getting that same error message everytime when i try to open Terminal License
server and have to manually connect locally.

 

[Vera Noest [MVP]]

Yes, I know. That's why I asked about the DNS events, you seem to
have a problem with discovery of the LS.
Have you run lsview and lsreport from the Resource Kit? What do
they report?
Did you install this LS as an Enterprise or Domain License Server?

You could try to hardcode the name of the LS into the registry, but
I would be hesitant to do so in your situation. It shouldn't be
necessary.

301932 - Terminal Services Licensing service discovery
http://support.microsoft.com/?kbid=301932

279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I just tried lsview but no server found and tried lsreport but it said No
Server found.
I installed as Terminal License server. What could be wrong?

 

[Vera Noest [MVP]]

I have not the faintest idea what's wrong, especially since you say
that there are no Events logged on the server and that clients
actually could connect when you pointed the terminal server to this
licensing server.
I think I would try to deactivate and reactivate the Licensing
Server. Be sure to read this first:

814593 - HOW TO: Deactivate or Reactivate a License Server Using
Terminal Services Licensing
http://support.microsoft.com/?kbid=814593

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I just manually override the license server in registry as per your previous
replied. It is working fine now.

279561 - How to Override the License Server Discovery Process
Thanks.

 

[Vera Noest [MVP]]

OK, it's good that your immediate problem is solved.
Still, I would spend some time going through all the EventLogs,
especially on your Domain Controllers and DNS server.
The LS should really have discovered itself automatically.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___