Finally I managed to get WOL working the way I wanted it to.
I wanted to use my Diskstation to wake up my pc at home.
For this, the following things needed to be done:
- In the BIOS
- Advanced -> APM Configuration -> Power On By PCI-E -> Enabled
- Advanced -> Network Stack Conf. -> Network Stack -> Enabled
- Advanced -> Network Stack Conf. -> Network Stack -> Ipv4/IPv6 -> Enabled
- In Windows
- Disable the hybrid shutdown mode
- In Control Panel, open the Power Options item.
- Click the Choose what the power buttons do link.
- Clear the Turn on fast startup (recommended) check box (you might need to click “Change settings that are currently unavailable”) first to enable it
- Click Save Settings.
- Enable Wake-on-Lan by Magic Packet in the Device Manager for your Network Adapter
- Install the “Simple TCPIP Services” from the Windows features screen (Not sure if needed)
- Open UDP Port 9 in the Windows Firewall
- Disable the hybrid shutdown mode
- In Diskstation
- In Control Panel -> Task Scheduler, create a new task (User-defined script)
- Enter a name
- Disable it
- For DMS Pre-6.0
- Enter “ether-wake -i eth0 01:02:03:04:05:06” into the run command (adjust the number according to your network adapter’s MAC)
- For DSM after 6.0
- Enter “synonet –wake 01:02:03:04:05:06 eth0” into the run command (adjust the number according to your network adapter’s MAC)
- Click Ok
That’s it. Now you can connect to your Diskstation from any device, load the admin iterface and go to the task scheduler and run this task once to start your workstation.
#
Thanks for this. I’m kind of surprised they have this under “PXE Support” since WOL really has nothing to do with PXE.
#
More info…
I struggled with this for a while, then I realized only one of the NIC’s on the Asus board stays ‘alive’ and linked after shutdown. Apparently that is the bottom NIC. I was using the top NIC. ‘I had chosen… poorly.’
After moving my cable to the bottom NIC, using the respective MAC address, and configuring BIOS settings as you suggested above, I got this working.
#
Cool thanks for the info. I might luckily have used the bottom port so I didn’t face this issue.
#
Thanks. I’ve configured my system and there was no need to enable the steps 1.II and 1.III
#
I just found out that you need to adjust the command after DSM 6.0 to synonet –wake. See my updated post above.
#
What happens if you want to wake up two machines on the network. I currently have one with port-forwarding to port 9 (in router), but what should I do if I want the second NUC to wake up with the command sent to the synology NAS. The wake command specifies the MAC address… can I effectively have both machine’s IP Addresses forward to port 9, or will that mess things up. (I hear you can also use ports 7 or 8 for synonet –wake, however I’m not sure the command issued to the NAS will allow choosing a different port. Thoughts?
#
I’m thinking that if us had both IP addresses (of both computers) have port 9 forwarding, the command when issued from the NAS will only send to the MAC address of the desired machine and so even both machines are port-forwarding to 9, only the specific wake command would apply to the one desired machine. Wonder if anybody’s tried this before.
#
Posting this as I only just came across this issue today (after owning this board for 8 years). Trying to get the system set up to donate to a friend. Anyway, with repect Jason’s post above…
“… I struggled with this for a while, then I realized only one of the NIC’s on the Asus board stays ‘alive’ and linked after shutdown. Apparently that is the bottom NIC. I was using the top NIC. ‘I had chosen… poorly.’
After moving my cable to the bottom NIC, using the respective MAC address, and configuring BIOS settings as you suggested above, I got this working.”
The issue with one port powering down completely at shutdown (Intel i211-AT Controller) has nothing to do with the hardware on the board or BIOS settings. Rather it’s the default state the Intel ethernet drivers appear to set on that controller. Change the WOL setting in the driver’s advanced properties tab (or via the PROSet ANS Configuration tool in recent driver versions) and the i211-AT will remain alive at shutdown just like it’s i219-V sibling. Might come in useful for those using LACP teaming on this setup.