Réveil sur réseau local Windows 10
Solved
eclispe
-
avion-f16 Posted messages 19182 Registration date Status Contributor Last intervention -
avion-f16 Posted messages 19182 Registration date Status Contributor Last intervention -
Hello,
I am trying to integrate Wake on LAN on my PC and turn it on remotely with HomeAssistant.
I configured my BIOS for Wake on LAN, saved the BIOS settings, the PC turns off, I activate Wake on LAN via Home Assistant, and the PC starts under Windows 10, everything is normal. I shut down my computer to try again, and then the PC won't start. I check my BIOS, nothing has changed, the PC turns off. I redo the procedure, and after exiting the BIOS, the PC turns on, but when I shut down my PC from Windows, Wake on LAN doesn't work anymore. Why?
Thank you for your help.
I am trying to integrate Wake on LAN on my PC and turn it on remotely with HomeAssistant.
I configured my BIOS for Wake on LAN, saved the BIOS settings, the PC turns off, I activate Wake on LAN via Home Assistant, and the PC starts under Windows 10, everything is normal. I shut down my computer to try again, and then the PC won't start. I check my BIOS, nothing has changed, the PC turns off. I redo the procedure, and after exiting the BIOS, the PC turns on, but when I shut down my PC from Windows, Wake on LAN doesn't work anymore. Why?
Thank you for your help.
5 answers
Hello,
First of all, WOL is a very finicky thing.
What is Home Assistant? And how does it wake up the PC? With its IP address or its MAC address using a magic packet that travels across the network? If it uses the IP, there is a chance the router/modem may not redirect it for long after the PC is turned off.
It should also be noted that in Windows 10, at the advanced settings of the network adapter, WOL needs to be enabled.
First of all, WOL is a very finicky thing.
What is Home Assistant? And how does it wake up the PC? With its IP address or its MAC address using a magic packet that travels across the network? If it uses the IP, there is a chance the router/modem may not redirect it for long after the PC is turned off.
It should also be noted that in Windows 10, at the advanced settings of the network adapter, WOL needs to be enabled.
Hello
I usually use https://wol.aquilatech.com/
It’s free, efficient, and straightforward.
The settings for each machine are simple
A+
--
If the answer helped you, a little click on the thumbs up would be great... If resolved, that’s perfect.
Let him who has never opened a user manual throw the first mouse ;-)
I usually use https://wol.aquilatech.com/
It’s free, efficient, and straightforward.
The settings for each machine are simple
A+
--
If the answer helped you, a little click on the thumbs up would be great... If resolved, that’s perfect.
Let him who has never opened a user manual throw the first mouse ;-)
Hi,
as a principle, regarding the PC booting up, the version of Windows or anything else for that matter is not important, since Windows isn’t operational at that point, just a small standalone software on the network card and a standby mode of the network card in the motherboard (power supply and management).
However, if it doesn’t boot after a shutdown through Windows, it might be that Windows is shutting down more things before turning off than the power button does.
--
and ... There you go!
as a principle, regarding the PC booting up, the version of Windows or anything else for that matter is not important, since Windows isn’t operational at that point, just a small standalone software on the network card and a standby mode of the network card in the motherboard (power supply and management).
However, if it doesn’t boot after a shutdown through Windows, it might be that Windows is shutting down more things before turning off than the power button does.
--
and ... There you go!
Hi, I've already noticed that when you play with the WOL settings of the card in Windows, it seems to transfer to the card itself.
Additionally, you definitely need to check the power settings of the card to ensure it isn't turned off with Windows shutdown.
Additionally, you definitely need to check the power settings of the card to ensure it isn't turned off with Windows shutdown.
I found the solution after fiddling with the settings here and there; you need to disable fast startup.
I'm posting the pictures of where to disable it for those who have the same problem as me.
I'm posting the pictures of where to disable it for those who have the same problem as me.
This thing is a kind of sleep mode, I always delete it, I always prefer to restart the PC from scratch, you have a clean environment.
On my network card under power management, there is an option, Allow this device to wake the computer from sleep mode, and Allow only a magic packet to wake the computer from sleep mode. There must be interactions.
On my network card under power management, there is an option, Allow this device to wake the computer from sleep mode, and Allow only a magic packet to wake the computer from sleep mode. There must be interactions.
Hi!
Windows isn't the only one interfering with the functioning of WOL. On Linux, I also need to modify the settings on the interface so that WOL still works after Linux shuts down.
For example, with NetworkManager:
WOL, when enabled at the BIOS/UEFI level, will work after the power supply is turned on, regardless of the OS settings. However, once an OS is loaded, it is possible that this OS disables the functionality at the network card level, rendering the next WOL attempts ineffective.
Windows isn't the only one interfering with the functioning of WOL. On Linux, I also need to modify the settings on the interface so that WOL still works after Linux shuts down.
For example, with NetworkManager:
sudo nmcli c modify myConnection 802-3-ethernet.wake-on-lan magic
WOL, when enabled at the BIOS/UEFI level, will work after the power supply is turned on, regardless of the OS settings. However, once an OS is loaded, it is possible that this OS disables the functionality at the network card level, rendering the next WOL attempts ineffective.
Hi,
That's pretty much what I thought, yes.
Well, I mention this here because I'm interested, but I've never used any WOL, I find it too clunky:
At my place, it's traditional,
a server is on 24/7 and a workstation is used when needed, restarting a server on demand, yuck, risky and a waste of time.
You can't imagine a NAS on WOL....
Moreover, a machine running 24/7 wears out less than a machine that's turned off and restarted, it's well known and proven.
There are numerous examples of servers forgotten in companies that haven't made noise for years, it probably wouldn't have been the same if they had been restarted every day.
Well,
there's energy consumption, but that is regularly decreasing with the performance of components.
That's pretty much what I thought, yes.
Well, I mention this here because I'm interested, but I've never used any WOL, I find it too clunky:
At my place, it's traditional,
a server is on 24/7 and a workstation is used when needed, restarting a server on demand, yuck, risky and a waste of time.
You can't imagine a NAS on WOL....
Moreover, a machine running 24/7 wears out less than a machine that's turned off and restarted, it's well known and proven.
There are numerous examples of servers forgotten in companies that haven't made noise for years, it probably wouldn't have been the same if they had been restarted every day.
Well,
there's energy consumption, but that is regularly decreasing with the performance of components.
So HomeAssistant and my home automation server is waking up with the MAC address.
When you talk about enabling WOL in the advanced settings, are you referring to "Wake on Magic Packet" and "Wake on Pattern Match"?
"Pattern Match" meaning matching with a pattern/profile, we should investigate to see what it is, maybe not activate it, just keep "Wake on Magic Packet" active.