PC Review


Reply
Thread Tools Rate Thread

Can't connect to TS

 
 
=?ISO-8859-1?Q?Albert_Lizondo_Fern=E1ndez?=
Guest
Posts: n/a
 
      10th Aug 2005
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
 
Reply With Quote
 
 
 
 
Vera Noest [MVP]
Guest
Posts: n/a
 
      10th Aug 2005
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

 
Reply With Quote
 
=?ISO-8859-1?Q?Albert_Lizondo_Fern=E1ndez?=
Guest
Posts: n/a
 
      16th Aug 2005
Thank you very much for your answer.

Finally I have been solved this error by entering the correct License
Server in HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parametres
where DefaultLicenseServer value was incorrect.

Albert Lizondo Fernández
------------------------


Vera Noest [MVP] wrote:
> 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

 
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
Media Connect won't start....UPnP doesnt exist, can't connect Xbox =?Utf-8?B?Q2hhcmxlcyBD?= Windows XP Help 0 26th Jan 2006 09:10 PM
This code hangs on connect() if connect hangs. how to make this so that if connect hangs i time out after 10 seconds. perhaps there is someway to do this with ioctlsocket and select? can anyone show how to do this? Daniel Microsoft Windows 2000 Networking 0 15th Feb 2005 01:37 AM
Win2k stand alone: WIreless will only connect AFTER Admin logs in, user can't connect Rudy Microsoft Windows 2000 0 29th Aug 2004 07:02 AM
'Connect to' item disappeared from Start Menu and Internet doesn't connect Thumper Windows XP Networking 0 30th Jan 2004 08:06 PM
Help! Fail to connect a windows XP laptop via a wireless connect to Dlink router! Stan Windows XP Networking 2 30th Nov 2003 05:14 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:05 AM.