cannot connect TS client in WinXP

[Rex]

Hi,

I have install TS client V5.00 in my WinXP, we have two
server have Terminal services. But i just can connect
one, another one will show "Terminal Server Has Ended the
Connection" when i want to connect the server. I have try
to use remote desktop in WinXP but also cannot connect.

Any help in this regard is appreciated

Regards,
Rex

 

[Vera Noest [MVP]]

Can you ping the server from the client? Are both clients located on
the same subnet? Is there anything in the EventLog on the TS when you
try to connect? Have you checked that your TS Licensing Server is
issueing TS CALs to your clients?

There is no need to install the 5.0 version on XP, which already has
the 5.1 version build-in. You might want to install the 5.2 client
instead. Download from
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en

 

[Rex]

Hi,

Yes, i can ping the server. we are Located on the same
subnet. Yes. I find the Eventlog "Windows cannot determine
the user or computer name. return value(1722).

Would you please tell me what file need to rename in TS
Licensing Server when i want to reset the the TS
licensing?? I have use V5.2 but also have the same
result. Many thanks for your help!!!

Regards,
Rex

 

[Vera Noest [MVP]]

You cannot simply "rename a file" to reset the Licensing server,
and I don't understand why on earth you would want to do this. The
cause of the problem is most likely indicated by the event that
you see in the EventLog.

I should have been more clear when asking for information from the
EventLog. What identifies an event is the EventID and the Source.
Events are searchable with these 2 parameters, searching for the
content of the event description is much more difficult.

Fortunately, the event that you have is a common one, EventID=
1000, Source=Userenv. Have a look at this:

http://www.eventid.net/display.asp?eventid=1000&source=userenv

You will find your exact event description there, with a number of
causes and possible solutions.
Most likely cause seems to be a problem with your DNS, but there
are several other possibilities as well.