Terminal Services Client Disconnected
From: Duke Fleming (DukeFleming_at_discussions.microsoft.com)
Date: 11/05/04
- Next message: Phillip Windell: "Re: Gigabit switching"
- Previous message: TheDragon: "Re: Need help pinpointing the cause of major broadcast in the network"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Nov 2004 09:16:02 -0800
I have an existing Windows 2000 Server installation in which the Terminal
Serivces for Remote Administration suddenly quit working after it had been
working without a problem for many months.
When I initiate a terminal services session from any client PC on the LAN, I
get the following message: "Terminal Services Client Disconnected. The
client could not connect to the Terminal server. The server may be too busy.
Please try connecting later."
This happens whether I use a WinXP, Win2K, or Win98 client to connect to the
Win2K server. I can connect to other Win2K and Win2K3 servers on the LAN and
WAN running Terminal Services in Remote Administration mode, just not this
particular one.
I tried pinging port 3389 and telnetting to port 3389 on the affected server
but got no repsonse from that port. The Terminal Services Manager on the box
shows that the service is active and the configuration is using RDP-tcp as
the connection to the terminal service. I have tried removing and
reinstalling Terminal services several times but the situation continues. I
would prefer not to blow away the install and do a fresh reinstall to correct
the problem, but I need to do remote administration on the box and don't want
to use PC Anywhere or some other 3d party remote access solution.
Any assistance in resolving this problem would be greatly appreciated.
-- Duke Fleming Systems Engineer Fleming Associates Inc.
- Next message: Phillip Windell: "Re: Gigabit switching"
- Previous message: TheDragon: "Re: Need help pinpointing the cause of major broadcast in the network"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|