Wake On LAN on Win7 client stopped working after joining to 2008 R2 D.C.
I have set up a test environment which includes a Windows 7 Pro x64 client and Windows Server 2008 R2 x64 Domain Controller. I am attempting to enable WOL (Wake On LAN) on the client for any network traffic, not just magic packets. I have had WOL enabled on this client (using Vista) in the past and never had any issues. WOL also seemed to work great on Windows 7 up until I joined the Win7 client to the 2008 R2 D.C. I took a look through power management, various group policy settings on both machines, and verified my initial settings on the client that were working, but was unable to determine what might be causing this. When I initially installed Win7 I repeatedly tested the WOL setting and it worked every time I attempted to wake it (with a ping from the DC-it was not joined to DC at this time). Right after joining the Win7 client to the DC, WOL stopped working completely (again, tested by pinging from the DC). I have read about some more control over these features with the new O.S.'s but I am at at a loss as to how to make this work. Any insight would be much appreciated. Thanks.
September 18th, 2009 1:10am

I have set up a test environment which includes a Windows 7 Pro x64 client and Windows Server 2008 R2 x64 Domain Controller. I am attempting to enable WOL (Wake On LAN) on the client for any network traffic, not just magic packets. I have had WOL enabled on this client (using Vista) in the past and never had any issues. WOL also seemed to work great on Windows 7 up until I joined the Win7 client to the 2008 R2 D.C. I took a look through power management, various group policy settings on both machines, and verified my initial settings on the client that were working, but was unable to determine what might be causing this. When I initially installed Win7 I repeatedly tested the WOL setting and it worked every time I attempted to wake it (with a ping from the DC-it was not joined to DC at this time). Right after joining the Win7 client to the DC, WOL stopped working completely (again, tested by pinging from the DC). I have read about some more control over these features with the new O.S.'s but I am at at a loss as to how to make this work. Any insight would be much appreciated. Thanks. Update: I found some info (http://serverfault.com/questions/55270/cant-get-windows-2008-r2-support-for-wake-on-lan) stating that a simple ping from a Windows Server will not wake Windows 7 but attempting to access the client using Windows Explorer (\\client.name\C$) will. So I gave it a try and it seemed to work, sort of. It didnt appear to wake the client reliably, but after 1-5 tries the client would wake. I would still like more control over this so if anyone can guide me to the settings I would be grateful. Ultimately I want to be able to wake the client even if the server is off or unavailable, like when trying to remote desktop into it. Thanks again.
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2009 1:10am

I have set up a test environment which includes a Windows 7 Pro x64 client and Windows Server 2008 R2 x64 Domain Controller. I am attempting to enable WOL (Wake On LAN) on the client for any network traffic, not just magic packets. I have had WOL enabled on this client (using Vista) in the past and never had any issues. WOL also seemed to work great on Windows 7 up until I joined the Win7 client to the 2008 R2 D.C. I took a look through power management, various group policy settings on both machines, and verified my initial settings on the client that were working, but was unable to determine what might be causing this. When I initially installed Win7 I repeatedly tested the WOL setting and it worked every time I attempted to wake it (with a ping from the DC-it was not joined to DC at this time). Right after joining the Win7 client to the DC, WOL stopped working completely (again, tested by pinging from the DC). I have read about some more control over these features with the new O.S.'s but I am at at a loss as to how to make this work. Any insight would be much appreciated. Thanks. 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."Quoted from: http://technet.microsoft.com/en-us/library/dd443486(WS.10).aspxStill not sure where the setting is to enable a ping or more specifically aRemote Destop sessionto wake a sleeping client.
September 27th, 2009 5:33am

I have been working on this issue for days straight and have tried everything. With my old vista install I was able to wake the machine simply by trying to access the network share I had on it or by using remote desktop to try to connect. That is exactly how I want my windows 7 machine to behave but it will not. The only thing that works is a WOL utility to send the magic packet. I do not want that extra step! The magic packet utility will not work over the internet either so that is a deal breaker. My router will not forward WAN sourced packets to the LAN. According to articles I've read, windows 7 has turned off the ability to wake by directed packetsto become more eco friendly (green). I have even tried to enable that functionality again using netsh enabledirectedWOLpattern settings. It does not work. I'm so frustrated with this. I have read every possible suggestion on the internet and it seems that it can't be done. I have tried 5 different drivers for my NIC cards and none have helped. My NIC card drivers are supposed to support the latest windows 7 power management features but it will still only wake witha magic patter sent only from my LAN. I hope they come up with a patch or something for this.
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2009 5:52pm

http://technet.microsoft.com/en-us/library/ee617165(WS.10).aspx?ppud=4 Have not tested this yet buy maybe it will work? Open a command prompt with administrator privileges. (click the Start button, type Command Prompt in the Start Search box, right click Command Prompt, and click Run as Administrator.) Type netsh interface ipv4 show interfaces. This will list all of the available network interfaces; note the index (labeled Idx) of the network adapter you want to modify. To force the network adapter to wake on ARP and NS type netsh interface ipv4 set interface [index] forcearpndwolpattern=enabled. If successful, OK will be returned. To revert to system default type netsh interface ipv4 set interface [index] forcearpndwolpattern=disabled. If successful, OK will be returned.
May 4th, 2010 12:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics