Teamviewer wake-on-lan not connecting from public

[vLiiaaM]

I have recently installed and setup Teamviewer for my home pc so I can use it from work.

I've set up my network to allow wake on LAN and it seems to be working correctly when I am at home.

However, as soon as I leave the house and go to work, the pc will not wake when prompted, even though I've tested it at home using the same 4g network on my phone (so a separate network from the one my pc is on) and it works fine.

Any advice would be great because I'm stumped!

 

[captaincharisma]

why not just disable standby mode and leave the computer running with the monitor turned off when away from it? or if you leave the monitor on just setup a screensaver?

 

[bill001g]

You likely have the standard problem because there is no such thing as wake on WAN. The reason it likely works from home is you did not wait many hours after you shut the machine down to test it. The ARP is timing out in your router.

What is happening is you attempting to use a IP address instead of a MAC address. When the machine is shutdown the OS is not running so there are no IP addresses. Wake on LAN sends a very special packet to the broadcast mac address with the mac of your machine in it. It does not use IP addresses.

The reason you can get it to work sometimes is many PC accept data they technically should not to wake. What happens when there is a ARP entry in the router the WoL packet is sent mac of the actual machine rather than the broadcast. When the arp entry times out in the router the router attempt to issue a ARP command to map the IP to the MAC but since the PC is turned off it does not respond to ARP messages so the router never gets a way to remap the ip to the mac.

Bottom line is you likely can not make this work with your router. The best method is a router that you can access remotely and ask it to send a actual WoL packet on your behalf. Asus has this feature. Otherwise you need to have a router that you can put in a static arp which as far as I know only ones with third party firmware. You would need to map a dummy ip to ffff.ffff.ffff mac address. You would also need to put in a port forward to this dummy so you can send from the outside. It works in most cases because most pc ignores the ip headers which technically should not be in the packet