RE: Error in licensing protocol



Have plenty of T/S CALs available.

"Vera Noest [MVP]" wrote:

Have you verified in the TS Licensing Manager that you have a free
TS CAL available? Maybe all of your TS CALs have been issued?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Sm9lIEUu?= <JoeE@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 26
feb 2006 in microsoft.public.windows.terminal_services:

Unfortunately no.

I did delete the registry key "mslicensing" which Microsoft says
to delete in the "Troubleshooting Remote Desktop Licensing Error
Message".


"RP-FR" wrote:

Unfortunaltely, you don't have another TS Server to see if this
one can a least on temporary licence for this laptop.
Do you try to change anything regarding licensing in the
registry?

"Joe E." wrote:

We only have one have one T/S.

But the links surely can't be broken as this Laptop is bran
new and and has only been used once to connect to T/S. It's
strange how it has the same problem on a brand new PC.


"RP-FR" wrote:

So have nothing on the server side? Nothing in Events
viewer? Maybe the registry settings for TS Licensing are
broken on the Laptop. have you another TS server to try a
connection?

Regards,

"Joe E." wrote:

The error message is:

The remote copmuter disconnected the session because of
an error in the licensing protocol. Please try
connecting to the remote computer again or contact your
server administrator.

"RP-FR" wrote:

What is the exact problem? ex the mesage displayed ...

"Joe E." wrote:

I only have this error on one Laptop, which is
running WinXP latest S/P & Patches applied.

I can log onto any other PC via T/S, with the exact
same user account without any problem.

I have already followed Microsoft instructions
(Troubleshooting Remote Desktop Licensing Error
Messages) on how to resolve it and had no luck. Also
searched the net without any luck.

Cheked the Log events on the Terminal Server.
Nothing usefull.

We have a Win Server 2003 Ent. acting as the Terminal
Licensing Server and it is activated. We have more
than 60 T/S connection working fine except
this Laptop.

I have just replaced the users old Laptop with a
brand new one today to see if it would make any
difference and I'm still getting the same error.

What can be done to resolve it?

.



Relevant Pages

  • RE: Error in licensing protocol
    ... for exemple the one shipped with Windows Server 2003? ... Do you try to change anything regarding licensing in the registry? ... But the links surely can't be broken as this Laptop is bran new and and has ... Desktop Licensing Error Messages) on how to resolve it and had no luck. ...
    (microsoft.public.windows.terminal_services)
  • RE: Error in licensing protocol
    ... "Joe E." ... Ask other user to log off the server and to stay off line during the test ... Try to connect this Laptop. ... to delete in the "Troubleshooting Remote Desktop Licensing Error ...
    (microsoft.public.windows.terminal_services)
  • RE: Error in licensing protocol
    ... The error for the same user first occured on a different laptop. ... was replacd with a brand new one and the same error occured on it. ... for exemple the one shipped with Windows Server 2003? ... Do you try to change anything regarding licensing in the registry? ...
    (microsoft.public.windows.terminal_services)
  • RE: Error in licensing protocol
    ... Have you verified in the TS Licensing Manager that you have a free ... MCSE, CCEA, Microsoft MVP - Terminal Server ... to delete in the "Troubleshooting Remote Desktop Licensing Error ... But the links surely can't be broken as this Laptop is bran ...
    (microsoft.public.windows.terminal_services)
  • Re: SBS2003 + Windows 2003 Sev + Terminal Services LICENSING issue
    ... On the T/S box run Licensing Server and you will see what I mean. ... > has remote desktop for administration. ...
    (microsoft.public.windows.server.sbs)