13.5.4.0 Events -> Wake on LAN

Hello,

I will have a discussion with our engineering team about it.

Thank you for reporting this!


Best regards,

Hello,

After discussing this with our engineers, could you please try increasing the retry count to maybe 10-15 to see if it helps?


Best regards,

Hi Mark,

if i set the retry count to 30 it is a little bit better but also not succesfull.. now the error message appears after about 60sec. The wait timeout is still configured to 120 sec.

I also found out that the WOL doesnt work if you set it on a Web Browser entry, on a SSH entry the wol command are executed. (Looks like the same as this post)

Regards,
Min

Hello,

For the timeout, we will see what we can do.

For the web browser part, I'm not sure I understand. The link you shared was from an issue you reported and that it was fixed in an update.

Are you saying that since 13.5.4.0, it has stopped working?


Best regards,

Hi,

I understand the two setting as follow: the session will wait maximum 120 sec and in this time the retry count will be executed. So 120 / 3 = every 40 seconds will be a WOL paket send.. Is this correct?

As for the Web Browser session - it looks like this . I can't longer wake up the server via the WOL command on the respective session - Also the Events => before connect feature doesnt wake up the server.
If I try it on a SSH session in both case the server wake up..

Indeed very strange.. :(

Thanks for your support!

Regards,
Min

Hello Min,

Let me explain the settings.
When you set the mode to Wake on LAN it begins by sending a WoL packet to the host. Then, RDM tries to scan for the port set up in the entry to see if it's available. This is where it uses the two settings. The port scan will retry X amount of times (the retry count), and when trying we set its timeout to the wait timeout value. I think the reason why you aren't getting the expected results is because the connection doesn't "timeout", it fails because the machine is just not available.
I think what we can do is introduce another setting for a wait time between port scans. This would mean if you set it to 5 seconds, it would retry only after 5 seconds have elapsed. I think with that it would work for your case, if you'd set something like 12 retries with 10 seconds wait inbetween each.

For the web browser issue I'll let Marc diagnose what's going on.

Regards,

Hello,

Just to be sure I understand the issue, could you please create a recording if you can of this issue so we can have a closer look?


Best regards,

Hello Hubert,
Hello Mark,

thanks for the explanation! Looks like I'm the only one that have troubles with this settings. Maybe my devices boots just too slow :\: :)
If you could improve the time between it would be perfect! One of my devices needs 90-120 sec (from cold boot) to respond..

Mark,
sure I can record it, but you will see only that i open the session, the modal window with the message trying to reach host on port xx and after 30-60sec the error message that the host is not available.
I tried it hust again - if i execute it on a SSH session the device wake up, on a Web Browser session the WOL command doesnt work and the device didnt wake up.

Thanks for the support!

Regards,
Min

Hello,

In the Information tab of your Web Session, have you provided the MAC address of the system?


In case you need additional information, we have this article on the Wake-On-LAN feature;
https://help.remotedesktopmanager.com/dashboard_macroscriptstools_wol.htm



Best regards,

Hi,

yes the mentioned fields are filled out - on the SSH and on the Web Browser session.
I also tried to add to the (working) SSH session a web browser sub connection and use here the variable $PARENT_MAC$ but open the sub connection unfortunately doesnt wake up the device.
Thanks, but I know this link already ;)

If you would, I can send you my sessions in private.

Regards,
Min

Hello,

If you can, please send me your session structure so I can have a look. I did not test with a variable. Maybe this will give a different result ;)


Best regards,

Hello,

I've done several tests with the entries you sent and unfortunately, I'm unable to recreate your issue.

Is there another system where you could try the WOL feature to see if you have the same issue?

Have you also tried to use it without variables & sub connections?


Best regards,

Hi Mark,

thank you very much for your investigation on your side. After some more tests it looks like the issue is related to port 8080 - so I will verify the local network and keep you up to date if I have some news.

Regards,
Min

Hi Mark,

after some tests the "issue" must be related to the windows application. I tried the same web browser session on iOS and Android - in both scenarios the WOL feature works. If I try it with the windows application it doest work.

I think it must be in connection with the windows application and port 8080 respectively port 8080 in a web browser session.

Are you still unable to reproduce the issue?

Thanks!

Regards,
Min

Hello,

Thank you for your reply.

I will assign this to our QA Team for further investigation.


Best regards,

Hello Min,

I'm using the before connect WOL like previously shown in this post on a Internet Explorer entry. The WOL is triggered properly as after that, I can connect through SSH on the same machine that was "sleeping".

Even with a bad port/website name, the "before connect feature" for the WOL is sure to send the packet to the machine to wake it up from what I've tested.

I'm not quite sure how to reproduce your issue, could you send me an export of the session you're using to wake the machine?

Regards,