Windows 2003 Server update stopped remote desktop listening on 5 out of 8 servers

Any ideas how to get remote desktop to listen again without rebooting live
servers.

We did an update on 8 servers last night, now 5 no longer function with
remote desktop.

The patches applied were as follows:-

7 servers (4 down 3 remote desktop ok)
KB935839
KB890830
KB935840
KB929123
KB924667-v2

1 server all the above plus (down)
KB927891

The remote desktop service is running
sc qc rpcss - shows the service is still corrrectly setup and
sc queryex rpcss - shows the service in state 4 running

telnet localhost 3389 does not connect and
using netstat -abnv|more shows that it is not listening on port 3389

Any ideas on how the get remote desktop to listen again or to restart the
service with out rebooting much appreciated.

OTHER SYMPTOMS
All the machines where remote desktop is not running did not do a normal
reboot.

The event log stops at the message

USER32 shutdown type restart
And there are none of the nomal restart messages.

On the machines that are still working it is the normal

USER32 shutdown type restart followed by
EventLog Event log service stopped
And post reboot
EventLog Windows banner message and normal boot sequence.



All the best

Ronald

Please copy replies direct to which will get
straight through to me thanks.

<> wrote in message
news:...
> Any ideas how to get remote desktop to listen again without rebooting live
> servers.
The only way is to reboot the server.
> The event log stops at the message
>
> USER32 shutdown type restart
> And there are none of the nomal restart messages.
>
> On the machines that are still working it is the normal
>
> USER32 shutdown type restart followed by
> EventLog Event log service stopped
> And post reboot
> EventLog Windows banner message and normal boot sequence.
>
This was because the machines did not reboot they just disconnected the
terminal services connection after the start of the reboot sequence, and
were stuck partly shutdown but still running. I killed the rpc process on
one to see if I could for a recyle of terminal services, however this just
results in a shutdown in 60 sec so I did a restart.

Things then closed down normally and started again OK.

Not a lot of fun if your only remote connection is via terminal services.

We see this constantly on our Windows 2003 servers. It always happens after
automatic updates when we choose to install them and then say to restart,
been happening for several months. If you watch it, the server never shuts
down, it just disconnects your RDP session, terminates TS and then sits. If
you google the newsgroups, you'll find a lot of others complaining about it
so its obviously a known issue whether MS wants to admit it to be a problem
or not. I've been hoping that they would at least fix it on the sly in one
of the hotfixes but so far no go.

The easy way to work around it is to just issue the following command from
any server/workstation:

shutdown -m \\%computername% -r

where %computername% is the server having the shutdown problem. This will
force a remote reboot of that server. May save you from making a trip to the
console.


"" wrote:

>
> <> wrote in message
> news:...
> > Any ideas how to get remote desktop to listen again without rebooting live
> > servers.
> The only way is to reboot the server.
> > The event log stops at the message
> >
> > USER32 shutdown type restart
> > And there are none of the nomal restart messages.
> >
> > On the machines that are still working it is the normal
> >
> > USER32 shutdown type restart followed by
> > EventLog Event log service stopped
> > And post reboot
> > EventLog Windows banner message and normal boot sequence.
> >
> This was because the machines did not reboot they just disconnected the
> terminal services connection after the start of the reboot sequence, and
> were stuck partly shutdown but still running. I killed the rpc process on
> one to see if I could for a recyle of terminal services, however this just
> results in a shutdown in 60 sec so I did a restart.
>
> Things then closed down normally and started again OK.
>
> Not a lot of fun if your only remote connection is via terminal services.
>
>
>