Is the AnyDesk Wake-on-LAN not working on the ASRock Z390 Phantom Gaming 6 motherboard?
Is the AnyDesk Wake-on-LAN not working on the ASRock Z390 Phantom Gaming 6 motherboard?
Dear Experts,
This is my first experience using an unpaid AnyDesk. I am running a Windows 10 desktop with an ASRock Z390 Phantom Gaming motherboard and the latest BOIS firmware. I activated Walk on LAN as per the provided instructions:
https://forum.asrock.com/forum_posts.asp...ake-on-lan
After setting up unattended access, I followed the steps to apply it to the network adapter (Ethernet, not WiFi):
https://support.anydesk.com/knowledge/wa..._to_set_up
To enable Wake-On-LAN in the operating system:
For Windows 7/10:
Open Start menu
Search for “Device Manager”
Expand the “Network Adapters” section
Right-click on the network card and go to Properties
Select Tab "Advanced"
Scroll down to find “Wake on Magic Packet”
Change the value to “Enabled”
Click the Power Management tab
Ensure “Allow this device to wake the computer” and “Only allow a magic packet to wake the computer” are enabled
Click OK
Disable fast startup
Go to Settings
System
Power & Sleep
Additional power settings
Select "what the power buttons do"
Uncheck the option “Turn on fast startup”
For testing, I placed the desktop in sleep mode. I’m uncertain whether it’s necessary to put it to sleep or shut it down completely.
I attempted to access it from my laptop and when I clicked power, the system said “(forget)” and I couldn’t locate a device to start Walk on LAN.
Thank you.
review the BIOS settings once more, as it could be disabled by default after an update.
can you connect to the PC in general?
only when in sleep mode, WOL should function.
if it’s powered off or hibernating, it’s not active.
are you attempting to start it using the internet or LAN?
Your issue probably stems from Microsoft’s choice to add their own sleep, hibernate, and wake functionalities. Despite BIOS now permitting Windows to adjust these parameters, BIOS still lets you manually set them. We require a more user-friendly solution than Microsoft provides.
Wake on LAN has always been unreliable, even years ago, especially when managing large numbers of test servers. You often had to repeatedly issue the wake command for it to function properly.
A more reliable approach is using advanced power adapters that allow remote control of the machine’s power state. You can then activate the BIOS feature for booting on power restoration. This method offers more consistent results.
An added advantage is that many of these adapters support remote access via the internet, enabling server reboots from anywhere.
While some websites claim they can make Wake on LAN work remotely, most of their guidance fails after about 15 minutes. The more reliable options explain the need to address mac timeouts, a feature that requires specialized router capabilities—features rarely found in consumer devices.