Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After rebooting my server Windows 2008 R2 server, I can't log into the remote desktop anymore. When I try to connect, the remote desktop zooms through different status messages, the last of them being "Configuring remote session" and then reverts to the initial Connection dialog again without giving me any error message.

The server is seems to be up, since it's still deliverying web pages. Also, it does seem to be accepting my credentials.

Is there any way to see why the connection fails? I've browsed through my system's even logs, but could not find anything related to remote desktop. Perhaps there's some hidden troubleshooting mode?



Edit: In the meantime the server has come back online. I'm not sure if it did so on it's own or if tech support did because I have not heard from them so far, but the problem is solved for the moment. It's a bit disappointing not to know the cause of thep problem though.

share|improve this question
Quick question - are you attempting to save the connection credentials? – Mr Furious Mar 10 '10 at 20:24
Initially I was, but then I also tried without saved credentials. I also tried it from a different terminal. Always the same problem. – Adrian Grigore Mar 10 '10 at 20:52
Adrian - is there anything in the Event Viewer to go on? Did the reboot happen when you had planned it to, or was it more recent? – mfinni Mar 10 '10 at 21:26
@mfinni: Please see my answer below – Adrian Grigore Mar 11 '10 at 16:58

Verify that it actually rebooted - if you can do a "net use" against the remote server, then connect to Event Viewer to see if it actually did reboot. I've seen plenty of Win2k3 servers that, when rebooted from an RDP session, don't actually reboot but stop responding to RDP. If that's the case, you can do a shutdown /i against the server or use some other out-of-band method of actually executing the reboot.

And if this is the case, in the future, don't reboot from a regular RDP session. Reboot only from the /console or /admin connection, or use shutdown /i, or other remote methods.

share|improve this answer
Forgive me the dumb question, I'm new to windows hosting since I've only used linux for ages, but can I do all these commands without a remote desktop? So far I have not installed any third party ssh server. Is there a way to connect to the computer's console just as with SSH on linux systems? – Adrian Grigore Mar 10 '10 at 19:28
You don't use SSH for this, "net use" works via NetBIOS over TCP. Do a "net use" to the server from your machine, then on your machine run Computer Management or Event Viewer, and Connect to the remote machine. – mfinni Mar 10 '10 at 19:42
@Adrian Grigore, I believe the assumption was that server existed on your local network and you where able to access it via SMB. If the server isn't on your network, then you probably won't be able to do a net use against it since that is probably blocked by firewalls. – Zoredache Mar 10 '10 at 19:43

I had a problem using remote desktop on a server 2003. I connected and after seeing some status messages I was disconnected before seeing the full desktop.

The Problem was, that the server had a wrong time because the synchronization failed for a few month (I think there was a time difference of about 30 minutes).

share|improve this answer
Thanks for the hint, but it doesn't seem to be the problem here. The server is brandnew, just installed it today. – Adrian Grigore Mar 10 '10 at 19:29

After further investigation of the event log, I think I have found the problem. There was this error almost exactly after the restart was initiated:

The Windows Modules Installer service did not shut down properly after receiving a preshutdown control.

So the problem was that some the services were shut down, while this particular service was hanging. It seems to have been killed after a timeout occurred (one hour), after which windows has rebooted as intended.

Now the only remaining question is how to prevent this in the future. Obviously I'd like future reboots to run a bit faster than this...

share|improve this answer

Remote Desktop can also behave oddly if you have older graphics drivers. On a server, I wouldn't think this would be an issue, but updating the graphics drivers is something else you can try. (It fixed a similar issue on an XP SP3 machine for me.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.