I have a problem with Wake On LAN (WOL) and wonder if anyone can help?
First of all I'll explain the setup.
The PC I am trying to Wake uses a Gigabyte GA-890GPA-UD3H motherboard with an onboard network card which does support WOL.
It is connected to a CISCO WRT320N router which is in turn, of course, connected to the internet.
Power on by "PME" event is enabled in the BIOS. I can send a magic packet on the local network either from my laptop or my android phone (using an app called aWOL) and this does wake up the PC fine.
When I send a magic packet over the internet (via 3G) it does wake the PC if it's recently been turned off. For some reason if the PC has been switched off for a while the magic packet does not wake the PC.
The PC has not gone into a low power state because if I send a packet locally on the LAN it DOES still wake the PC. If I then shut it down and wake it up over the WAN it starts up fine.
If I send packets to the PC while I have wireshark monitoring port 9 it receives all packets (both local and over WAN) fine.
I can't understand why a packet send over the WAN won't wake the PC if it's been off for a while. Does this make sense to anyone out there? I can provide Wireshark captures if anyone needs to see them.
Thanks for any help.
Brian
First of all I'll explain the setup.
The PC I am trying to Wake uses a Gigabyte GA-890GPA-UD3H motherboard with an onboard network card which does support WOL.
It is connected to a CISCO WRT320N router which is in turn, of course, connected to the internet.
Power on by "PME" event is enabled in the BIOS. I can send a magic packet on the local network either from my laptop or my android phone (using an app called aWOL) and this does wake up the PC fine.
When I send a magic packet over the internet (via 3G) it does wake the PC if it's recently been turned off. For some reason if the PC has been switched off for a while the magic packet does not wake the PC.
The PC has not gone into a low power state because if I send a packet locally on the LAN it DOES still wake the PC. If I then shut it down and wake it up over the WAN it starts up fine.
If I send packets to the PC while I have wireshark monitoring port 9 it receives all packets (both local and over WAN) fine.
I can't understand why a packet send over the WAN won't wake the PC if it's been off for a while. Does this make sense to anyone out there? I can provide Wireshark captures if anyone needs to see them.
Thanks for any help.
Brian