Wake on LAN stopped working on my RN102

Are you using the app over the internet (or cellular data), or are you using it on your local WiFi?

One problem with most of these apps is that very few routers forward broadcast packets. So the apps send to the router's WAN IP address, and the WoL packet needs to be forwarded to the NAS IP address by the router.

Failure modes include (a) NAS IP address changing (b) the router WAN IP changing (if no DDNS) and (c) the router+switches not knowing how to route the packets to the NAS.

On (c) - when the NAS is not responding, both the router and any switches eventually "forget" how to reach the port the NAS is connected too. The protocols for re-discovering that information require the NAS to respond.

I have an WoL add-on installed on my pro. I use that to wake my client PCs, but leave the NAS running 24-7. That works because the NAS is sending ethernet broadcast packets, which always reach the full network.

Thanks for all the info on possible issues. Unfortunately, I don't think it applies to my set-up.

My RN102 has a direct ethernet connection to the wireless ADSL modem/router, and I'm sending the magic packets within my LAN. So, I've got a simple set-up and the IP of my NAS has not been changed.

I schedule my NAS to come on for a few hours each evening, but I prefer to leave it off for as much as possible and WoL it when it's needed.

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.

Thank you very much, it's now working! :D

After using the Windows tool it made me realise that SimpleWoL was a bit too simple and did not allow the configuration of subnet or broadcast. I now have an app called RemoteBoot which is working perfectly.

Thank you for your time and all of the information you've provided to get to the bottom of this problem.