PC Review


Reply
Thread Tools Rate Thread

TS refuses client licence request.

 
 
sam
Guest
Posts: n/a
 
      11th Feb 2004
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
 
Reply With Quote
 
 
 
 
Vera Noest [MVP]
Guest
Posts: n/a
 
      11th Feb 2004
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?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

"sam" <(E-Mail Removed)> wrote in news:e68301c3f0b2
$8df451f0$(E-Mail Removed):

> 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

 
Reply With Quote
 
Sam
Guest
Posts: n/a
 
      12th Feb 2004
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

>-----Original Message-----
>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?
>
> --
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup ---
>
>"sam" <(E-Mail Removed)> wrote in

news:e68301c3f0b2
>$8df451f0$(E-Mail Removed):
>
>> 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

>.
>

 
Reply With Quote
 
Vera Noest [MVP]
Guest
Posts: n/a
 
      12th Feb 2004
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?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

"Sam" <(E-Mail Removed)> wrote in news:e9a601c3f158
$0cb6aba0$(E-Mail Removed):

> 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
>
>>-----Original Message-----
>>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?
>>
>> --
>>Vera Noest
>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup ---
>>
>>"sam" <(E-Mail Removed)> wrote in

> news:e68301c3f0b2
>>$8df451f0$(E-Mail Removed):
>>
>>> 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

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP client refuses to start =?Utf-8?B?QmFzdGlsbGU=?= Windows XP Networking 5 23rd Oct 2006 06:24 AM
Client Access Licence =?Utf-8?B?cWFr?= Microsoft Windows 2000 Networking 1 8th Jun 2005 12:54 PM
1 client get licence error - all others ok scott Microsoft Windows 2000 Terminal Server Clients 2 9th Dec 2004 05:30 PM
terminal server client licence msg ? what does it mean ? scott Microsoft Windows 2000 Networking 0 9th Dec 2004 02:53 PM
ASP.NET + Client Access Licence =?Utf-8?B?SGFuaSBBdGFzc2k=?= Microsoft ASP .NET 6 2nd Nov 2004 10:20 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 07:08 PM.