NoMachine 5.2.11 on Linux – Connection timed out error 110

Forum / NoMachine for Linux / NoMachine 5.2.11 on Linux – Connection timed out error 110

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #13734


    I have installed NoMachine v. 5.2.11 free version on 2 machines, both running Kubuntu 16.04.1 LTS, 64 bit: a laptop and a desktop. They both run KDE Plasma 5.8.5.

    I can connect from the laptop to the desktop.

    When I try to connect from the desktop to the laptop, I get a white screen for a few seconds, then “The connection the server was lost. Error is 110: Connection timed out”. It appears that authentication succeeds (I get a different error if I enter incorrect credentials) but something else must be failing after that.

    I have tried disabling the firewall on the laptop but it didn’t help.

    This may be a red herring but one thing I noticed is that the NoMachine (!M) icon on the desktop’s KDE system tray has a red background, while the one on the laptop is grey.

    These are the related processes on the laptop (host):

    root 1625 17.2 0.6 265880 102948 tty7 Ss+ Feb08 233:52 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{0b1cf65d-b224-427e-ac80-b05c4a349093} -background none -noreset -displayfd
    18 vt7
    nx 6401 0.2 0.4 636376 76540 ? Ssl 16:58 0:04 /usr/NX/bin/nxserver.bin –daemon
    ciprian 6450 0.0 0.0 32552 4084 ? S< 16:58 0:00 /usr/NX/bin/nxexec –node –user ciprian –priority realtime –mode 0 –pid 11
    nx 6451 0.0 0.0 483732 8100 ? Sl 16:58 0:00 /usr/NX/bin/nxd
    ciprian 6472 8.5 0.7 1774364 129732 ? SX/bin/nxnode.bin
    ciprian 6505 0.0 0.2 1334556 35464 ? Sl 16:58 0:00 /usr/NX/bin/nxclient.bin –monitor –pid 4035
    nx 6640 0.0 0.4 883812 75276 ? Sl 16:59 0:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    ciprian 6653 0.0 0.0 32552 3964 ? S< 16:59 0:00 /usr/NX/bin/nxexec –node –user ciprian –priority realtime –mode 0 –pid 13 -H 5
    ciprian 6664 0.0 0.4 1347872 75880 ? SX/bin/nxnode.bin -H 5
    ciprian 6724 0.0 0.0 21776 2664 ? S< 16:59 0:00 /usr/NX/bin/nxcodec.bin

    Any idea what could be wrong?

    I have enabled debug logging on the laptop (host) and attached it along with the client logs. Please note that the nxserver.log was too large so I removed the first part of the log before restarting the server and reproducing the problem.

    Thanks for your help. Please let me know if you need anything else.


    Hello linuxuser,
    thank you for logs, based on them we could said that there is internal
    problem with network stack or configuration. Internal local connection to localhost
    is refused because it is wrongly recognized as a remote one.

    Could you show us results of the following commands:

    cat /etc/hosts
    ping -c localhost

    About NoMachine icon color, differences are just cosmetic and depend on themes and operating systems.Can you confirm you’re using different themes on notebook and on desktop?


    Hi brotech,

    Thanks very much for your prompt response.

    I have attached the output of the commands you requested – I assume you meant on the laptop, i.e. the problematic nxserver host.

    Regarding the desktop theme: most settings are identical between the desktop and the laptop (the theme is set to “Breeze” on both machines under System settings -> Workspace Theme -> Look and feel and Desktop Theme; same for Qt widget style under System settings -> Application style -> Widget style). The only thing that differed was the GTK2 and GTK3 themes – I changed them both to Breeze but it didn’t seem to make a difference. So it’s a strange one but if it’s just cosmetic then it’s ok, there must be a different setting I missed.




    We couldn’t reproduce such problem. Can you send also kernel information from the machine where issue shows? Just execute uname -a command and paste output here.



    This is the output:

    Linux ciprian-laptop 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux



    We weren’t able to reproduce issue on the same Kubuntu version. It looks that is internal network problem. Issue still shows after system reboot?

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.