Wake On LAN - Source of all Confusion
I would like to have 100% responsive to WoL. However, I am having some issues with the various hardware and software configuration options, and am looking for some advice.
My test system is an Optiplex 740 with a Broadcom Netxtreme 57xx is network interface
As far as I can tell, there are 3 areas where WoL behavior is configured. These are:
Windows Network Interface Power Management - A tab in the network interface's properties.
I would rather not have Windows turn off the device to save power, but my testing has shown that if Windows Power Management isn't enabled for the interface, the system doesn't respond to wake requests when it is sleep mode. Does anybody have any explanation for this?
Advanced Driver Settings:
The alternative configuration settings for Wake Up Capabilities are Magic Packet, Wake Up Frame, None, or Both. Both is the default. I haven't ever dealt with this, but it varies depending on the network card, and driver.
Remote Wake Up must be on, and Low Power Mode must be off.
So with these settings configured as pictured above, I am able to wake a computer from shutdown and from sleep (hibernation is disabled). My problem is that, after ~3 hours (or less), the system stops reacting to wake requests.
What could be causing it to stop responding to wake requests after some time period of having been shutdown?
Has anybody else wrestled with WoL and come through the other side?
Community Chosen Answer
I wrestled with it and had internal resistance to change but had a similar issue.
In our instance, the MAC address tables on switches and routers have a setting to clear the tables after "X" hours. Once you turn off the PC and it hits that magic number, the MAC is flushed and the network hardware doesn't know where to send the WOL packet any longer. There are apparently issues to changing this setting, and my team wasn't willing to alter the value.
It's pretty frustrating, so I'd love to hear other suggestions.