No RDP after reboot

[grabrail]

I support a large number of Windows 2003 servers, and there is a problem that is becoming more and more common.

Sometimes after a reboot of a server, RDP does not work until the server is restarted again.

There are no errors in the event logs, and the server functions fine except for RDP.

Has anybody else experienced this and have a solution or at least a reson for it happening.

TIA

 

[itsp1965]

I have had this issue myself mostly with 64-bit Windows (and on occassion 32-bit). I had opened a ticket with MS regarding this but of course they want me to run their reporting tool after the server is down when I can't access it. As you have indicated, no rhyme or reason. I have;
- Checked TS it is running
- Can manage it remotely form Computer Mgmt Applet
- No errors in the event logs
- No issues with name resolution as I am connecting directly via IP

I would also like to know if anyone has run into this.

 

[Paul318]

Hi
Yes I also have the same problem, another restart usually does the trick, I have learn to use an alternative remote tool (VNC or LOGMEIN) to initially connect after the first restart to perform a second reboot. I have trawled through lots of documents on this, none have worked and most just say restart again? So a solution to this would be welcome!

 

[pagy]

Yep, same thing happens here, only have 32 bit here

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[58sniper]

I have learn to use an alternative remote tool (VNC or LOGMEIN) to initially connect after the first restart to perform a second reboot.

Or just use
shutdown /r /m \\servername

Pat Richard
Microsoft Exchange MVP