terminal server client lic problem

[Babu]

hi
i have windows 2003 standard server& 5 client cal per user
licences. i installed in licence server & activated it .
when xp pro terminal client pcs r connecting no problem.
when 98 client pcs showing time our error msg. in my
terminal server licences its showing 5 tokers and issued
showing only 0 what could be problem in licencing or
configuration

thank u

 

[Abhijeet Nigam [MSFT]]

Hi,
Please check these network shares IPC$ and ADMIN $ in your windows
If these shares are not there then you will not be able to connect to
terminal server
KB 318755 to recreate the shares

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[GeezerBob]

Well, I had a similar problem and had to pay MS to find out that
turning off TS Logging Service solved it. Hope this helps.

 

[Vera Noest [MVP]]

Check the EventLog on the Terminal Server to see why the W98
clients can't connect.

Is the Terminal Server (not the Licensing Server!) set to use "Per
User" licensing? The default is "Per Device".
You can check this from Administrative Tools - Terminal Services
Configuration - Server Settings
If it's set to Per Device mode, it will look for a Device TS CAL
and will not issue your Per User TS CALs.

Check this article, it explains that even after you have
switched licensing mode on the TS, your Per User TS CAL count will
not be decremented:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

 

[Guest]

What you have in the current scenario is Windows CALs, and for Win98 to be
able to do a terminal server session, you need to have TS CALs, as the
article below will explain:

Windows Server 2003 Terminal Server licensing issues and requirements for
deployment
http://support.microsoft.com/default.aspx?scid=kb;en-us;823313

 

[Them]

This helped me a BUNCH! I found that in "Domain" mode my server couldn't
find the license server by it's self even though it was the license server.
It takes a simple reg hack to correct. A reboot and "bam" everything is
working.

Thanks!!!

Just another admin