How to set up and use Wake-on-LAN to remotely turn on office computers
Summary
This guide helps you troubleshoot and resolve: How to set up and use Wake-on-LAN to remotely turn on office computers. Follow the steps below to fix the issue.
Common Causes
Wake-on-LAN (WoL) allows you to power on a computer remotely by sending a special network packet, often called a “magic packet”. This is particularly useful for small businesses and home offices that need to perform after-hours maintenance, push software updates, or access files on a workstation without leaving a machine running 24/7. This guide covers the three key stages: enabling WoL in the computer’s BIOS/UEFI, configuring the operating system, and sending the wake-up command from another device on the same network or via a VPN.
Before You Begin
Wake-on-LAN works over a wired Ethernet connection in almost all cases. While some modern computers support “Wake on Wireless LAN” (WoWLAN), it is far less reliable and often disabled by default for security reasons. For a business environment, we strongly recommend using a cabled connection for any machine you intend to wake remotely.
Step 1: Enable Wake-on-LAN in BIOS/UEFI
The first step is to enable the feature at the hardware level. The exact wording varies between manufacturers, but the setting is usually found in the power management or advanced settings section of the BIOS/UEFI.
- Restart the computer you want to wake remotely.
- During startup, press the key to enter BIOS/UEFI setup. Common keys are
F2,Del,F10, orEsc. The correct key is usually displayed briefly on the screen. - Navigate to the Power Management, Advanced, or ACPI settings tab.
- Look for an option named one of the following:
- Wake on LAN
- Power On By PCI-E/PCI
- Resume by LAN
- Remote Wake Up
- Set the option to Enabled.
- If you see a separate option for Wake on Magic Packet, enable that as well. Some systems also have Wake on Pattern Match — this is not required and can cause unintended wake-ups, so leave it disabled.
- Save your changes and exit. The key is usually
F10orF4, but check the on-screen prompt.
Step 2: Configure the Network Adapter in Windows
After enabling WoL in the BIOS, you must also configure the network adapter driver within Windows. This step is often missed and is the most common cause of WoL not working.
- Right-click the Start button and select Device Manager.
- Expand the Network adapters section.
- Right-click your Ethernet adapter (it usually has a name containing “Ethernet”, “PCIe”, “Gigabit”, or the manufacturer name such as Intel, Realtek, or Broadcom) and select Properties.
- Click the Advanced tab.
- In the Property list, look for entries related to Wake-on-LAN. Common names include:
- Wake on Magic Packet
- Wake on LAN
- Shutdown Wake-On-Lan
- Wake on Pattern Match
- Set the value for Wake on Magic Packet to Enabled.
- If you see Shutdown Wake-On-Lan, set it to Enabled as well. This allows the machine to wake from a full shutdown state (S5), not just sleep.
- Click the Power Management tab.
- Tick the following checkboxes:
- Allow this device to wake the computer
- Only allow a magic packet to wake the computer
- Click OK to save the changes.
Step 3: Disable Fast Startup (Recommended)
Windows Fast Startup (also called hybrid shutdown) can interfere with Wake-on-LAN on some systems. When Fast Startup is enabled, the computer enters a hibernation-like state instead of a full shutdown, and some network adapters do not respond to magic packets in this state.
- Open the Control Panel.
- Go to Hardware and Sound > Power Options.
- Click Choose what the power buttons do in the left sidebar.
- Click Change settings that are currently unavailable.
- Under Shutdown settings, untick Turn on fast startup (recommended).
- Click Save changes.
If you prefer to keep Fast Startup enabled for quicker boot times, test WoL with it on first. If the machine does not wake from a full shutdown, disable Fast Startup and test again.
Step 4: Note the MAC Address and IP Details
To send a magic packet, you need the target computer’s MAC address. You will also need to know whether you will send the packet to the computer’s IP address or use a broadcast address.
- On the target computer, open Command Prompt or PowerShell.
- Type the following command and press Enter:
ipconfig /all- Find the Ethernet adapter section that is currently active.
- Note the Physical Address — this is the MAC address. It is a 12-character hexadecimal string, formatted like
AA-BB-CC-DD-EE-FF. - Also note the IPv4 Address and Subnet Mask for the network.
arp -a command from another computer on the same network to view recently cached MAC addresses.Step 5: Send the Magic Packet
There are several ways to send the magic packet. Choose the method that best suits your environment.
Option A: Using a Mobile App (Simplest for Occasional Use)
- On a phone or tablet connected to the same office Wi-Fi network, install a Wake-on-LAN app. Reliable options include Wake On Lan (Android) or Wake Me Up (iOS).
- Open the app and add a new device.
- Enter the target computer’s MAC address and a friendly name (e.g., “Reception PC”).
- If prompted for an IP address or broadcast address, enter the computer’s IP address or the network broadcast address (e.g.,
192.168.1.255). - Tap the device in the list to send the magic packet. The computer should power on within a few seconds.
Option B: Using a Windows Utility
- Download a lightweight WoL utility such as WakeOnLan (by NirSoft) or a similar trusted tool.
- Extract or install the utility and launch it.
- Add a new computer entry.
- Enter the target computer’s MAC address (e.g.,
AA-BB-CC-DD-EE-FF). - Enter the target computer’s IP address or the network broadcast address (e.g.,
192.168.1.255). Using the broadcast address is often more reliable if the IP address might change. - Give the entry a friendly name (e.g., “Office Workstation”) and save it.
- Select the computer from the list and click Wake Up or Send Magic Packet.
- The computer should power on within a few seconds.
Option C: Using PowerShell (For Technicians)
- Open PowerShell on a computer on the same network.
- Run a command similar to the following, replacing the MAC address and IP address with your target’s details:
$mac = "AA-BB-CC-DD-EE-FF" $ip = "192.168.1.255" $bytes = $mac -split '[-:]' | ForEach-Object { [convert]::ToByte($_, 16) } $packet = [byte[]](,0xFF * 6) + ($bytes * 16) $udp = New-Object System.Net.Sockets.UdpClient $udp.Send($packet, $packet.Length, $ip, 7)- Press Enter to send the packet.
- The target computer should power on if WoL is correctly configured.
Step 6: Troubleshooting
Wake-on-LAN can fail for several reasons. Work through these checks if the target computer does not power on.
The PC does not wake from a full shutdown
- Confirm that Shutdown Wake-On-Lan is enabled in the network adapter’s Advanced tab.
- Disable Fast Startup as described in Step 3.
- Check the BIOS/UEFI for Wake on LAN from S4/S5 and ensure it is enabled.
Network adapter loses power when off
- Look at the network port on the back of the computer while it is powered off. A blinking or steady amber/green LED usually indicates the adapter is receiving standby power and can receive a magic packet.
- If there is no light at all, the network interface may be fully powered down. Check BIOS power settings and disable Deep Sleep or ErP Ready modes.
Router or firewall blocking broadcast packets
- By default, many routers do not forward broadcast packets across subnets. If you are waking a computer on a different VLAN or subnet, enable directed broadcast forwarding or WoL forwarding on your router or Layer 3 switch.
- If using a VPN, ensure the VPN tunnel allows broadcast traffic or use IP-directed broadcast to the remote subnet’s broadcast address. VPN “hairpinning” (sending traffic out and back into the same interface) can also prevent magic packets from reaching the target.
ARP cache expiry
- If the target computer has been off for a long time, the router’s ARP table may no longer map its IP address to its MAC address. Sending a magic packet to a stale IP will fail.
- Ping the target computer’s IP address from another device on the network just before sending the magic packet. This refreshes the ARP entry and improves reliability.
NIC driver issues
- Ensure the network adapter driver is up to date. Visit the manufacturer’s website (Intel, Realtek, Broadcom, etc.) and install the latest driver for your model.
- After updating the driver, repeat Step 2 to confirm WoL settings are still enabled, as driver updates can reset adapter properties.
IP address changes
- If you are sending the magic packet to a specific IP address rather than a broadcast address, confirm the target computer still has that IP. Use a DHCP reservation or static IP as recommended in the prerequisite note.
If you have checked all the above and the computer still will not wake, please Open a Ticket for assisted support.
Still Having Issues?
đź’» Open a Ticket