Community
Wake On LAN
Links used in this discussion
- https://www.remoteutilities.com/support/docs/wake-on-lan/
- https://www.remoteutilities.com/support/forums/messages/forum1/message3538/758-is-it-possilbe-to-start-a-host-over-the-internet-with-wol-from-a-full-shutdown#message3538
- https://www.remoteutilities.com/support/docs/updating-remote-utilities/#Update_Hosts
- https://www.remoteutilities.com/support/docs/updating-remote-utilities/
- https://www.remoteutilities.com/support/docs/host-log/
- https://www.remoteutilities.com/support/docs/manual-import-export/#Exporting_address_book_
- https://www.remoteutilities.com/download/
In this case, could you please provide us the Host log file for examination? You can send it to support@remoteutilities.com.
In addition, please let us know what OS is running on both sides of the connection.
Looking forward to your reply.
It simply doesn't work at all.
I can see and controll all Computers on my network, i don't have Subnets or someting, it's my home.
But Wake on LAN doesn't work at all, at least on my installation it NEVER worked for me.
I tried at work, too, with completely fresh installations of Windows with only the drivers.
No chance to get WoL working.
I use WOL2 for waking up my computers, it works since beta status of that software.
I use the Wake-Option in my fritzbox, it works, too.
So I can say, it has nothing at all to do with misconfiguration or something else.
So I think, it's simply a bug inside the software, because there is nothing to configure inside Remote Utilities.
Is there a plan, when this will get fixed?
It's not dealbreaking, because there are other tools or my fritzbox, that are working, but it would be nice,
if this function would be useful, so I could use really an "all in one" solution.
Regards
David
I have nothing green or energy saving activated in BIOS. And that wouldn't explain, why it works with all other tools.Patrick Riley wrote:
I was able to get it working. A lot of setting changes in the bios and on the network adapter. Do you have energy efficient or green ethernet disabled?
If it were a BIOS misconfiguration, it wouldn't work with other tools at all.
I have activated the option, that the Computer will only be woke up by "Magic Packet" and not by "Pattern match",
because in that case my Computer would start with a simple PING, and that wouldn't be so nice.
What kind of changes have you done?
Si, Pancho. :-)Patrick Riley wrote:
Are you running Windows 10?
All Systems are running Windows 10 x64, with all updates, only the Windows Defender, no Security Suite or other shit and only the drivers without any bundled Software.
My Autostart is clean and I don't use any optimizer tools, I hate them.
Only for couriousity:
I tried with Windows 7 and XP, too.
I would try with Windows 2000, but the Software doesn't work on it. :-)
Then, go back to control panel and go to Power Options. On the left, click on choose what the power buttons do. Click on Change settings that are currently unavailable at the top. Then disable turn on fast startup.
WOL in the BIOS also needs to be enabled but BIOS settings are different depending on the manufacturer. I also disable other sleep settings in the BIOS. But I know these settings in Windows 10 need to be set right for WOL to work with remote utilities. Let me know if you have any questions.
Like I said, it is all configured like that.Patrick Riley wrote:
Ok, check these settings on your windows 10 machines. Control Panel->Network and Sharing Center->Change Adapter Settings. Right click on ethernet adapter and go to Properties. Click Configure, then Advanced. Make sure green ethernet or energy efficient ethernet is disabled. Sometimes it has both. Then make sure all your wake on lan settings are enabled. Wake on magic packet needs to be enabled. Disable shutdown wake on lan if it is listed, but you may need to do trial and error with this setting.
Then, go back to control panel and go to Power Options. On the left, click on choose what the power buttons do. Click on Change settings that are currently unavailable at the top. Then disable turn on fast startup.
WOL in the BIOS also needs to be enabled but BIOS settings are different depending on the manufacturer. I also disable other sleep settings in the BIOS. But I know these settings in Windows 10 need to be set right for WOL to work with remote utilities. Let me know if you have any questions.
Deep sleep, green LAN, and all the other energy saving shit, all disabled.
Sorry, it only won't work with RU. All other wake tools are working flawlessly.
And it doesn't matter, what I configure in Windows, because when the Computer ist shut down, then there is of course no Windows loaded.
At this time only the BIOS is important and there I have configured all properly, because all other tools can wake that machine, even if I delete the Harddisk.
OK, it won't boot anything but at least it would start the machine.
Of course Magic Packet is activated. I even have Intel AMT activated on one machine (my server).
My post was only for couriousity, it isn't important for me to have this issue fixed.
I'm satisfacted with RU, for WoL I use Box2go on Android and WOL2 on Windows. It's OK for me.
If someone would have fixed that issue reliably, then it would be nice,
or the developer could implement another waking method like all other tools in market.
But again, if it isn't fixable yet, then it's OK for me, too.
I'm running out of options now because all settings mentioned by you were set correctly.
Only for example:
I have the Host installed on machine A and B.
I have the Server installed only on machine A.
Machine A is running 24/7.
Machine B is shut down.
Now I want to wake machine B:
If I use WOL2 on machine A: OK, machine B starts up.
If I use Box2go on my Phone via Fritzbox: OK, machine B starts up.
If I use RU Viewer on Machine A or on any other machine: no way. Machine B remains sleeping.
Yes, the lights are on. Sporadically they blink.Patrick Riley wrote:
Are the link lights on for the ethernet adapter when the computer is shut down?
My Router recognize my Computer as RUNNING, even if I shut it down because the LAN port never shut off.
* Website time zone: America/New_York (UTC -5)