A powered-off device cannot be reached at all. Remote power-on completes the loop — wake first, then connect — and is the missing piece of true unattended access.
Two ways to wake
Wake-on-LAN depends on motherboard and NIC support and needs the network card to keep receiving power while off. A smart plug controls power at the hardware level and is far more compatible.
- Wake-on-LAN: enable WOL in BIOS and the NIC
- Smart plug: hardware-level control, wide compatibility
- Both need the device powered and connected
- Combine them for a higher success rate
Setup steps
Enable the power management options in BIOS, allow the NIC to wake the machine in the OS, then bind the device and wake method in the client and test it.
- Enable Wake on LAN and power-recovery policy in BIOS
- Allow the NIC to wake the computer in the OS
- Bind the smart plug or WOL device in the client
- Shut down and rehearse the wake flow once
When waking fails
Failures usually come from power, BIOS settings or the network path. Waking across subnets needs the router to forward magic packets; in some environments a smart plug is simply more reliable.
- Confirm power and network cable are connected
- Cross-subnet wake needs broadcast forwarding
- Laptop lid and battery policies may block wake
- Wi-Fi adapters rarely support WOL — use a smart plug
FAQ
Can a shut-down machine still wake?
Desktop PCs and some laptops with WOL can. If the device is fully powered off or the environment does not support it, use a smart plug.
How long until I can connect?
Usually one to two minutes for boot and client startup; machines with mechanical disks or many startup items take longer.