Re: Rebooting servers breaks RDP

"Ant-nee" <Antnee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3760D4C-A0C2-4927-BD52-5028FF33AA04@xxxxxxxxxxxxxxxx
I've posted this once before, but I'll try again.

All,

I have several Windows Server 2003 SP1 servers that exhibit this problem.
Some are DCs, some are not; all of them serve different purposes and have
different softwares installed. There's nothing that they truly have in
common except this:

When I reboot them, I can no longer RDP to them. The server is up and
fully
functional, but I cannot connect using RDP. The only way to fix this
problem, I have found, is to again reboot the server, either from the
console
or remotely using the shutdown command. Then I can RDP to the server
again.

When RDP is broken on these servers, I can still connect to the servers
and
all their resources, including file shares. I just can't RDP to them.

This is a real pain, especially on patch days when we are rebooting dozens
of servers.

Does anyone know why this problem happens? How can I fix it?

Thanks,
Anthony Rizzo, MCSE, MCDBA, MCTS

I have a similar problem on some of my servers here (I think) - are you sure
they have definately rebooted?
On my servers, I install the updates, then hit the reboot button and I get
logged off RDP as expected. However, the machines don't actually reboot and
still respond to pings, folder browsing etc. so it appears only the RDP
service stops. I have to then execute a remote shutdown (/r /f) to get the
box to actually reboot.


.