Can’t see Ubuntu host in the NoMachine Player from MacOs

[Ek9max]

For the life of me, I can’t connect to my Ubuntu PC from my 2 other MacOS computers.

I can connect via Remote desktop, but it’s unstable and wont’ let me log back in without a reboot.

Neither of my MacOS computers can see the Ubuntu Machine (or each other) but it can see both MacOS machines.

Any help is appreciated!

[Bilbotine]

Hi Ek9max,

Based on what the info you gave us, it could be due to one of the following reasons – please check and let us know if the issue is resolved :

* Check Port 5353 (mDNS) on the Ubuntu Machine: Please verify whether port 5353 (mDNS) is blocked on the Ubuntu machine. If this port is blocked, it will prevent the machine from being visible in the NoMachine Player.

* Verify Software Functionality: To ensure the NoMachine software is functioning correctly, run the following command on the Ubuntu machine: /etc/NX/nxserver --status

* Manually Add the Ubuntu Machine: If the --status command confirms that all services are running, you can manually add the Ubuntu machine to the NoMachine Player on the macOS machine. To do this, use the “Add” button in the Player interface.

[Ek9max]

*Pretty sure that I was able to turn the entire firewall off.   I’m not sure if I entered the command correctly as I tried “sudo ufw status verbose”

Status: inactive

I ran “telnet 192.168.1.17 5353”

Trying 192.168.1.17…

telnet: Unable to connect to remote host: Connection refused

* ran /etc/NX/nxserver –status
NX> 111 New connections to NoMachine server are enabled.
NX> 161 Enabled service: nxserver.
NX> 161 Enabled service: nxnode.
NX> 161 Enabled service: nxd.

*I’ve tried to add manually.  “No route to the network or to the host ‘192.168.1.17’ was found. The issue could either be caused by a wrong server address or by a networking problem. Please verify your connection and try again.”

[fisherman]

On NoMachine port 5353 is the broadcasting port, so you can not check it the way you tried. NoMachine uses NX port 4000 by default, or SSH port 22 for any enterprise product.

Please try the following steps:

1. Check accessibility:
   Use Telnet to test if either port 4000 or port 22 is accessible on the server:
   192.168.1.17 4000
   or
   telnet 192.168.1.17 22
2. Verify network routes:
   Ensure that your client’s subnetwork can access the server’s subnetwork, or confirm that the correct routes are in place to enable connectivity between the client and server.

Let me know if you need further assistance.

[Author]

Posts