NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Wake on LAN stopped working on my RN102
Does anyone else currently use WoL on their RN102? I used to use it occasionally, and I can't think what's changed since I last used it. Possibly the 6.2.2 firmware update? I'm using the SimpleWo...
Try using this tool, and see if it works: http://www.depicus.com/wake-on-lan/wake-on-lan-gui.aspx
If the magic packets aren't sent using a broadcast address then WoL can fail. Having a static or reserved IP address on the NAS won't necessarily help. A direct connection to the router won't necessarily help either.
If a packet is directed to an IP unicast address, and the router (for whatever reason) doesn't know the destination ethernet MAC address, then it begins by using a protocol called ARP (http://en.wikipedia.org/wiki/Address_Re ... n_Protocol). This sends a broadcast packet on the LAN, asking for the device to identify itself. This allows the router to (a) use the correct ethernet mac destination and (b) know what ethernet port to route the packet to. If there are intermediate switches, they also update their mac address route tables, so they also know how to direct the packet. (even though people talk about ethernet as being "switched", not "routed", in fact it is routed - using ethernet MAC addresses instead of IP addresses).
If the NAS is off, it won't respond to ARP. ARP fails, and the router drops the magic packet. fwiw, it will work sometimes (when the ARP information is still in the router's cache).
This might not be happening with your app (I don't use it, so I'm not sure). But the software above uses ethernet and IP broadcast, so if it also fails the issue isn't related to ARP.
If the magic packets aren't sent using a broadcast address then WoL can fail. Having a static or reserved IP address on the NAS won't necessarily help. A direct connection to the router won't necessarily help either.
If a packet is directed to an IP unicast address, and the router (for whatever reason) doesn't know the destination ethernet MAC address, then it begins by using a protocol called ARP (http://en.wikipedia.org/wiki/Address_Re ... n_Protocol). This sends a broadcast packet on the LAN, asking for the device to identify itself. This allows the router to (a) use the correct ethernet mac destination and (b) know what ethernet port to route the packet to. If there are intermediate switches, they also update their mac address route tables, so they also know how to direct the packet. (even though people talk about ethernet as being "switched", not "routed", in fact it is routed - using ethernet MAC addresses instead of IP addresses).
If the NAS is off, it won't respond to ARP. ARP fails, and the router drops the magic packet. fwiw, it will work sometimes (when the ARP information is still in the router's cache).
This might not be happening with your app (I don't use it, so I'm not sure). But the software above uses ethernet and IP broadcast, so if it also fails the issue isn't related to ARP.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
