Wake-on-LAN Not Working From iPhone: The Failure Checklist
Short version. Sent from your iPhone, PingKit can only tell you that the magic packet was sent, because a magic packet is fire-and-forget UDP and nothing answers it. So every Wake-on-LAN failure is on the other machine or on the path to it, and the causes have a reliable order: Fast Startup on Windows, a machine that is shut down rather than asleep, Wake-on-LAN disabled in firmware or in the adapter's power settings, a wake attempt over Wi-Fi rather than Ethernet, and a wrong MAC address. Work down that list, then verify with Ping rather than by looking at the screen. The happy-path setup is in How to Wake Your Computer Remotely with iPhone; this page is for when it does not work.
Wake-on-LAN, Ping and Port Scanner are free, with all 19 tools. No ads, no account.
What the App Can and Cannot Tell You
A magic packet is six bytes of 0xFF followed by the target's MAC address repeated sixteen times[source]. PingKit sends it as a UDP broadcast onto the local network, with no reply expected and none possible. Nothing acknowledges it. So The Best Wake-on-LAN App for iPhone reports "Magic packet sent" for a wake sent from the phone, never "the machine woke". The only honest way to report more is to watch for the machine afterwards, which a wake through your Mac does when it knows the machine's address.
That is the good news, in a way: it means the app's part either worked or it did not, and everything else in the chain is on the target machine or the network between. The checklist below is in the order these actually turn out to be the cause.
1. Windows Fast Startup
This is the most common single cause on Windows, and it is on by default wherever hibernation is enabled, which is most desktops and many laptops. Fast Startup makes a shutdown into a hybrid hibernation, and in that state the network adapter is powered down in a way that ignores magic packets. The machine looks shut down, behaves shut down, and cannot be woken.
Turn it off in Control Panel › Hardware and Sound › Power Options › Choose what the power buttons do › Change settings that are currently unavailable, then clear Turn on fast startup. Restart once afterwards so the machine actually leaves the hybrid state.
2. Asleep Versus Shut Down
Wake-on-LAN wakes a sleeping machine reliably. Whether it can power on a machine that is fully shut down depends entirely on the firmware and the adapter, and on plenty of hardware it cannot. If you are testing with a machine you powered off, put it to sleep instead and test again: that one change resolves a large share of "it never works" reports, and it also tells you which of the two problems you have. A Synology NAS is the other way round: Synology says it wakes only after a proper shutdown, as the Synology Wake-on-LAN guide explains.
Wake-on-LAN, Ping and Port Scanner are free in PingKit, with no account and no ads.
3. Wake-on-LAN Disabled in Firmware or in the Adapter
There are two switches, and both have to be on:
- Firmware. In the BIOS or UEFI setup, usually under Power Management, named "Wake on LAN", "Wake on PCIe", "Power on by PCI-E" or "Resume by LAN" depending on the vendor. Enable it.
- The operating system's adapter settings. On Windows, Device Manager, the Ethernet adapter, the Power Management tab: Allow this device to wake the computer must be ticked, and Only allow a magic packet to wake the computer should be as well. On some Intel and Realtek adapters there is also a Wake on Magic Packet entry under Advanced that has to be enabled separately. On Linux the second switch is
ethtool, and it can reset at every reboot: Wake-on-LAN on Linux and Ubuntu makes it stick.
4. Wi-Fi Instead of Ethernet
Waking over Wi-Fi rarely works, and it is not a bug. A wireless adapter in a low power state is usually not associated with the access point at all, so there is no radio link for a broadcast to arrive on. Some laptops support a wake-on-wireless mode, most do not, and the ones that do often only honour it from sleep rather than from a deeper state.
If the target machine is on Ethernet, this is not your problem. If it is on Wi-Fi, this is very likely your only problem, and the fix is a cable.
The iPhone's side of this is separate and simpler: PingKit's Wake-on-LAN screen sends its own packet only when the phone has a Wi-Fi or Ethernet interface up. A broadcast has to be put onto the local network, and a phone on cellular has no local network to put it on, so without Guardian the screen shows Wi-Fi Required. With Guardian and a Mac at home that is awake and running PingKit Agent, it offers Wake from anywhere instead: the Mac sends the packet on its own network, then, when it knows the machine's address, pings it to tell you whether it woke.
PingKit also needs Local Network access to send the packet: if it is off, turn it on in Settings, Privacy & Security, Local Network. If you have never allowed it, the Wake Device shortcut in Siri and Shortcuts asks you to open PingKit first.
5. The MAC Address Is Wrong, or Is Not the Right One
This is the cause people check last and should check earlier, because a wrong address fails in exactly the same silent way as everything above. Three things go wrong here:
- The address is for the wireless adapter and the machine is waking from Ethernet, or the other way round. A laptop has at least two, and they are different addresses.
- A digit was transposed. A magic packet with a wrong address is sent successfully and wakes nothing.
- The machine has a virtual adapter, from a VM host or a VPN client, whose address was picked up instead of the real one.
Where to get the right address, in order of reliability:
| Source | How |
|---|---|
| The target machine itself, always first | Windows: ipconfig /all in a Command Prompt, and read Physical Address under the adapter that is actually plugged in. macOS: System Settings, Network, the interface, Details, Hardware. Linux: ip link |
| The router's DHCP client table, second | Every consumer router lists leases with hardware addresses next to hostnames. Useful when the machine is already asleep |
| The Mac Agent, for a device it knows | PingKit Agent's Wake-on-LAN tool lists devices it holds an address for. On macOS 27, Agent 3.3.0 or later reads them for new devices too; an older Agent there learns no new ones and covers only machines it recorded before that upgrade. Typing an address by hand always works |
| The iPhone, depends on iOS | On iOS 27 and later, PingKit shows most devices' MAC addresses on their detail screens. On iOS 17 to 26, iOS hides most devices' hardware addresses from apps, answering with 02:00:00:00:00:00, a placeholder rather than a real address, so for most devices PingKit on iPhone shows no MAC address there. Read it from the machine itself or the router |
Typing it into PingKit: open Wake-on-LAN, tap the add button, and enter a name and the address. If the address is already saved under another name the sheet says so, because a magic packet is addressed by hardware address and a second entry with the same one is a second name for one machine. A saved device cannot be edited. To change an address, swipe the row away and add it again.
6. The Broadcast Address and the Port
Both live in the Advanced section of the Add sheet, and both are usually correct by default. The broadcast address defaults to 255.255.255.255 and the port to 9.
- When to change the broadcast address: rarely. When PingKit knows your subnet, it already sends each wake both to your subnet's broadcast address, such as
192.168.1.255on a192.168.1.0/24network, and to255.255.255.255, because routers differ in which one they pass on. Change it when the target is on a different subnet from the phone, to the directed broadcast for the target's subnet. If the two are on genuinely different subnets, the router has to be willing to forward a directed broadcast, and most consumer routers are not. - When to change the port: almost never. Port 9 is the discard port and is the conventional target; some tools use 7. If the machine was set up with a tool that used 7, match it. A wake sent through your Mac (Wake from anywhere) always goes out on port 9 to your home network's broadcast addresses, whatever port and broadcast address you saved here.
7. Verify the Wake, Do Not Look at the Screen
A machine can wake, find nothing to do and go straight back to sleep, which looks exactly like a wake that never happened. Verify on the network instead:
- Send the packet.
- Open Ping in the Tools tab, enter the machine's address, and send twenty packets. Replies mean it is up.
- If you need a service rather than a host, open Port Scanner and check the port you actually want: 3389 for Windows Remote Desktop, 22 for SSH, 445 for Windows file sharing, 5900 for VNC and screen sharing. A host that answers ping but not the port has woken and not finished starting its services, which is a wait rather than a failure.
This also settles arguments about whether the packet is reaching the machine at all: a machine that never answers ping after a successful send has not woken, and the cause is one of items 1 to 5.
Still Nothing: the Two Remaining Causes
- The switch or the router is not forwarding the broadcast. Some managed switches with storm control, and a few mesh systems, drop broadcast traffic between ports. Test from a machine on the same wired segment to confirm.
- The machine lost power completely. A network adapter keeps a small amount of standby power to listen for magic packets. A power cut, a switched-off socket or a tripped surge protector clears that state, and the first wake after power returns will fail even with everything configured correctly.
Honest Limits
- Sent from the iPhone, PingKit reports that the packet was sent and no more, because a magic packet is never acknowledged. Through your Mac, the Mac pings the device's address to watch for up to two minutes afterwards and reports whether it answered.
- On iOS 17 to 26, for most devices the iPhone cannot find a MAC address for you, because iOS hides other devices' hardware addresses from apps. That is an iOS restriction, not a missing feature; on iOS 27 and later PingKit shows most devices' MAC addresses.
- Sent from the iPhone, Wake-on-LAN needs the phone on the same local network, and PingKit refuses to send from cellular. Waking from anywhere needs Guardian and a Mac at home, awake and running PingKit Agent on the same network as the machine; PingKit Agent on a Raspberry Pi, NAS or Home Assistant that stays on can send it through PingKit's relay instead. Nothing is forwarded over the internet to the machine itself. If you would rather forward a port on your router yourself, waking a PC remotely from an iPhone covers that route and where it breaks.
- A saved device can be woken or deleted, not edited.
- Whether a fully powered-off machine can be woken at all is a firmware question that no app can change.
Frequently Asked Questions
Why does Wake-on-LAN say sent but my computer does not wake?
A magic packet is fire-and-forget UDP, so "sent" only means it left the phone. The usual causes, in order: Windows Fast Startup is on, the machine is shut down rather than asleep, Wake-on-LAN is disabled in firmware or in the adapter's power settings, the target is on Wi-Fi rather than Ethernet, or the MAC address belongs to a different adapter.
Does Wake-on-LAN work over WiFi?
Rarely, and it depends on the hardware. A wireless adapter in a low power state is usually not associated with the access point, so there is no link for a broadcast to arrive on. A cable to the target machine is the reliable answer. Separately, the iPhone sending the packet must itself be on Wi-Fi or Ethernet, because the packet is a local broadcast; away from home, with Guardian, a Mac at home that is awake and running PingKit Agent sends it instead.
Can I wake my computer from outside my home network?
Yes, with Guardian and a Mac at home running PingKit Agent. A magic packet is a broadcast onto the local network, so the iPhone sends its own only over Wi-Fi or Ethernet. Away from home the Wake-on-LAN screen asks your Mac instead, through your iCloud: the Mac sends the packet on its own network and tells you when the machine answers. The Mac has to be awake, running the Agent and on the same network as the machine. No Mac at home? PingKit Agent on a Raspberry Pi, NAS or Home Assistant that stays on can send the packet instead, through PingKit's relay with Guardian; its answer means the packet was sent, not that the machine woke.
How do I find the MAC address for Wake-on-LAN?
From the target machine first: ipconfig /all on Windows and read the Physical Address of the adapter that is plugged in, or System Settings, Network, Details, Hardware on a Mac. The router's DHCP client table is the second source. On iOS 27 and later, PingKit shows most devices' MAC addresses on their detail screens; check that it is the adapter that is plugged in. On iOS 17 to 26 an iPhone is not a dependable source: iOS hides most devices' hardware addresses from apps, answering with 02:00:00:00:00:00.
How do I check whether the computer actually woke?
Ping it. Send twenty packets to its address from PingKit's Ping tool; replies mean it is up. If you need a specific service, scan the port you want, 3389 for Remote Desktop or 22 for SSH. A machine that answers ping but not the port has woken and is still starting services.
Can I edit a saved Wake-on-LAN device in PingKit?
No. A saved device can be woken or swiped away to delete. To change a MAC address, broadcast address or port, delete the entry and add it again.
Send the packet, then prove it worked.
Free to download, with all 19 tools and no ads. Guardian is $2.99 a month or $24.99 a year on iPhone or Mac, with a 1-week free trial. Cancel anytime.
Download PingKit for iPhoneRelated Articles
- The Best Wake-on-LAN App for iPhone
- How to Wake Your Computer Remotely with iPhone (Wake-on-LAN)
- Wake-on-LAN for Windows 11 From an iPhone: The Full Setup
- Port Scanner App for iPhone
- Best Wake-on-LAN Apps for iPhone, Mac, Windows and Android (2026)
- Wake-on-LAN from a Mac (2026): Setup That Actually Works
- Wake-on-LAN on Linux, Ubuntu and Proxmox From an iPhone
- Wake-on-LAN for a Synology NAS From an iPhone: The Full Setup