Shorten timeout before WOL?

Forum / NoMachine for Windows / Shorten timeout before WOL?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #47150

    It is possible to adjust the delay before a client tries Wake On Lan if the server is not responding to a connection request?

    The default delay is uncomfortably long.  My client & server are on a fast local LAN, and the server responds in a fraction of a second if it is awake.  I would like to have the WoL packet be sent after a 2 or 3 second delay.


    P.S. Using NoMachine 8.11.3 on both client (Windows 11) and server (Linux)


    The most reasonable implementation would be to send a WOL packet just before the connection attempt, so that if the server is not running, it would restart its run, or send the WOL packet if the server is not immediately responding in a reasonable time, like a couple of seconds. The WOL packet, instead, is now sent after the connection timeout, if the remote host is not responding. The reason it was done like this was to overcome a few WOL problems and incompatibilities we encountered at the time of the first implementation. We actually retested all of this and it doesn’t seem that these problems and incompatibilities still hold. This means that a more reasonable implementation should come shortly, actually resolving the problem you detected. Thanks for reporting.

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.