No, Microsoft has *not* dropped the free TS CALs for XP Pro clients
connecting to a W2K Terminal Server. What you have heard applies to
Windows 2003, where also XP Pro clients need a purchased TS CAL.
You can try to delete the locally stored license from the PC.
If that doesn't help, you might have to delete some registry keys
from the server, as documented here:
323597 - Windows XP Clients Cannot Connect to a Windows 2000
Terminal Services Server
http://support.microsoft.com/?kbid=323597
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Albert Lizondo Fernández <(E-Mail Removed)> wrote on 10 aug
2005 in microsoft.public.win2000.termserv.clients:
> I have a W2k with Terminal Services and one client can't connect
> to it. The client have WinXP, and connect everyday with it.
> There are two W2k DC, one of them as "License Server". The
> client connect throught a Tarantella server (under Debian
> linux), which send a random user.
>
> The TS Event System show this message:
> Tipo de suceso: Información
> Origen del suceso: TermService
> Categoría del suceso: Ninguno
> Id. del suceso: 1003
> Fecha: 09/08/2005
> Hora: 18:40:06
> Usuario: No disponible
> Equipo: xxxxx (hidden)
> Descripción:
> El cliente de Terminal Server "SCVDDF3ZA" ha proporcionado una
> licencia no válida.
>
> The client has connected succesfully for more than three months,
> but they failed the connection yesterday.
>
> More than 20 users are connecting to this TS every day without
> problems, and has the same OS. The licensing mode is per-seat.
>
> A person tell me that Microsoft drops recently the licenses for
> TS over w2k for XP, and the problem will solve by deleting the
> registry entry HKLM\SOFTWARE\Microsoft\MSLicensing and reconnect
> to the TS to regenerate it.
>
> Will anyone confirm that? What it means, that we will regenerate
> it every three months?
>
> Regards