Remote Desktop & Wake-on-LAN

Hey folks,

I have a Linksys LNE100TX ver. 5 10/100 NIC in XP Pro SP1 for which I
have Wake-on-LAN configured. I resume this machine from suspend to RAM with
a Remote Desktop client connection. Procedure works well, but when I
disconnect the RD connection and attempt to then re-suspend this machine, it
will continually resume to full activity no matter what I do from either its
end or the client end. It appears that RD leaves residual hooks, which I do
not want because the server machine will never successfully return to
suspend to RAM once a RD connection is disconnected. Anyone know how to fix
this either at the client or the server end? The only solution I have is to
reboot the client as it appears that it is the client that retains these
residual RD connections to the server. This isn't something that is just
time-sensitive because this activity will continue indefinitely until I
reboot the client.

Thanks,

Dave

--
______________________________
Remove "yourclothes" to reply directly.

What exactly happens when the machine refuses to suspend?
Do you see popups like - this or that device prevents the machine from going to standby...
or some relevant messages in the eventlog?

--PA

"David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message news:goCqc.501740$Pk3.76993@pd7tw1no...
> Hey folks,
>
> I have a Linksys LNE100TX ver. 5 10/100 NIC in XP Pro SP1 for which I
> have Wake-on-LAN configured. I resume this machine from suspend to RAM with
> a Remote Desktop client connection. Procedure works well, but when I
> disconnect the RD connection and attempt to then re-suspend this machine, it
> will continually resume to full activity no matter what I do from either its
> end or the client end. It appears that RD leaves residual hooks, which I do
> not want because the server machine will never successfully return to
> suspend to RAM once a RD connection is disconnected. Anyone know how to fix
> this either at the client or the server end? The only solution I have is to
> reboot the client as it appears that it is the client that retains these
> residual RD connections to the server. This isn't something that is just
> time-sensitive because this activity will continue indefinitely until I
> reboot the client.
>
> Thanks,
>
> Dave
>
> --
> ______________________________
> Remove "yourclothes" to reply directly.
>
>

Sorry I wasn't clear. No errors or pop-ups, just that the server machine
will immediately and continually resume from manual suspend and will never
go into a timed suspend until I reboot the client, even though the RD
connection had long since terminated. A netstat -n will show that the RD
port remains open.

Dave

> What exactly happens when the machine refuses to suspend?
> Do you see popups like - this or that device prevents the machine from
going to standby...
> or some relevant messages in the eventlog?
>
> --PA
>
> > Hey folks,
> >
> > I have a Linksys LNE100TX ver. 5 10/100 NIC in XP Pro SP1 for which
I
> > have Wake-on-LAN configured. I resume this machine from suspend to RAM
with
> > a Remote Desktop client connection. Procedure works well, but when I
> > disconnect the RD connection and attempt to then re-suspend this
machine, it
> > will continually resume to full activity no matter what I do from either
its
> > end or the client end. It appears that RD leaves residual hooks, which I
do
> > not want because the server machine will never successfully return to
> > suspend to RAM once a RD connection is disconnected. Anyone know how to
fix
> > this either at the client or the server end? The only solution I have is
to
> > reboot the client as it appears that it is the client that retains these
> > residual RD connections to the server. This isn't something that is just
> > time-sensitive because this activity will continue indefinitely until I
> > reboot the client.
> >
> > Thanks,
> >
> > Dave
> >
> > --
> > ______________________________
> > Remove "yourclothes" to reply directly.
> >
> >
>
>