Terminal Services error message

[Lou T]

I just setup a user with a new laptop running Windows 2k
professional. On his old laptop he could connect to a
particular server using his terminal services client. On
the new laptop he gets and error message saying,
"The remote computer disconnected the session because of
an error in the licensing protocol."

In the event log of the computer that he is trying to
connect to, I get event id 1004 - The terminal server
could not issue a client license.

All other users connect to this box fine and the users old
laptop connects fine. The user can also Term Serv into
other boxes just fine. The box he is trying to connect to
is setup for application mode.

Any ideas? Thanks.

 

[Matthew Harris [MVP]]

Have you tried removing or renaming the MSlicensing
registry key on the client to see if that helps any?

-M

 

[Ivan]

It puts the lotion in the basket...

-----Original Message-----
Have you tried removing or renaming the MSlicensing
registry key on the client to see if that helps any?

-M

.

 

[Guest]

I just tried it, but it didn't work. Any other ideas?
Thanks.

 

[Matthew Harris [MVP]]

Once you reconnected, did the MSLicensing key get
recreated? Also, check the permissions on that key to
make sure everyone can write to it. Lastly, have you
tried reducing the amount of encryption on your RDP data
stream?

-M