Remote Desktop Problems
I rebooted our 2k3 server box, and it looks like its hanging for some reason and I can't connect via terminal services to investigate. Any suggestions to resolve this issue?
Update
- Working on vpn - server is a stand alone sql server - no domain - development environment
- Can ping
- SQL Service, everything else is running fine, just cant connect via RD, trying console doesn't work either.
Update 5:41 PM EST
- tried using
psShutdown -r -f, and shutdown /r/f with no luck. I think I did manage to take out the RPC service though as it is no longer responding. It's still responding to pings though. Also, just for kicks I tried to telnet to the remote port, something seems to be listening on 3389.
When trying to use mstsc in any mode i get the Remote Desktop Disconnected Message.
6:04 PM EST - Going to need a manual reboot I think. Thanks everyone for the advice, I learned some good tips.
Does your server have multiple NIC's installed? We ran into a behavior that occurs on some servers where the server gets rebooted but you cannot connect via RDP, but it doesn't happen every time.
We finally tracked it down to an obscure bug (IMHO) where having the RDP bound to all interfaces (which is the default) can cause the behavior. Fortunately, the first server we had that happen on had a DRAC which allowed us to correct the problem remotely. The second one did not.
The solution was to explicity bind RDP to the interface it was suppose to be using. Since then we haven't had a problem. In the case of our second server we were able to issue a reboot command from another machine on the network and when it came back up we were able to connect and fix the issue. The command was:
shutdown /r /f /t 000 /m \\<servername>
or you can use this command to show the GUI for it
shutdown /i
After reading all the descriptions of what's going on, (greyed out controls, unable to RDP, etc.) I'd bet a soda pop that your RPC service is having great difficulty, (and/or is possibly affecting your server service.)
If this is the case, none of the pstools will work, (psexec, pslist, etc.)
And if time is of the essence, suggest wrangling a user on-site to perform a hard power down/up. I'd probably also have the user watch for RAID errors, during boot process.
Good luck, mate.. I've been where you are, before :)
I'm assuming that you can ping the server. Try accessing the server's services via Computer Management on your desktop and make sure that Terminal Services is up and Running.
Have you tried accessing the terminal server though a MSTS console switch?
mstsc -v:servername /F -console
You should try this if regular TS connection fails