Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

The Client could not connect - Terminal Services

Status
Not open for further replies.

PeterPan22

Technical User
Nov 13, 2001
2
GB
After removing Active Directory by demotion and re-installing (this may not have anything to do with this particular problem), I get the following:

The Client could not connect to the terminal server. The server may be too busy. Please try connecting later.

There's only one server (Win 2000 Adv.)and 1 Win 2K Pro Client (it's a test network) so it being busy is obviously not the case. I've re-installed every part I can think of, tried various suggestions, all no no avail. Time is running short and my boss is beginning to lose that confident smile he had when we started all this, so any suggestions very gratefully received.
Thanks.
 
Did you try removing Terminal Server?
Then reinstall.
Then reinstall SP2 Glenn A
"Do not meddle in the affairs of dragons, for you are tasty and crunchy and good with ketchup."


 
No, but thanks for the suggestion, I'll give it a go.
 
First thing is to try to establish the RDP connection locally, eg. try to run the TS-Client on the server to connect to the server.


After that is verified, try to establish connection with the server from a client. Also verify that communication between the 2 machines is up, use a portmonitor to see if the server gets a request from the clients IP-adress and make sure that the server listens to RDP connections.

Some small tips... Good Luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top