Question Problem with WOL from S5 over internet ?

Aug 2, 2023
4
0
10
I am stumped as to why this won’t work. Wake on lan works perfectly fine from S3 and S5 internally. WOL works every time from S3 externally, but I cannot get it to work from S5 externally and I have no idea what the culprit could be. I have tried many things. If anyone knows or has any ideas on how to make this work it would be much appreciated , thanks.
 
S3 is the sleep state. S5 is full shutdown. Im on windows 11. My network adapter and motherboard both have the option for wake from S5 or Full shutdown. It should be simple. Send the Magic Packet containing the mac address to the PC. It is getting it clearly if it wakes it from sleep. For some reason when it is in full shutdown it is either not receiving the magic packet like it does when it comes from the internal LAN. Or it is reacting different for reasons unknown. If I was having trouble waking the pc from outside the network completely that would be one thing, but its receives the WOL packet just fine when it is sleeping, or when it is shutdown and it comes locally. It is just the one sleep state that refuses to react to an outside packet which there has to be a reason for that in which someone much more experienced probably has a much better idea.
\
 
I am stumped as to why this won’t work. Wake on lan works perfectly fine from S3 and S5 internally. WOL works every time from S3 externally, but I cannot get it to work from S5 externally and I have no idea what the culprit could be. I have tried many things. If anyone knows or has any ideas on how to make this work it would be much appreciated , thanks.
hello, hope you are well, I can give you some tips for troubleshooting Wake on LAN not working externally from sleep state S5
Check router/firewall settings to ensure the magic WOL packet is not blocked externally
Verify WOL utility can reach the target MAC address externally
Disable energy-efficient ethernet on NIC if enabled
Ensure WoL enabled in BIOS
Send magic packet multiple times in case the first fails
Check network logs for where WOL packets are blocked externally
 
This is where microsoft has messed things up. They hijacked the concept of wake on lan and replaced it with their sleep states. It has gotten even more messy because not all bios manufactures support all microsoft sleep states.

If we assume s5 is actually WOL then you likely have the standard wake on WAN issue.

So how do you actually send WoL packets from the internet. Do you have a router you can log into and ask it to send WoL packets or are you using some silly app that send it trying to use IP addresses and ports.

WoL has no concept of IP addresses or port addresses it is purely a mac addresses based thing. Even if you were to get port forwarding setup correctly it generally still does not work. The problem is the ARP entry in the router times out and since the pc is in shutdown mode it does not respond to arps. The nic only gets a ip after the OS is booted.

Pretty much because of the ARP timeout issue you are better off trying to use something other than WOL when you want to activate from the internet. If S3 sleep works (likely the OS in functional and responds to ARP) maybe use that. The power usage difference is extremely tiny.
 
hello, hope you are well, I can give you some tips for troubleshooting Wake on LAN not working externally from sleep state S5
Check router/firewall settings to ensure the magic WOL packet is not blocked externally
Verify WOL utility can reach the target MAC address externally
Disable energy-efficient ethernet on NIC if enabled
Ensure WoL enabled in BIOS
Send magic packet multiple times in case the first fails
Check network logs for where WOL packets are blocked externally
I haven’t checked the network logs that’s probably worth doing to see if there is a difference when I do it In the different sleep states. Although like the person below suggested I think I am just going to concede and be happy with the fact I can do it from S3, and keep the PC in sleep mode and just restart it once in a while 🤷‍♂️ I will overcome my unnecessary fixation on completely powering it off .
 
This is where microsoft has messed things up. They hijacked the concept of wake on lan and replaced it with their sleep states. It has gotten even more messy because not all bios manufactures support all microsoft sleep states.

If we assume s5 is actually WOL then you likely have the standard wake on WAN issue.

So how do you actually send WoL packets from the internet. Do you have a router you can log into and ask it to send WoL packets or are you using some silly app that send it trying to use IP addresses and ports.

WoL has no concept of IP addresses or port addresses it is purely a mac addresses based thing. Even if you were to get port forwarding setup correctly it generally still does not work. The problem is the ARP entry in the router times out and since the pc is in shutdown mode it does not respond to arps. The nic only gets a ip after the OS is booted.

Pretty much because of the ARP timeout issue you are better off trying to use something other than WOL when you want to activate from the internet. If S3 sleep works (likely the OS in functional and responds to ARP) maybe use that. The power usage difference is extremely tiny.
You are more than likely right. That’s what I settled on, I know my urge to have it completely powered down is unnecessary. I’ll probably just give up on it. It’s just me nitpicking at something that is not really a problemz