Problem with WakeOnLan
Hello,
I want to wake a PC at night for a backup.
Due to the fact, that the PC and the Server hosting the Acronis Management Console are in different LAN-Subnets, I installed a Acronis WOL Proxy at a Server located in the same subnet as the PC. After it I registered the Server as WOL Proxy in the Server-Management options with correct login data.
While creating a backup plan I aktivated the Wake-On-Lan checkbox, a click on the hyperlink (for configurating a proxy) below the checkbox showes only a blank window with a ok and cancle button but acronis accept just clicking ok.
When reaching the starting time for the backup, the PC doesn't wake up. The WOL configuration of the PC is still ok and I can wake it with some other software. If I do this the backup starts, but I don't want to come at night to work and start the program...
Does anyone have a idea how to fix it?
Thanks
Hello,
I used WhireShark to check it the WOL packet is send from the server to the PC as you said, but I can't find something, that looks like a acronis magic packet. Can you tell me how it is called in WhireShark?
I tested to wake a host in the same subnet as the acronis server, but it failed too.
If you have an idea, how I make it work, that would be great.
Thanks
I'd expect it to look like described in http://wiki.wireshark.org/WakeOnLAN
Yes, that's a "normal" magic packet.
I'm able to generate a test magic packet with some other software and display it in WireShark, using (ip.src == "AcronisServerIP")&&(ip.dst == 255.255.255.255) as filter, where "AcronisServerIP" is the ip of our server hosting the acronis management console. But I can't display any magic packets send from acronis.
Where Wireshark was running? Did you install in on 'PC' (which you want to wake) or on the Management Server? I'd check that WOL packet is captured on the Management Server itself. I checked it in the virtual environment and was able to see it on both ends.
Btw, are both computers in the same time zone? (it doesn't matter now that the WOL is not working at all, but if it works, backup on the PC may be scheduled at the different time than WOL packet is sent)
Yeah, we are now in 2014 and this "bug" still has NOT been fixed.
I also need WOL Proxy working with my purchased copy of Acronis Backup 11.5, because I configure the Management Server Options to include the Management Server and another server located in another subnet to wake up machines in another work area.
As the user above describes, when you click on WOL Proxy within the actual job definition you get a BLANK SCREEN with just OK and CANCEL, but in the options within the console you can add WOL Proxy Servers, but there is NO TEST BUTTON, NO CONFIRMATION POPUP, NOTHING to indicate that this has been added correctly and working. Acronis needs to FIX this option to prompt the user that the WOL Proxy is actually connected and working, because there is NO OPTION anywhere in the console to show that the remote installation is even communicating with the Management Server.
Finally, both machines are in the SAME building, but different subnets and the machine is NOT being awoken, so this needs to be fixed ASAP and I am surprised more people have not complained.
Is it only WOL proxy not working, or Wake-on-lan itself too? There is a bug that WOL doesn't work in Tower of Hanoi scheme (will be fixed in the nearest update). Did you open a support case about this problem?
The problem is that the Acronis interface does NOT have any means to let you know if the WOL Proxy is actually connected or working properly. You basically just add entries and click OK, but you get no confirmation as to whether or not it is actually communicating or working.
WOL is just WOL and I can send it from any other machine within the subnet, but Acronis itself should be CONFIRMING that the WOL Proxy is communicating with the Management Server, so your interface needs to be updated to correct for this.
Aside from that, when you click on the WOL Proxy highlighted text in the Job Definition you get a BLANK, EMPTY, WHITE screen with NO OPTIONS, NO SERVERS even though you entered them in the Console Options, so this is also BAD and a "bug".
So you have TWO problems right there with the interface and now you tell me that WOL has a problem with Hanoi, which JUST HAPPENS to be what I am using for my backup scheme so that means you have THREE problems to fix now.
I guess I should file a ticket then... >:(
WOL proxy settings empty window (When opened from scheduling settings dialog) will be fixed in the next update too (it just opens AMS settings window and these settings are the same for all plans). Currently there are no plans to improve WOL proxy connectivity diagnostics which you reported as the first problem.