TS refuses client licence request.

[sam]

I have a bit of a strange one here... I have a user who
can log into NT but when they connect to a terminal server
they are getting their connection refused.

(The terminal server they are connecting to is also
running the TS licencing service and has granted a licence
for that machine already. There are also plenty of free
licences available on the licencing server)

If we log into the client machine with a different user ID
and then try and connect to the terminal server with the
ID that failed before it works OK......???? I thought TS
licencing was based per client machine. (The licencing on
the Terminal server is configured as per seat)

Any help on this would be greatly appreciated.

Regards

Sam

 

[Vera Noest [MVP]]

So what makes you believe that the problem is related to
licensing?
Is there anything in the EventLog on the TS when this happens?
Exactly what error message does the user get?
Which OS and SP do you run on the TS and the client?

 

[Sam]

Vera,
Thanks for your reply. The Client OS is windows NT4
SP6a, the Server is Windows 2000 SP3. When logged on as
one user it works fine. using the same id but logging on
as a different user to terminal server the following
message appears: The terminal server has ended the
connection.

The following corresponding event appears in the terminal
servers system log: Event ID 1004 The terminal server
cannot issue a client licence. When checking the terminal
services licencing server (on the same terminal server)
There already two licences issued to this workstation.
And there are also 600 unused licences remaining.

Regards

Sam

 

[Vera Noest [MVP]]

That's weird, indeed.
Only reason I can think of is when the user account that is used
to logon to the NT 4.0 workstation does not have the necessary
permissions to update the registry key that holds the license
information. But somehow, this scenario doesn't fit the bill
either. If you have successfully connected from a workstation
(twice), then it has received a license and should be good to go
also for the next user.
But still, could you check that the user has Read & Write
permissions on the registry key mentioned here:

187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

While you're at it, have you tried to delete the registry entry
for the license from the client?