Windows 2003 Server

  • Thread starter Thread starter Rich
  • Start date Start date
R

Rich

I have a windows 2003 server in a windows 2000 domain. I
use TS to connect to all of my servers for remote admin.
For some reason, I cannot connect to the single windows
2003 server. Error says... "Client could not connect to
the Terminal Server. the server may be too busy. Please
try connceting later."

There is no error message on the TS itself. Built in
firewall is not turned on and I do have rights. I don't
get it. Is it somehting to do with the Win 2K license
server in the domain? I wouldn't think so because it's
just for remote admin.

Thanks to any who can help.

Rich
 
Neither of the KB articles applies to my situation. I
have also noticed that if I open the terminal services
client, the server is not listed there with the rest. It
is as if somehting is not running properly. Any other
ideas?

Thanks
 
The server name will appear in the list only after a successful connect. Not
having the name there does not imply that you can't connect to it.

Can you ping the server from client machine? If yes, can you try machine's
IP address in TS client and let us know if it succeeds?

Rajneesh
 
I would try one more thing. Launch TS Client from that windows 2003 server
machine and try connecting to itself (by entering its name or IP address).
If you get the same error then probably you have not enabled remote desktop.
Right click on my computer, choose properties, go to remote tab and check
the Remote Desktop option.

Rajneesh
 
That did it. When I did an install in my test
enviornment, it was on by default. Good to know for next
time. Thanks very much!

Rich
 
Back
Top