Wake-on-LAN (WoL) is a network standard that allows you to remotely connect a computer, whether it is asleep, sleep, or even completely disconnected. It works by receiving the so-called “magic packet”, which is sent from the WoL client.
It also does not matter what operating system the computer will boot into (Windows, Mac, Ubuntu, etc.), you can use Wake-on-LAN to turn on any computer that receives a magic packet. The computer hardware must support Wake-on-LAN with a compatible BIOS and network interface card, so not every computer can automatically use Wake-on-LAN.
The first thing you need to do to enable WoL is to set up the BIOS correctly so that the software can listen for incoming wake up requests.
Each manufacturer will have unique steps, so what you see below cannot accurately describe your installation. If these instructions do not help, find out your BIOS manufacturer and check their website for a user guide on how to enter the BIOS and find the WoL function.
Windows Wake-on-LAN is configured through the device manager. Here you can configure several settings:
Now that the computer is fully configured to use Wake-on-LAN, you need a program that can send the magic packet that is required to start the run. TeamViewer is one example of a free remote access tool that supports Wake-on-LAN. Since TeamViewer is designed specifically for remote access, its WoL feature is convenient for those times when you need to your computer when idle, but forgot to turn it on before you left.
TeamViewer can use Wake-on-LAN in two ways. One of them is through the public IP address of the network, and the other is through another TeamViewer account on the same network (provided that this other computer is turned on). This allows you to wake up the computer without configuring the router ports (more on this below), since another local computer where TeamViewer is installed can relay the WoL request internally.
Another great Wake-on-LAN tool is Depicus, and it works from different places. You can use your WoL function through your website without downloading anything, but they also have a GUI and command line tool available for both Windows (free of charge) and MacOS, as well as for mobile applications Wake-on-LAN for Android and iOS.
Some other free Wake-on-LAN apps include Wake On LAN for Android and RemoteBoot WOL for iOS. WakeOnLan is another free WoL tool for macOS, and Windows users can also choose the Wake On Lan Magic packages.
If you followed the steps above, it turned out that your device supports Wake-on-LAN without any problems, but when you try to turn on the computer it still does not work, you may also need to turn it on through the router. To do this, you need to log in to your router to make some changes.
A magic packet that runs on a computer is usually sent as a UDP datagram over port 7 or 9. If this is the case with the program that you use to send a packet, and you try to do it from outside the network, you need to open these ports on router and redirect requests to every IP address on the network.
Redirecting WoL magic packets to a specific client IP address will be meaningless, as the computer with the power off does not have an active IP address. However, since port forwarding requires a specific IP address, you must ensure that the port (s) are redirected to the so-called broadcast address so that it gets to each client computer. This address is in *. *. *.
For example, if you specify the IP address of your router as 192.168.1.1, use the address 192.168.1.255 as the forwarding port. If this is 192.168.2.1, you should use 192.168.2.255. The same is true for other addresses, such as 10.0.0.2, which will use the IP address 10.0.0.255 as the forwarding address.
You might also want to consider signing up for a Dynamic DNS (DDNS) service, such as No-IP. Thus, even if the IP address associated with the WoL network changes, DNS will update to reflect this change and still allow you to wake the computer. DDNS service is really useful only when you turn on the computer from outside the network, for example, from your phone when you are not at home.
Also consider using Action1 to use Wake-on-LAN if: