client error

  • Thread starter Thread starter Jack
  • Start date Start date
J

Jack

Hi guys!

We have a dozen servers on our internal LAN as part of a
global Active Directory system. From my PC (as admin), I
can terminal into every single server on the LAN without
issue - except one!

It never used to be a problem up until a week ago, then
suddenly I got the "unable to connect" message. This is
most annoying as our server room is located 5-floors above
us - and it saves the trek!

Every other server is fine, but none of the guys can now
TS to this one server. I reinstalled terminal services on
the server twice, and reinstalled the clients on the PCs
but it still refuses. There isnt anything in the server
event viewer either.

No network changes have been made (routers etc.) - its
exactly as it was before this stopped working.

Any ideas at all as to why this has occured??

Many thanks guys

Jack
 
I assume you have a normal network connection to the server (you
can ping it and connect to shared folders)?
Just a wild guess: If you start TS Administration on the console,
do you have a listener session? What is the status?

312030 - Cannot Connect to a Windows 2000-Based Computer with
Terminal Services Installed and RDP Listener Is "Down"
http://support.microsoft.com/?kbid=312030
 
Hi, thanks for the reply.

Yes, your assumptions are correct. Everything else is
fine. We can ping and connect to folders without problem -
just Terminal services not working.

I checked in TS Manager and there is no 'Listener' session
showing for that particular server. It doesn't appear at
all. So would the link to Microsoft fix resolve this
issue? would like to clarify before going into the
registry - problem is this is without a doubt one of our
most critical servers.

Many thanks

JackW
 
No listener session at all, that's even more serious.
In that case, I would follow the troubleshooting tips in this
article:

258021 - Event ID 52 When You Start Terminal Services
http://support.microsoft.com/?kbid=258021

I understand your hesitation to modify the registry. Be sure to
make a full backup of the server (including system state) before
making any changes. Also: if you export a registry key before
deleting or modifying it, you can always restore it if needed.
 
Back
Top