TS Error when connecting

  • Thread starter Thread starter Pete
  • Start date Start date
P

Pete

Hi people!

Have a question for you, but here's the situation.

We have a group of servers on an Active Directory network
on a LAN, from my desktop PC I have always been able to
connect to them all (and still do) via terminal services
to perform updates, changes etc.

However, this works fine - except for one server! It was
working ok last week, but now everytime I attempt to
connect I get the following (standard) message:

"The client could not connect to the Terminal server. The
server may be too busy. Please try connecting later."

Now I know there isn't anyone else on it, I've rebooted
it, re-installed it, and can't connect from any other PC
(neither can colleagues). The event logs don't show
anything either - it just refuses to connect. Apart from
this error the server itself is fine!

It's running Windows 2000 service pack 4 with all security
updates. Nothing has been installed since last week that
could be the cause. Just very odd. Our PC's are a mix of
Win2000 Pro and XP Pro, but we can connect to all the
other servers without problems.

Any ideas\suggestions?

Thanks guys - Pete
 
<snip>
Could someone by any chance have disabled the RDP-Tcp connection in
Terminal Services Configuration?

--
Cheers,
Marin Marinov
MCT,MCSE 2003,MCSE:Security 2003
-
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Back
Top