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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot Remote Desktop

Status
Not open for further replies.
Mar 12, 2003
678
US
I was able to remote desktop into a Windows 2003 Server before it was rebooted, now after the reboot no one can remote desktop. Unfortunatley we can not reboot it again anytime soon. Anyone have any idea why Remote Desktop will not work. The server is set to allow Remote Desktop and permissions are correct.
 
Make sure that the terminal services service is started, it may have crashed when you rebooted and not been set to auto restart on a crash.
 
Start/settings/control panel/administrative tools/services

the service is called terminal services.
 
Thanks, I found it...it says it is started but it does not allow me to restart it...is that the way it should be.
 
If its started thats not your problem. though you should be able to restart it if you are logged in with an account with admin rights, unless its in use.

What is the actual error message that you receive when you try to connect to the server using remote desktop?
 
That is the way that service should look. If you are running SP1 check the firewall to see if it is enabled and if blocking port 3389.

Network properties/Advanced tab.
Network properties/TCP/IP Properties/General/Adv/options.


Also check System Properties/remote tab/Remote desktop config is still enabled.
 
The messaage is
Header: Remote Desktop Disconnected
This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network admin.

I am an admin on the server and like I said we did not have this problem before we rebotted.
 
When I run the query i get

TCP port 3389 <unkown service>: Listening
 
I've ran into this when doing server patching. And as funny as it sounds I had to re-boot a second time to clear the issue.
 
It turns out that we have a hardware problem that the server guys will have to fix. Thanks for all of your replies though.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top