NoMachine on Windows 11 and LAN – nxservice restart required to connect

Forum / NoMachine for Windows / NoMachine on Windows 11 and LAN – nxservice restart required to connect

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #42074
    elgreco
    Participant

    Hello there,

    Since installing Windows 11 on all my machines (2 desktops, 1 laptop), I am experiencing the following: previously I was able to connect from/to each machine without problems (on a LAN, I do not need to reach them over the Internet). After installing Windows 11 22H2 (build 963), this is not possible anymore as connections time out. The only solution is to restart the nxservice (NoMachine Device Service) on the remote machine (e.g. using RDP). Obviosuly I have checked my router as well as firewall clients on all machines and they are not the problem.

    As soon as the nxservice is restarted on the remote machine, I can connect to it remotely without any problem.

    On all three machines the server is set to autostart, but the service still needs to be restarted to make it work.

    Is there any solution to this? Perhaps restarting the service using task scheduler?

    Thanks!

    #42085
    elgreco
    Participant

    In case anyone is interested, I solved it by creating a scheduled task as follows:

    • Run with highest privileges using SYSTEM account
    • Trigger: at startup
    • Action: run command powershell -command “Restart-Service nxservice”

    Seems to have solved the problem.

    #42091
    Bilbotine
    Participant

    Hello elgreco,

    We are glad that you found a workaround.

    On our side, we will try to reproduce the problem and investigate it. We’ll get back to you if we have more questions or need logs.

    Thanks!

    #42093
    elgreco
    Participant

    Hello Bilbotine,

    Thank you, just let me know if you need further details or configuration details!

    #43531
    Britgirl
    Participant

    A quick update on this. We were never able to reproduce it.

    Maybe autostart was inadvertently disabled. Something to bear in mind is that in the Free Edition there are 3 services that need to be started, with Enterprise Desktop there are 4:

    /cygdrive/c/ProgramData/NoMachine/nxserver/nxserver.exe –startmode
    NX> 807 Service NoMachine status is: Automatic
    NX> 807 Service NXD status is: Automatic
    NX> 807 Service NXHTD status is: Automatic
    NX> 807 Service NXSSHD status is: Automatic

    This topic can be considered closed. If the issue comes back, please open a new topic.

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

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