none
WOL doesn't work after 6 mins RRS feed

  • Question

  • Hello all

    My Version 1902

    I have an issue with WOL which is doing my head in. I've enabled WOL for the site and also configured it using the client Power management settings.

    My hardware is Dell and I've enabled WOL in the BIOS using the CCTK tool, deep sleep is off and quick boot as per the recommendations.

    all machines are on the same subnet as the site server.

    Within 6 minutes of machine shutdown:

    Client will wake up using the client notification method

    Client will wake up by deploying an app and sending wake-up packets

    After 6 minutes of machine shutdown:

    Client will wake up using the client notification method

    Client will NOT wake up by deploying an app and sending wake-up packets

    I've looked at power settings as it makes sense that the NIC is an unawakenable mode after the time period but then being woken by notification works so this doesn't make sense either. I've checked the registry settings for the network adapter to see if anything happens after 360 seconds, but nothing!!

    There are no errors in the wolcmgr and wolmgr logs, 3 magic packets are sent. the network guys can also see the magic packets. I've also traced them with wireshark on the clients when they are switched on.

    I've trawled the internet and cant find a solution, any help would be very welcome? 



    • Edited by rtimmsie Tuesday, September 17, 2019 9:01 AM
    Tuesday, September 17, 2019 8:59 AM

All replies

  • This isn't a ConfigMgr issue as there are no time limits or time restrictions inherent in the ConfigMgr processes for WoL. 

    Have you checked wolcmgr.log and wolmgr.log on the site server to validate that the magic packet is being sent in response to a deployment?

    For WoL client notification, there aren't any server side logs that show the actual sending of the WoL packet but you can check the bgbmgr.log to see which client was notified to send the magic packet and then check that client's logs.

    Have you reviewed, at a network level, the magic packet itself?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, September 17, 2019 3:04 PM
  • Is connected/modern standby enabled on these systems? What's the output when you run

    powercfg /a



    https://ccmcache.wordpress.com/ | @kevmjohnston

    Tuesday, September 17, 2019 3:18 PM
  • thanks for the reply,

    yes I've checked the wol logs and they look normal, and yes I have reviewed the magic packets and they too are formed correctly.

    Wednesday, September 18, 2019 6:19 AM
  • thanks for the reply

    Hibernate and Fast Startup are available

    I've turned off fast start-up in the power settings

    I've disabled "Energy Efficient Ethernet" and "Green Ethernet" settings on the NIC

    the settings are exactly as per this article

    https://www.dell.com/support/article/uk/en/ukdhs1/sln292761/wake-on-lan-wol-troubleshooting-best-practices?lang=en



    • Edited by rtimmsie Wednesday, September 18, 2019 7:10 AM
    Wednesday, September 18, 2019 6:28 AM
  • Then as noted, this is a hardware vendor issue that you need to address with them. Note that I've seen drivers and even NIC firmware cause faulty WoL behavior in the past so updating those is worth pursuing as well.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 18, 2019 12:15 PM
  • thanks Jason

    I've flashed the BIOS and made sure the latest drivers are installed. I also have an open call with DELL

    it doesn't make sense though that a client notification wakes it even if its been off for 24hrs but a deployment sending wake-up packet wont wake it.

    as far as I understand it the client notification will use another client on the subnet to wake it but the deployment with a wake-up packet comes direct from the server. Is that correct?

    Wednesday, September 18, 2019 12:30 PM
  • as far as I understand it the client notification will use another client on the subnet to wake it but the deployment with a wake-up packet comes direct from the server. Is that correct?

    Correct.

    Have you conferred with your network folks? They may be able to help you track the magic packet. Also, keep in mind that subnet does not necessarily equal broadcast domain so being on the same subnet isn't necessarily sufficient.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 18, 2019 12:40 PM
  • Yep, Networks confirm that the Magic packets are sent across the switch and down to the device. I've been able to have a look at the magic packets in Wireshark too.

    it makes absolutely no sense to me! it's almost like the client doesn't trust the server but does trust a packet from a client.

    BUT it does trust the packet from the server if its sent quickly enough after shutdown

       
    Wednesday, September 18, 2019 1:32 PM