If we look at WOL as a rube goldberg machine, TeamViewer has a 'Pea-shooter' function to start off the machine. But if there is a problem with your mail server not correctly receiving or sending mail, this is outside of the scope of support of the mail client. Lets say you have an email client (say, thunderbird) this client will manage your mail for you and is the service this program offers. You can also enter a static IP address if you have one and go through some port forwarding, but TeamViewer cannot control or streamline this process. This bypasses the need for port forwarding in this case as the signal itself comes from inside the network. We also have the ability to send a command to an online computer inside your network, and have that device send a Magic Packet inside the Local Area Network. TeamViewer offers the ability to send Wake on LAN commands (Magic Packets) to wake up a device inside a Local Area Network. You just fire a packet at your public IP (Or bounce it off a DNS server), bounce it through some port forwards and hope it hits your Computer on the other side without getting filtered. To be honest, Wake On LAN using a public IP is the technical equivalent of a Rube Goldberg machine as the remote computer is for all intents and purposes, offline and there is no active communication.

Wake On LAN is actually originally intended for local networks only (Wake On Local Area Network) This feature wakes the device from sleep if a specific command (Magic Packet) is received by the network card. Wake On LAN is a hardware feature of many network cards. Wake on LAN is not a simple process and there are no hard and fast instructions that will guarantee success.īecause of this, I am sorry for my long winded response but I will try to explain why this is a complex issue and there is no easy fix or answer that we can provide.

In regards to this issue, unfortunately there is no easy answer to any of these questions and we cannot diagnose all the possible problems here.

Teamviewer wake on lan tutorial