WOL isn't connecting with AnyDesk or similar tools, remaining stuck in the "Connecting" state during remote sessions?
WOL isn't connecting with AnyDesk or similar tools, remaining stuck in the "Connecting" state during remote sessions?
Hello everyone,
I'm having persistent issues getting Wake on LAN (WOL) to work on my
Alienware Aurora R16 Desktop PC.
I'm trying to wake it remotely using AnyDesk from my Android phone, but it gets stuck at "connecting" with no error message (it times out after like a few mins automatically). The PC's indicator light stays off until I provide physical input (like moving the mouse), at which point it wakes up fully, the lights come on, the monitor turns on, and I can see the login screen both on my phone via AnyDesk and on the PC itself. This suggests the connection request is detected once the PC is manually woken, but WoL isn't triggering the wake automatically.
I've tried a bunch of troubleshooting steps based on online guides and suggestions, including BIOS changes, Windows settings, and alternative apps, but nothing has worked so far. I'd really appreciate any insights, especially from other R16 owners or WoL experts. Below, I'll detail my setup, the exact issue, and everything I've tried.
My Setup
BIOS Version
: 2.17 (latest as of my last check; no updates available via Dell SupportAssist).
Network Adapter
: Killer E3100G Ethernet Controller (wired connection only; no WiFi involved for WoL, as I know WiFi doesn't support it reliably).
OS
: Windows 11 Pro Workstation (fully updated).
Router/Network
: Home network with a standard consumer router. PC is connected via Ethernet cable. My phone is on cellular data for remote tests (outside the home network), but I've also tested locally on WiFi to isolate issues.
Software for WoL
:
AnyDesk (latest version on both PC and Android phone; unattended access enabled with password).
Other apps tried: WakeOnLan (Android app), WolOn (Android app), and a few others like Mocha WoL for testing Magic Packets.
Power State Testing
: I've tested WoL from both sleep/standby (S3) and full shutdown (S5) states. Fast Startup is disabled (more on that below).
MAC Address
: Confirmed via ipconfig /all and used it in app tests.
No VPN/Firewall Blocks
: Windows Defender Firewall allows AnyDesk on private/public networks. No third-party antivirus or VPN interfering.
The goal is to wake the PC remotely over the internet from my phone (e.g., via cellular) so I can access it via AnyDesk without being home.
The Issue in Detail
When I initiate a WoL connection from AnyDesk on my phone (entering the PC's AnyDesk ID and selecting "Wake up" if prompted), it shows "Connecting..." indefinitely (it timed out after a few mins).
The PC remains powered off (indicator light off, no fans spinning, monitor blank).
If I physically interact with the PC (e.g., move the mouse or press a key), it wakes up immediately. At that point, the AnyDesk connection completes almost instantly—I see the login screen on my phone, and everything works fine for remote control.
This happens consistently on remote attempts (cellular). On local network tests (phone on home WiFi).
No wake at all from full shutdown; from sleep.
Other WoL apps (Wake On Lan, WolOn) fail similarly: They claim to send the Magic Packet, but the PC doesn't respond remotely.
I suspect the Magic Packet isn't reaching or triggering the NIC properly, especially remotely, or the PC is in a deep power state where the NIC loses power/listening capability.
This isn't a full connection failure—once manually woken, AnyDesk works perfectly. It feels like the wake signal is either not sent/received or ignored by the hardware.
Methods I've Tried (All in Detail)
I've followed multiple guides, including the AirDroid troubleshooting article on AnyDesk WoL issues, a Dell forum thread on Aurora R16 WoL settings, and other online suggestions. Here's everything step-by-step, including commands and settings changes.
Disabled Fast Startup (Hiberboot)
:
Ran in admin Command Prompt: reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Power" /v "HiberbootEnabled" /t REG_DWORD /d 0 /f
Rebooted to apply.
Verified: reg query "HKLM\System\CurrentControlSet\Control\Session Manager\Power" /v "HiberbootEnabled" – Output shows HiberbootEnabled REG_DWORD 0x0.
This ensures full shutdown (S5) instead of hybrid hibernate, which can interfere with WoL.
Enabled Wake Timers in Power Settings
:
In admin Command Prompt: powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_SLEEP RTCWAKE 1
Then: powercfg /setactive SCHEME_CURRENT (applies to plugged-in/desktop mode).
This allows wake timers without needing the GUI, though it's more for scheduled wakes than pure WoL.
BIOS Changes (Dell-Specific for R16)
:
Restarted and entered BIOS (spammed F2 during boot).
Navigated to Advanced > Power Options/Power Management.
Set "Deep Sleep Control" to Disabled (was Enabled by default).
Enabled "USB PowerShare in S4/S5 state" (to keep power to ports/NIC in low-power states).
Saved and exited.
Rebooted. Note: No direct "Wake on LAN" toggle in this BIOS, which matches what others reported for R16.
Configured Network Adapter Settings (Killer Ethernet)
:
Opened Device Manager > Network Adapters > Right-clicked "Killer E3100G" > Properties.
Power Management tab
:
Checked "Allow this device to wake the computer."
Checked "Only allow a magic packet to wake the computer." (currently unchecked again as i want wider sources)
Checked "Allow the computer to turn off this device to save power" (recommended for Killer to enable low-power listening).
Advanced tab
:
Set "Shutdown Wake-On-Lan" to Enabled.
Set "Wake on Magic Packet" to Enabled.
Set "Wake on Pattern Match" to Enabled.
Updated drivers, systems says so at least.
Checked Killer Control Center software (pre-installed): No conflicting bandwidth/priority settings; disabled unnecessary services temporarily via services.msc (e.g., stopped "Killer Network Service") to test, but re-enabled after no change.
AnyDesk-Specific Settings
:
On PC: Opened AnyDesk > Settings > Security > Enabled "Enable Wake-On-LAN."
Set up unattended access with a strong password.
On phone: Enabled WoL in AnyDesk settings.
Firewall and Network Checks
:
In Windows Security > Firewall > Allowed apps: Ensured AnyDesk is allowed for private and public networks.
Alternative WoL Apps and Tools
:
WakeOnLan (Android)
: Entered PC's MAC address, IP , port 9. Sent packet locallyno response.
WolOn (Android)
: Similar setup; supports secure ON, but same issue—stuck sending remotely, no wake.
Other General Troubleshooting
:
Updated AnyDesk to latest on both devices.
Tested with PC in sleep vs. shutdown.
Read additional forums/guides: Reddit threads on Killer adapters and WoL, Intel docs on E3100G (confirmed WoL support), and general WoL setup articles.
Despite all this, WoL still doesn't trigger remotely and locally. Am I missing something Dell-specific for the R16? Maybe a Killer software conflict or router issue? Has anyone gotten AnyDesk WoL working on this model over the internet without a relay? Open to more ideas.
thanks in advance!
FYI - Related discussion: https://forums. Reference for comments and ideas shared by myself and others. It might be helpful to use Wireshark to inspect the packets. However, I think there could be problems with Killer, so I'll wait for those who are more experienced with it.
You're on the right track. The problem seems to lie in the target PC's configuration settings such as BIOS or drivers.
Here is my current workaround for booting on power restore:
My process includes: placing the PC in sleep or full shutdown, connecting a smart plug to the PC's power source to remotely cut and restore power through an app, enabling "Boot on Power Restore" in BIOS, and automatically resuming when power returns. Note that it may not reopen apps or tabs after waking from sleep.
You might be unsure about how power restoration works versus when the PC just falls asleep and waits for a wake-up signal.
Indeed, it’s essential to confirm that if power drops, the system resumes listening promptly once it regains energy...
That means you should verify the setup so the PC automatically returns to active mode as soon as power is restored.
Depending on your level of interest and willingness to experiment, you may need to adjust how WOL packets are sent from the Raspberry Pi to the device you want to wake.
There are several methods available; generally, the goal is to broadcast specific commands over the network (without using subnets) so that an online PC recognizes its MAC address and reacts.
You can find detailed instructions and a PowerShell script here: https://www.pdq.com/blog/wake-on-lan-wol...owershell/
If you know the target MAC address, you can modify the script to suit your needs.
Be sure to test carefully, paying close attention to any errors that appear during execution—they might point out what’s wrong.
I recommend turning off all other devices or apps on the target PC before proceeding.
Keep it in sleep mode without relying on external tools; just let it wake up automatically when the magic packet arrives.
Make sure the PC is actively listening on its network while asleep, using BIOS/UEFI and the network card.
Check that the broadcast IP address is correct.
You may need to do some additional research to confirm the overall setup of the target system.
Other resources offer clearer guidance: https://www.cleverence.com/articles/tech...asy-guide/
Look for relevant links and verify any configuration settings that might affect this process.
It’s important to follow a systematic approach—draw diagrams of the devices, note connections, and confirm requirements from both ends.
Track each step carefully: ping the target PC from the Raspberry Pi, observe the responses, and use tools like Wireshark to inspect the data.
Always keep backups of critical information in case anything goes wrong.