Wake PC on RDP connection?

[Washy]

Is there a way to wake a computer in S3 mode when using RDP? I like my pc to sleep to conserve power, but I need to access my PC from work and I don't want to leave the PC on all day if I don't have to.

Thanks in advance,

Washy

 

[Antman]

Enable Wake On LAN in BIOS and/or Device Manager.

 

[SquonkSC]

Down side is that it will wake every single time one of your other networked computers sends something over the network.

Drove me crazy. :shock:

 

[Antman]

...Drove me crazy.

Ohhh... that was it...

Upright walking cats are usually more stable.

 

[SquonkSC]

Ohhh... that was it...

Upright walking cats are usually more stable.

Well that, and the ten ton truck that ran over me.

 

[Antman]

Well that, and the ten ton truck that ran over me.

<off topic> Redirect </off>

 

[Washy]

That didn't work. It still doesn't wake. I know the settings are correct because my Xbox extenders can wake the pc to connect to windows media center.

Is there a command line with powercfg that may work to enable the RDP program to wake the pc?

 

[Washy]

I found this great utility that will wake the pc remotely. Works like a charm.
Its called WoL Command Line.

Unless there is a way to do what I want without a bat file, please let me know.

Thanks,

Washy

 

[Pucker]

I found that RDP connections would wake up my computers running win7. That was working fine until I joined the computers to a domain. Now I can't wake them. WolCMD is fine as long as you're on your own network. But it won't work going through ASA firewalls and Cisco concentrators.

 

[SquonkSC]

I found that RDP connections would wake up my computers running win7. That was working fine until I joined the computers to a domain. Now I can't wake them. WolCMD is fine as long as you're on your own network. But it won't work going through ASA firewalls and Cisco concentrators.

Hi Pucker,

I think there is a policy for it in windows server.

good luck.

 

[johngalt]

OK, so I have RD set up on W7 and on my laptop (also W7) so I can access it from home. The problem I have is that the laptop will not connect - stating that the connection failed. I know that the computer goes to sleep on its own, as that is how I have it set, and I have WOL enabled for both NICs on the system, and my Router is set to forward RD sessions to my IP.

What I cannot figure out is why it will not wake - however, I went back to play with it tonight and when I changed the RD settings, I see that it gives the following warning:



As you can see, according to the warning RD doesn't work with machines set to sleep / hibernate. According to this thread, it is supposed to - or is it?

My power options with regard to Sleep are as follows:



So far, no luck with the NIC WOL - if I enable "Allow the system to turn off this device, then only do I get the option to enable WOL - so, currently, both are enabled (and I have not enabled WOL w/ MP only):



I'll try out that WOLGUI next to see if it works on this machine....

 

[johngalt]

I just tried this locally - my laptop was still not able to wake my desktop up.

Time to see about WOL GUI

 

[johngalt]

Hmmm - WOL GUI needs a MAC - I suppose I am supposed to always keep that MAC address handy?

 

[johngalt]

Hrm....I think that for now I am going to just have my machine not go into sleep mode....

 

[johngalt]

I found a solution - of sorts.

After setting the NICs to allow to be woken up, I found that if I tried to remote into the machine, then waited about 2 minutes or so, and then tried to remote in, it was woken up.

But, to avoid the hit and miss I found a better solution - at least for me.

http://www.sevenforums.com/network-...r-dynamically-adjust-your-power-settings.html

 

[kegobeer]

Hmmm - WOL GUI needs a MAC - I suppose I am supposed to always keep that MAC address handy?

I wrote a batch file for each computer I need to wake up using WOL, so I didn't have to remember each MAC address.

 

[MattD]

I noticed the same issue as Pucker

I installed Windows 7 on a PC, enabled WOL and it worked flawlessly. Immediately after joining it to a Windows Server 2008 R2 Domain Controller, WOL stopped working, sort of. I have since learned Win7/08R2 has advanced power management related to waking PC's up:

"Support for Green Computing
With improved Wake on LAN (WoL) support, Windows 7 computers can reduce electricity consumption by going to sleep and staying asleep longer. Fine-grain control over wake-up packets keeps the PC asleep longer. Protocol offload to the network adapter allows a sleeping PC to remain reachable by network management tools without being woken up. Windows 7 also supports Wake on Wireless LAN (WoWLAN), which extends sleep scenarios to wireless client computers."

I believe this is so PC's remain asleep in an enterprise environment where there is likely a lot of netork traffic that could potentially wake them up constantly. That being said, after joining the Win7 client to an 08 R2 D.C., a simple ping would no longer wake the computer (it did beforehand), but attempting to access the client from the D.C. via Windows Explorer (i.e. \\clientname\C$) will wake it every time.

Ultimately I would like to be able to wake the client PC when I attempt to directly remote desktop into it and not have to go through the server to do it. I have searched up and down for a setting (server and client side) or group policy that addresses this but have been unsuccessful in finding it thus far. If anyone can shed any light on this it would be much appreciated. I should note that I have used this identical setup with Windows Vista/Server 2008 and it worked every time. Thanks.

More links on new power features in Windows 7:
NDIS Power Management Overview
WOL Methods in Windows 7
Protocol Offloads for NDIS Power Management
Low Power for Wake on LAN