Re: Remote Desktop & Wake-on-LAN

From: David Shorthouse (davidshorthouse_at_shawyourclothes.ca)
Date: 05/19/04 

Date: Wed, 19 May 2004 19:57:45 GMT

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.
> >
> >
>
>

Relevant Pages

  • Re: Remote Desktop & Wake-on-LAN
    ... What exactly happens when the machine refuses to suspend? ... > a Remote Desktop client connection. ... > not want because the server machine will never successfully return to ...
    (microsoft.public.windowsxp.network_web)
  • Re: Client side printing
    ... xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted ... Perhaps you can specify the printer name using UNC naming so the print is done on ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: Which is best - recordsets/VBA V SQL statements for updating data
    ... One typical requirement was a client who required a report that forecast ... > SQL is better than Recordset Updating and Vice Versa. ... Is this a job for SQL or for Recordset ... > Procedure or UDF on the Server machine, using loops, conditional, ...
    (comp.databases.ms-access)
  • Re: Err.Raise in COM+ Component loses Err.Source and Err.Description
    ... error" on 2 different server machines running the same server-side package. ... I wish I had another Win2000 machine I could try as a client to ... Using the same SERVER machine and varying CLIENT machines running the same ... Set cnDBMS = New Connection ...
    (microsoft.public.vb.general.discussion)
  • Re: Client side printing
    ... Thanks Tibor, yes what you are suggesting, makes sense. ... server by other users. ... everyone at client-side got there own printers, so I doubt if client admin ... I managed to do this on Server machine. ...
    (microsoft.public.sqlserver.server)