Intel® NUCs
Support for Intel® NUC products
12525 Discussions

BXNUC10i7FNH2 Wake On LAN from Modern StandBy not working

UdoCologne
Novice
6,222 Views

Dear Community,
I cannot make my Intel NUC wake by wired LAN from "Modern Standby".

Note: I'm translating some settings below from German, so it might not be a 100% match for what a setting is called in English

Many of the BIOS/NIC/Windows settings are from this Intel Support Article:
https://www.intel.com/content/www/us/en/support/articles/000027615/intel-nuc.html

System: BXNUC10i7FNH2
BIOS: FNCML357.0043.2020.0708.1750
Integrated Wired-NIC: I219-V with driver 12.18.9.23 (2020-04-20)
Windows 10 Pro 1909 (Build 18363.959) - fully updated (2004 is not on the menu yet, waiting for MS to allow this system)

BIOS Settings
Onboard Devices - WLAN: Off (I want to use wired LAN adapter ... Fun Fact: I HAVE configured the WLAN adapter to be able to wake the system from Modern Standby on a RDP request from another system connected to the same WLAN ... but I'd rather figure out how to enable good old WOL using the wired adapter, so for now WLAN adapter is set to off in BIOS)
Secondary Power Settings - Deep S4/S5: Off - tested both On and Off, doesn't really seems to matter for all I'm going to write about WOL below (Fun Fact: even though the description in BIOS suggests that only the Power Button will wake the system if this is set to ON, my mouse and keyboard are still able to wake the system...)
Secondary Power Settings - Wake On LAN from S4/S5: Power On - Normal Boot
Secondary Power Settings - Wake System from S5: Off
Secondary Power Settings - USB S4/S5 Power: Off
Secondary Power Settings - Wake from Thunderbolt Device: On
Secondary Power Settings - PCIe ASPM Support: On
Secondary Power Settings - Native ACPI OS PCIe Support: Off
User Password: Not set
Supervisor Password: Not set

NIC Settings
Speed and Duplex: Automatic negotiation (=Default, results in 1 GBit/s Full Duplex)
Respond to ARP requests without waking system: On (=Default)
Respond to NS requests without waking system: On (=Default)
Wake on Magic Packet: On (=Default)
Wake on Pattern Match: On (=Default)
Wake on Magic Packet from power off state: On (=Default)
Wake on Link: Off (=Default)
Reduce speed when on battery: On (=Default)
Reduce speed when idle: Off (=Default)
Energy Efficient Ethernet: On (=Default, my LinkSys LGS108 switch supports EEE 802.3az)
Compatibility mode for older switches: Off (=Default)
All other settings: Default

Windows Settings
Fast Startup/Hybrid Sleep: Off
"powercfg /AVAILABLESLEEPSTATES" indicates support for Connected Standby, Hibernate and Fast Startup - Standby S1/S2/S3 are not supported by the system firmware (as expected on a system which was installed from scratch using Modern Standby setting in BIOS)
"powercfg /devicequery wake_from_any" indicates Intel I219-V as one of the devices enabled to wake the system from any sleep mode
"powercfg /devicequery wake_programmable" & "powercfg /devicequery wake_armed" only lists HID Keyboard and Mouse
Windows Defender Firewall: Off for all kind of networks
Comodo Internet Security Premium Firewall: Off during testing, still - rules for allowing almost everything on local subnet exist, specifically UDP port 7 & 9 are allowed in for this NUC as confirmed by my WOL sniffer (see below)

WOL Tools used
Aquila Technology LLC "WakeOnLAN 2.12.4" (https://wol.aquilatech.com/)
Marko Oette's "WakeOnLan Tool 2" (https://oette.wordpress.com/wol2/)
"WOL 2.1" from Gammadyne's Free DOS Utilities (https://www.gammadyne.com/cmdline.htm#wol)

WOL Sniffer used
apreltech "Wake-On-Lan Packet Sniffer v1.2" (https://apreltech.com/Blog/Wake_on_lan_Sniffer)
See typical sniffer results on the receiving/target machine below.

Notes:
WOL from OFF/Shutdown State for this NUC is not an issue at all, the system wakes up right away, only Modern Standby WOL not working for now.
When in Modern Standby Link-LEDs show the wired LAN adapter link is available/connected, both on the switch and the NUC itself.
The PC I'm using for sending WOL packets is connected to the same LinkSys LGS108 switch as the Intel NUC target machine.
All WOL Tools used allow changing the port (7 or 9 UDP typically) and can do a BroadCast (255.255.255.255) or subnet directed BroadCast (192.168.1.255).
Since the machines are in the same subnet BroadCast should do just fine.
"WakeOnLan Tool 2" and "WOL 2.1" optionally can send a SecureOn password - since there is no BIOS option to set a SecureOn Password that I can find (only User/Supervisor Password) I leave that blank/don't send a password.

Please, if somebody in the community got this working, share your settings and maybe tools for WOL used.

Thank you so much in advance,
Stay Safe,
Udo


Sniffer Results:
WOL 2.1 command line utility from Gammadyne result:
---------------------------Wake-On-LAN Magic Packet---------------------------

Time received:
07/14/20 08:44:23
UDP Header:
|-Source IP : 192.168.1.x
|-Destination IP : 192.168.1.255
|-Source Port : 50685
|-Destination Port : 9
|-UDP Length : 110
|-UDP Checksum : 36920
MAC Address:
1C 69 xx xx xx xx
Raw Data (102 bytes):
FF FF FF FF FF FF 1C 69 <snip, 16 times repeat of target MAC>

Marko Oette's WakeOnLan Tool 2 result:
---------------------------Wake-On-LAN Magic Packet---------------------------

Time received:
07/14/20 08:53:35
UDP Header:
|-Source IP : 192.168.1.x
|-Destination IP : 192.168.1.255
|-Source Port : 51061
|-Destination Port : 7
|-UDP Length : 134
|-UDP Checksum : 36498
MAC Address:
1C 69 xx xx xx xx
Pasword:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Raw Data (126 bytes):
FF FF FF FF FF FF 1C 69 <snip, 16 times repeat of target MAC>

Aquila Technology LLC "WakeOnLAN" 2.12.4 result:
---------------------------Wake-On-LAN Magic Packet---------------------------

Time received:
07/14/20 08:58:03
UDP Header:
|-Source IP : 192.168.1.x
|-Destination IP : 255.255.255.255
|-Source Port : 9
|-Destination Port : 9
|-UDP Length : 110
|-UDP Checksum : 61396
MAC Address:
1C 69 xx xx xx xx
Raw Data (102 bytes):
FF FF FF FF FF FF 1C 69 <snip, 16 times repeat of target MAC>

0 Kudos
1 Solution
Ronny_G_Intel
Community Manager
4,596 Views

Hi ayavilevich,

I did some digging on this issue and my understanding is that BIOS 0048 which was not released to the Download Center has the fix for this issue so BIOS 0050 should have inherited the fix. In regards to the release notes not listing this fix, not everything is included in the BIOS release notes but I will report it to the Product Team.

Can you also make sure that you have the latest LAN driver version 25.6 running on your system? Link to the latest driver - https://downloadcenter.intel.com/download/25016/Ethernet-Intel-Network-Adapter-Driver-for-Windows-10

 

Regards,

Ronny G

View solution in original post

34 Replies
AndrewG_Intel
Moderator
1,134 Views

Hello all

Thank you for your patience in this matter.

We would like to update this thread and inform you that our team is working on this and we are releasing new BIOS that addresses this issue. Please keep checking https://downloadcenter.intel.com/ for coming updates.


Best regards,

Andrew G.

Intel Customer Support Technician


UdoCologne
Novice
1,131 Views
AndrewG_Intel
Moderator
1,126 Views

Hello @UdoCologne

Thank you for your response. We would like to inform you that we will proceed to close this inquiry for now. If you need any additional information, please submit a new question.


Best regards,

Andrew G.

Intel Customer Support Technician


Ronny_G_Intel
Community Manager
1,120 Views

Hi UdoCologne,

Just to give you some more details, the BIOS that will be addressing this issue will be available by mid-February via our Intel Download Center, please check the following URL https://downloadcenter.intel.com/product/188808/Intel-NUC-10-Performance-kit-NUC10i7FNK by that time and lets us know if you still need assistance.

Regards,
Ronny G

ayavilevich
Novice
1,032 Views

Hi @Ronny_G_Intel , @AndrewG_Intel 

There is a new BIOS update version 0050 for this NUC released in the beginning of March.

Release notes don't mention any changes to WoL. Can you clarify if the new BIOS update addresses the issues in this thread?

Regards,

Arik.

Ronny_G_Intel
Community Manager
4,597 Views

Hi ayavilevich,

I did some digging on this issue and my understanding is that BIOS 0048 which was not released to the Download Center has the fix for this issue so BIOS 0050 should have inherited the fix. In regards to the release notes not listing this fix, not everything is included in the BIOS release notes but I will report it to the Product Team.

Can you also make sure that you have the latest LAN driver version 25.6 running on your system? Link to the latest driver - https://downloadcenter.intel.com/download/25016/Ethernet-Intel-Network-Adapter-Driver-for-Windows-10

 

Regards,

Ronny G

Ronny_G_Intel
Community Manager
1,009 Views

Hi ayavilevich,

More information regarding this issue: under New Fix/Features section in the BIOS release notes, see  "Updated GBE (Gigabit Ethernet) to 0.8 and fixed incorrect SSID issue" this fix is what addresses the issue that you reported on this community.

 

Let me know the results.

 

Regards,

Ronny G

ayavilevich
Novice
989 Views

Hi Ronny,

I installed the BIOS update (V50).

The good news: it seems that now the computer will WOL from the Modern Sleep state.

The bad news:

I have to put it in the sleep state manually (using the windows menu). It doesn't go in to sleep itself even though it is configured for it to go after some time. I am still trying to troubleshoot that.

Sometime it doesn't go to sleep even if manually instructed. Just makes the screen go black. PC keeps running.

WOL from hibernate doesn't work.

 

So there is improvement. Any idea about the other issues? Are those know? Expected?

Regards,

Arik.

UdoCologne
Novice
977 Views

Hi @Ronny_G_Intel@AndrewG_Intel, All,
I've installed BIOS v50 and can confirm that I am now able to wake up the system from both Power-Off and Modern-StandBy states using WOL tools.

Initiating a Remote-Desktop session while the system is in Modern-StandBy wakes it up, too.

Thank you all!

Since Modern-StandBy still seems to be fuzzy about running user initiated maintenance tasks, e.g. backup, on a (nightly) schedule and with the low power draw I'll not be using Modern-StandBy but it is nice to know that once that is out of the way I could wake it up using standard WOL tools.

Thanks again,
Stay safe,
Udo

ayavilevich
Novice
968 Views

Hey Udo

I've installed BIOS v50 and can confirm that I am now able to wake up the system from both Power-Off and Modern-StandBy states using WOL tools.

Does it wake from hibernate for you too or just from complete power off?

Arik.

UdoCologne
Novice
958 Views

Hi @ayavilevich,
I don't use Hibernation on most of my machines, only enabled it on two laptops so far.

So, I never tested Hibernation on the NUC before. Yesterday evening I've enabled Hibernation and did a quick test - I cannot wake up the NUC with the same tool that works for Power-Off and Modern-StandBy states from Hibernation state, too.

Stay safe,
Udo

UdoCologne
Novice
974 Views

@Ronny_G_Intel I hope I clicked 'Accept as solution' successfully

AndrewG_Intel
Moderator
939 Views

Hello @ayavilevich

Regarding WoL from Hibernation, we believe this is a different issue. Everyone's situation and environment are unique so in this case, we kindly recommend creating a new thread to isolate your case and system configuration.


On the new thread, please let us know if you are using Modern Standby or Legacy Standby. Also, please make sure you add the information of the system model and specs, detailed information of the problem that you are having, plus all the information that you have added to this thread, so we can get more information about the problem.

Thank you for your understanding; hope to hear from you soon.


Best regards,

Andrew G.

Intel Customer Support Technician


AndrewG_Intel
Moderator
939 Views

Hello @UdoCologne

Thank you for your response and for your feedback. We are glad to know that after installing BIOS 0050 now you are able to wake up the system from both Power-Off and Modern-StandBy states using WoL (Wake-on-LAN) tools.


Having said that and since the thread has been marked as "Solved" we will proceed to close this inquiry now. If you need any additional information, please submit a new question as this thread will no longer be monitored. Thank you for your efforts, it has been a pleasure to assist you.


Best regards,

Andrew G.

Intel Customer Support Technician


Reply