Wake-On-LAN: Anybody Got It Working?

I, too, have Ultra 6s with WOL issues. I opened a trouble ticket with Netgear support on 17 December 2010 and we have been chasing this down ever since. Netgear sent me the 6/10/10 BIOS update, which fixed the scheduled-wake problem, but (as others here have reported) WOL only works after a Frontview shutdown, not after a power-button shutdown or a scheduled power-off.

For the last three weeks my backup Ultra 6 has been stripped of its content, with port 22 opened for Netgear's SSH engineering access, with no progress to date. I'll let 'em know I'm not the only one with this WOL problem, and maybe things will move along...

FWIW, I don't see this problem at all with the Pro Pioneer and Pro Business systems we have, only with the Ultras.

adamwilt wrote:
For the last three weeks my backup Ultra 6 has been stripped of its content, with port 22 opened for Netgear's SSH engineering access, with no progress to date. I'll let 'em know I'm not the only one with this WOL problem, and maybe things will move along...

I wouldn't agree to that. This is a consistent and easily reproducible problem, from what I gather after reading forums and testing it on my own Ultra 4 Plus. It shouldn't take them 2 seconds to reproduce it on their own hardware!! Why should they use yours. Thats sounds like REALLY bad customer service... Or is it just me being too critical?

Larswa wrote:
Thats sounds like REALLY bad customer service... Or is it just me being too critical?

The picture I get from experience and reading the experiences of others:

• The Phone-in system is not working the way NetGear thinks it should work. One of the level-3 guys spelled out how it is supposed to work for me and it sounded perfectly reasonable. But my experience suggests that it is not working that way... not even close. Cannot comment on the web-driven system bc I have not used it.

• Comments from others suggest that NetGear has unexpected problems with released products and their Level-3 people are currently over-worked.

• My experience is that the Level-3 people are great once you get their attention. The person who fixed my boot loop went above and beyond the call of duty by doing it on his own time - outside of the system.

Web driven support at least acknowledged that they received the issue, and that they would relay it back to the engineering team. This was the WOL case mentioned here. Obviously no fix have been provided, but at least they seemed to listen. Lets see what happens.

I'm a european customer, so I have a local phone support line. But really .. this problem needs engineering to fix it - hopefully in the next release, so I wouldn't even bother with local phone support. I feel more certain that writing a ticket with exact description of problem would have a better chance of getting the message through. That said ... I don't hope I need phone support :-)

Sounds great with 3rd level support being that committed.

WOL does not work when I have LACP enabled on my ReadyNAS 3100 NICs. If I disable LACP on the switch (NETGEAR GS748Tv3), WOL will work but then I can't access my NAS until I re-enable LACP on the switch.

When I use just a single NIC, it works everytime.

RAIDiator x86 Firware: 4.2.15

trackless wrote:
WOL does not work when I have LACP enabled on my ReadyNAS 3100 NICs. If I disable LACP on the switch (NETGEAR GS748Tv3), WOL will work but then I can't access my NAS until I re-enable LACP on the switch. When I use just a single NIC, it works everytime. RAIDiator x86 Firware: 4.2.15

I have LACP enabled also.

Local WOL works flawless for me but the only way I can get WOL to work over the internet is to enable root SSH on the NAS. Is this normal? I have of course forwarded the necessary ports I am using for WOL to the NAS's LAN IP. I am testing this on a Pro-2 and Pro-6 with a ProSecure UTM25 router.

Edit: after further testing , it appears to be the same problem as listed in previous posts. The WAN WOL only works when powered down by the admin interface. When it is powered down via the power button, no WAN WOL only LAN WOL.

Hope this gets worked out quickly.

Sorry if this isn't very helpful but I spent some time on this myself --

I have CIsco E3000 router and wanted to get WOL working, simple enough. Set it on in my BIOS, on in the network adapter properties, read some tips online about the port and although it doesn't seem to matter I created a port foward in my router settings anyway -- to go to 192.168.0.127 --
Set my router subnet to 255.255.255.128 -- my router is set on 192.168.0.1 instead of 1.1 also... and then when i do a WOL client broadcast to 192.168.0.127 on port 5555 (i have a forward in the router to .0.127. on port 5555) that way you send the packet on subnet 255.255.255.255 to the correct MAC address and it will work

ANyway once I use the WOL client to send the magic packet -- it only works that way with the "Local internet" option selected , not "internet" externally.

Then I went into the E3000's settings under 'Security' and found an option checked "Filter anonymous internet requests" -- I disabled that option and once i did that -- then both local and external internet Wake on LAN was working for me....

Since then - I did not change anything but for some reason I can't get it to work over Internet again.

Cannot figure out why. It still works over Local internet when I am testgin from home on my network but over internet its not seeing it anymore - that Security setting is still the same and nothing else changed. Any help would be welcome

I've got an update to my WOL issues on the Ultra 4 Plus. If I disable the power-schedule, I am able to wake the NAS after both a soft-off (from the web admin interface) and turning it off on the button on the NAS.

If the powerschedule is set, it only wakes up after being turned off through the web admin interface.

Larswa wrote:
I've got an update to my WOL issues on the Ultra 4 Plus. If I disable the power-schedule, I am able to wake the NAS after both a soft-off (from the web admin interface) and turning it off on the button on the NAS. If the powerschedule is set, it only wakes up after being turned off through the web admin interface.

Just tried it with my Ultra-6: same results.

WOL works from a .BAT file/utility if the box has been turned off via the power switch - but only as long as power schedule is disabled.

Enable power schedule, and WOL does not work, and the box has tb turned on by pressing the Power switch or, I guess, one has to wait for the next scheduled Power On.

I wonder if that could be by design....

PeteCress wrote:

Larswa wrote: I've got an update to my WOL issues on the Ultra 4 Plus. If I disable the power-schedule, I am able to wake the NAS after both a soft-off (from the web admin interface) and turning it off on the button on the NAS. If the powerschedule is set, it only wakes up after being turned off through the web admin interface. Just tried it with my Ultra-6: same results. WOL works from a .BAT file/utility if the box has been turned off via the power switch - but only as long as power schedule is disabled. Enable power schedule, and WOL does not work, and the box has tb turned on by pressing the Power switch or, I guess, one has to wait for the next scheduled Power On. I wonder if that could be by design....

I confirm there is same problem on my Ultra 4.

If I disable schedule shut down WOL works correctly.

I have found a litte workaround if you want make a scheduled shutdown:

1. Enable root ssh
2. Fix crontab's editor bug setting EDITOR variable:

echo "export EDITOR=/bin/vi" >> .profile

3. Edit root contabs with:

crontab -e

4. Put your contab shutdown (press i), for example:

30 00 * * * /sbin/shutdown -h +3 'ReadyNAS scheduled shutdown.'

5. Write file and installing new crontab with:

:wq

Good luck.