Help LanTurnOn

Help

LanTurnOn Help and FAQ

Getting Started

  1. Add the target device in the app and give it a clear name.
  2. Enter and verify the device MAC address.
  3. Set the correct broadcast or host value and UDP port for your network.
  4. Ensure Wake-on-LAN is enabled in BIOS/UEFI and operating system settings.
  5. Keep both devices on the same local network for initial testing.
  6. Send a wake command and confirm the device powers on.

Device Setup

LanTurnOn is built around saved device entries. In most setups, the fastest way to get reliable results is to configure one device carefully, test it on the same LAN, and only then add more machines or try more advanced networking scenarios.

What information should I enter for a device?

  • Device name: Use a clear label such as Office-PC or Media Server.
  • MAC address: This is required for Wake-on-LAN. If it is wrong, the magic packet will not target the correct network adapter.
  • Broadcast / Host: Many local networks work with a broadcast address such as 255.255.255.255 or 192.168.1.255. Some environments need a different host value.
  • UDP port: Port 9 is common, but your network may require a different port.
  • Group: Optional, but useful when you want to organize several devices such as Office, Lab, or Media.
  • SecureOn: Optional and only needed if the target adapter is configured to require a SecureOn password.
  • TCP probe ports: Optional. These help LanTurnOn check whether a machine is reachable after wake-up.

Why does LanTurnOn ask for a broadcast or host address?

Wake-on-LAN packets still need a network destination. On many home networks, that destination is the subnet broadcast address, but some routers, VLANs, or routed subnets need a more specific host or directed-broadcast target. If waking fails even with the right MAC address, the host value is one of the first settings to review.

How should I choose the UDP port?

Start with the default your network or router expects. Port 9 is common, but not universal. LanTurnOn sends the wake packet using the configured UDP port, so it needs to match what your target environment allows.

Can I organize devices into groups?

Yes. LanTurnOn supports an optional group field so you can keep related devices together and find them more quickly. This is especially helpful if you manage several office machines, lab devices, or media systems.

Can I wake multiple devices at once?

Yes. LanTurnOn includes a Wake all action. It works best when each saved device already wakes reliably on its own.

Can I import or export my saved devices?

Yes. LanTurnOn supports importing and exporting device snapshots, which is useful for backups, moving to a new device, or preparing several entries before testing.

FAQ

What does LanTurnOn do?

LanTurnOn sends Wake-on-LAN magic packets to devices that you save in the app. It is designed to help you wake supported computers and similar devices on your local network, keep them organized, and optionally check whether they come online afterward.

What do I need to add a device in LanTurnOn?

You need the target device MAC address and a Wake-on-LAN configuration that already works on the target machine and network. Depending on your setup, you may also need the correct broadcast host and UDP port in LanTurnOn.

Why does LanTurnOn ask for a MAC address?

LanTurnOn uses the saved MAC address to build the wake packet for the target device. If the MAC address is wrong, the wake command will not reach the correct device.

Does Wake-on-LAN depend only on LanTurnOn?

No. The app can send the correct magic packet, but successful wake-up also depends on the target computer motherboard, firmware, network adapter, operating system, and router or switch behavior.

Do both devices need to be on the same network?

In normal use, yes. LanTurnOn is intended for waking devices on the same local network as the device running the app.

Why does my device not wake up?

  • WoL disabled in BIOS/UEFI.
  • Network adapter wake settings disabled in OS.
  • Incorrect MAC address.
  • Incorrect broadcast or host address.
  • Incorrect UDP port.
  • SecureOn required but not configured correctly.
  • Router/firewall blocking packets.
  • Device is in a power state that does not accept WoL.

Which power states can LanTurnOn wake from?

That depends on the target hardware, firmware, and operating system settings. LanTurnOn can send the wake packet, but the target device must support waking from the current power state.

Can LanTurnOn wake devices over the internet?

LanTurnOn does not provide its own internet relay, VPN, tunneling, or secure remote-access service. The app is designed around local-network wake behavior, although advanced users may be able to make remote wake scenarios work if their own network supports directed routing, firewall rules, and packet forwarding.

Do I need a static IP?

Not always, but DHCP reservation/static assignment can improve reliability and reduce intermittent failures.

Why does LanTurnOn have a broadcast host setting?

LanTurnOn sends the wake packet to the host you configure for that device. Many setups work with a subnet broadcast address such as 192.168.1.255, while others may use a different host value depending on the network.

What is device discovery for?

Device discovery helps scan the local network for reachable machines and related network details. It can be useful when you are collecting host information, but it does not replace verifying the target MAC address and Wake-on-LAN support.

What is status probing for?

LanTurnOn can use TCP probe ports to help show whether a machine appears reachable. This is useful for status feedback after wake-up, but it is not the same thing as Wake-on-LAN itself.

Troubleshooting Checklist

  1. Re-check MAC address in app and on target system.
  2. Verify the configured broadcast or host value for the target subnet.
  3. Verify the UDP port expected by the target network.
  4. Confirm WoL BIOS/UEFI option is enabled.
  5. Confirm OS adapter wake options are enabled.
  6. Confirm the NIC still has standby power when the computer is off or asleep.
  7. Test wake on same LAN first, before trying remote networks.
  8. Try a direct broadcast address such as 255.255.255.255 or your subnet broadcast.
  9. If SecureOn is enabled on the target, confirm the stored value matches exactly.
  10. Temporarily disable network filtering to isolate firewall issues.
  11. Use status probing or another network check to see whether the device comes online after wake.
  12. Reboot router and target machine after settings changes.

Remote Network Notes

Some users want to wake a machine from outside the home or office network. That can work in some environments, but it depends on your own router and firewall configuration rather than on a built-in LanTurnOn relay. You may need port forwarding, a reachable public host name, support for forwarding UDP wake packets, and network hardware that handles directed broadcasts correctly.

If you are troubleshooting a remote setup, first prove that the device wakes reliably on the same local network. Once local wake works every time, then test external routing, DNS, firewall, and forwarding behavior one piece at a time.