F5F Stay Refreshed Power Users Networks WOL help

WOL help

WOL help

M
Mr_D_Trump
Junior Member
30
02-05-2016, 04:05 PM
#1
For Wake on LAN you need to adjust the device manager settings carefully. You can send the magic packet successfully and reach the target machine without issues, but sometimes the Wake on Land (WOL) fails. It seems the "Allow this computer to turn off this device to save power" option must be enabled alongside "Allow this device to wake the computer." Make sure both are checked properly—otherwise the PC might disable the adapter when trying to wake the system. Double-check your settings and ensure they align with your expectations.
M
Mr_D_Trump
02-05-2016, 04:05 PM #1

For Wake on LAN you need to adjust the device manager settings carefully. You can send the magic packet successfully and reach the target machine without issues, but sometimes the Wake on Land (WOL) fails. It seems the "Allow this computer to turn off this device to save power" option must be enabled alongside "Allow this device to wake the computer." Make sure both are checked properly—otherwise the PC might disable the adapter when trying to wake the system. Double-check your settings and ensure they align with your expectations.

S
superfalcong
Junior Member
42
02-10-2016, 07:38 AM
#2
Windows blocks WOL during shutdown. The device needs to be in sleep mode for WOL to work reliably. The options you see here are accurate.
S
superfalcong
02-10-2016, 07:38 AM #2

Windows blocks WOL during shutdown. The device needs to be in sleep mode for WOL to work reliably. The options you see here are accurate.

U
ultra_blue1
Junior Member
14
02-17-2016, 05:13 AM
#3
Your system seems to have inconsistent behavior during shutdown. Even though fast boot is disabled and you expect S5 to activate, it doesn’t always happen. This could be due to other factors like BIOS settings, power management configurations, or hardware limitations. Checking the BIOS options for wake-on-lantern support and ensuring stable power delivery might help.
U
ultra_blue1
02-17-2016, 05:13 AM #3

Your system seems to have inconsistent behavior during shutdown. Even though fast boot is disabled and you expect S5 to activate, it doesn’t always happen. This could be due to other factors like BIOS settings, power management configurations, or hardware limitations. Checking the BIOS options for wake-on-lantern support and ensuring stable power delivery might help.

E
EmperorDerp
Junior Member
8
02-17-2016, 07:01 AM
#4
BIOS configurations typically exist in two locations: one for enabling the network interface and another for keeping the NIC active. Many systems also require a backup power source to maintain operation after a power interruption before restarting.
E
EmperorDerp
02-17-2016, 07:01 AM #4

BIOS configurations typically exist in two locations: one for enabling the network interface and another for keeping the NIC active. Many systems also require a backup power source to maintain operation after a power interruption before restarting.

B
boom1shot
Member
127
02-17-2016, 07:18 AM
#5
Thank you for your response. It seems your BIOS configurations appear to be accurate. You've also adjusted the WOL feature from S5, though it sometimes fails. The power drop is intriguing, but your server has maintained 173 days of continuous operation, and the UPS will notify you during outages.
B
boom1shot
02-17-2016, 07:18 AM #5

Thank you for your response. It seems your BIOS configurations appear to be accurate. You've also adjusted the WOL feature from S5, though it sometimes fails. The power drop is intriguing, but your server has maintained 173 days of continuous operation, and the UPS will notify you during outages.

V
vuur123
Member
163
02-22-2016, 12:14 PM
#6
It’s actually the windows that are causing this problem. I’ve been experiencing it for many years. Try setting your PC to sleep and observe its performance. Windows 8 altered the WOL settings, while Windows 10 made things worse. WOL isn’t compatible with S4 and S5 since Windows 8 was released, even if your hardware can handle WOL in S5. Windows assigns the NIC to D3 whenever you initiate a shutdown, regardless of your WOL preferences. WOL works consistently only from S3, which activates during sleep mode on Windows (and sometimes S4 during hibernation, though not always).
V
vuur123
02-22-2016, 12:14 PM #6

It’s actually the windows that are causing this problem. I’ve been experiencing it for many years. Try setting your PC to sleep and observe its performance. Windows 8 altered the WOL settings, while Windows 10 made things worse. WOL isn’t compatible with S4 and S5 since Windows 8 was released, even if your hardware can handle WOL in S5. Windows assigns the NIC to D3 whenever you initiate a shutdown, regardless of your WOL preferences. WOL works consistently only from S3, which activates during sleep mode on Windows (and sometimes S4 during hibernation, though not always).

T
TimeGod9870
Junior Member
19
02-22-2016, 05:19 PM
#7
They say it's about saving energy. Because Windows can't tell the difference between a phone with a battery and a device running on constant power, so the Wake-on-Lan option was reduced.
T
TimeGod9870
02-22-2016, 05:19 PM #7

They say it's about saving energy. Because Windows can't tell the difference between a phone with a battery and a device running on constant power, so the Wake-on-Lan option was reduced.