NoMachine cannot be connected

Forums / NoMachine for Linux / NoMachine cannot be connected

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #40216
    zhouych
    Participant

    Installation log:

    nomachine_8.0.168_2_# dpkg -i nomachine_8.0.168_2_amd64.deb

    (Reading database … 491800 files and directories currently installed.)

    Preparing to unpack nomachine_8.0.168_2_amd64.deb …

    Unpacking nomachine (8.0.168-2) over (8.0.168-2) …

    Setting up nomachine (8.0.168-2) …

    NX> 700 Starting install at: Tue Sep 20 17:04:53 2022.

    NX> 700 Installing: nxrunner version: 8.0.168.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Compiling the USB module.

    NX> 700 Installing: nxplayer version: 8.0.168.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 To connect the remote printer to the local desktop,

    NX> 700 the user account must be a member of the CUPS System Group: lpadmin.

    NX> 700 Installing: nxnode version: 8.0.168.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Creating configuration in: /usr/NX/etc/node.cfg.

    NX> 700 Installing: nxserver version: 8.0.168.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Creating configuration in: /usr/NX/etc/server.cfg.

    NX> 700 Install completed at: Tue Sep 20 17:05:09 2022.

    NX> 700 NoMachine was configured to run the following services:

    NX> 700 NX service on port: 4000

    /nomachine_8.0.168_2_#

     

    Everything seems good during the installation.

    The IP of the  Ubuntu server is 192.169.1.103.

    I tried connect from a Windows with IP of 192.168.1.109. Failed.

    “A connection timeout has occurred while trying to connect to ‘192.168.1.103’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.”

    I then tried to connect from itself, get the same message.

    I have tried on the windows system. It can connect from itself.

    When using the SSH protocol, I get:

    “Running NoMachine sessions over a SSH connection is not supported on this server. Do you want to switch your connection to using the NX protocol?”

    After a long time, it gives the previous message.

    I wondering that the 4000 port on the system is not open, I

    #grep -w ‘4000/tcp’ /etc/services

    gives nothing.

    #lsof -i -P -n | grep 4000

    nxd       11543              nx    3u  IPv4  64902      0t0  TCP *:4000 (LISTEN)

    nxd       11543              nx    4u  IPv4  63023      0t0  UDP *:4000

    nxd       11543              nx    5u  IPv6  65912      0t0  UDP *:4000

    nxd       11543              nx    6u  IPv6  63024      0t0  TCP *:4000 (LISTEN)

     

    Is there any body can help me to solve the issue? Many thanks!

    #40245
    Britgirl
    Keymaster

    Hi,

    just to clarify that this message “Running NoMachine sessions over a SSH connection is not supported on this server. Do you want to switch your connection to using the NX protocol?” occurs when you are trying to connect to the desktop where you have installed the NoMachine Free Edition via an SSH session, when the free edition does not support SSH.

    If I understand correctly, you can connect to the localhost on your Windows machine. This means everything is working. But you cannot connect to the localhost on your Ubuntu machine. The IP address would appear to be not correct. Can you try by just inserting the term “localhost” in the hostname field of the connection configuration?

    A connection timeout has occurred while trying to connect to ‘192.168.1.103’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.

    This message generally appears when you are trying to connect from the internet and your computer is behind a NAT or if the firewall is blocking the connection in, but it’s strange that your firewall would be blocking connections from the same machine. The logs of the server machine would be useful. Please follow the instructions here and send them to forum[at]nomachine[dot]com, https://kb.nomachine.com/DT11R00182, making sure to use the title of this topic as the subject of your email. Thanks!

    #40270
    zhouych
    Participant

    If I understand correctly, you can connect to the localhost on your Windows machine. This means everything is working.

    Yes, server is Windows, the client is also the Windows. It means server on Windows is good.

    But you cannot connect to the localhost on your Ubuntu machine.

    No, the server is Linux, the client is Linux too. It also cannot connected by Windows client. Which means the server on Linux is not working.

    I have figured it out. It was the firewall. After run cmd “ufw allow 4000”, everything goes well. Thanks.

    #40275
    Britgirl
    Keymaster

    I’m glad you can now connect. Thanks for letting us know 🙂

    #40298
    toddkrein
    Participant

    I’m running into a very similar problem. I have NoMachine installed on a Win10 box and two Ubuntu boxes. All three can get to the desktop on the Windows machine, and the first Ubuntu box. Only the second can get to the second Ubuntu box, via its network IP address (192.168.200.120). “lsof” shows the same four entries as above.

    I’ve tried the “ufw allow 4000”, as well as manually flushing the iptables, and even disabling the firewall and rebooting. Nothing works. I’ve even tried uninstalling it and re-installing it. The weirdest thing is that it worked once when I first installed it, but never again.

    Suggestions?

    #40309
    Britgirl
    Keymaster

    I’m not sure what is working and what is not 🙂

    So you are on a LAN, correct?

    You have version 8 installed on everything, yes? Before updating to version 8, everything was working out-of-the-box?

    Windows to Ubuntu1 connects ok?
    Ubuntu1 to Windows connects ok?
    Ubuntu1 to Ubuntu2 connects ok?
    Ubuntu2 can connect to itself ok (local host)?
    Can Ubuntu2 connect to either Windows or Ubuntu1?

    What error messages are you seeing when you are trying to connect?

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

You must be logged in to reply to this topic.