Tom

[Tom]

Hi Gorkmc,

We will need the NoMachine installation logs. You can find the installation logs in the directory C:\ProgramData\NoMachine\var\log
The file name is  nxinstall.log. Please send via attachment on the forum.

Regards,
Tom

[Tom]

Hi Teknicianexpertiz,
run on NoMachine Server command in the console: traceroute whatismyip.com and paste its results on forum.

Remove the last two numbers from all IP addresses e.g. 80.92.83.99 replace with 80.92.x.x

Addresses you don’t have to change
192.168.x.x
10.x.x.x
172.16.x.x – 172.31.x.x

these are private addresses, they do not identify your network.

If you paste something that will not be safe, the moderator will remove it before approving the post.

Regards,
Tom

[Tom]

Hi Gorkmc,

you must first check if the NoMachine server is working properly on computer A (Notebook). You should see the NoMachine icon in the windows tray.

When you move the cursor over it and press the left mouse button, a menu will appear, select “show server status” from it. In the window that will appear you should see a green dot and the words “server running”. This means that the problem is not the NoMachine server not working. What do you see? Can you submit a screenshot of Server status?

Regards,
Tom

[Tom]

Hi Steveatsws,
I tested the “ListenAddress” key on Ubuntu 18.04 and NoMachine 8.4.2. It works as it should.
My Ubuntu has two interfaces which have IP 10.0.136.88 and 10.0.112.202. I can connect to both via NoMachine.

When I set the key in the server.cfg file:

NXdListenAddress "10.0.136.88"

I saved it and restarted the Nomachine server:

sudo /usr/NX/bin/nxserver --restart

I cannot connect to the address 10.0.112.202

Maybe you didn’t restart Nomachine after changing server.cfg?

Regards,
Tom

[Tom]

Hi Manchys,
Just to be sure, I set up NoMachine on a VM with Ubuntu 18.04 and two NICs. I had no problems like you.

Please prepare NoMachine logs according to the article: https://kb.nomachine.com/DT11R00181

At the beginning, we will only need logs from the server.

Start with the situation where you are connected to the NoMachine server via WiFi, disconnect the NoMachine client, connect the ethernet cable, wait two minutes, and try connecting via WiFi again.

Regards,
Tom

[Tom]

Hi Steveatsws,

I installed NoMachine Free
 on my Jetson Ubuntu 20.04.
I have Nvidia Jetson Nano – ARM Cortex A57 4x 1,43 GHz, Nvidia Maxwell
Because it has one built-in card, I installed the second LAN via USB.

I did a test, connected both cards to ethernet cables. I connected from the NoMachine client to the server, first to the IP address of the first card, I disconnected NoMachine client,  then I connected to the IP of the second card. Everything worked.
I disconnected the network cables in the second card and connected to the IP of the first card. Everything was still working.

I don’t know what could be causing your problems. Perhaps the NoMachine logs will help.
Please read the article: https://kb.nomachine.com/DT11R00181

Collect logs and upload them.

P.S. I saw you opened another thread on the forum, maybe we can move the Jetson discussion there?

Regards,
Tom

[Tom]

Teknicianexpertiz
If you can, try to connect to the NoMachine server from your local network, this will allow us to eliminate the problem on the NoMachine server side.

You need to know your public IP to be able to connect to it. The solution to the dynamic IP address problem can be to use services like noip.com.

You can check your public  IP at whatismyip.com. Check it from the computer you want to connect to (NoMachine server).
 Try connecting from outside via NoMachine to the IP you saw on whatismyip.com and port 24080 if that port hasn’t changed.

There may be several reasons for the external IP not showing up in NoMachine.

Run on NoMachine Server command in the console: traceroute whatismyip.com. If the command is not installed, you can do it with the following command: sudo apt install traceroute. With this command you will be able to check if you are behind a double NAT. 

If the first two hops give local addresses, e.g. 192.168.x.x 10.x.x.x 172.16.x.x -172.31.x.x, it means that your computer you want to connect to is behind double NAT.

Regards,
Tom

[Tom]

Hi Manchys,
when computer has two interfaces connected, each of them has a different IP address.
I just connect to the IP of the WiFi interface.

You can display the addresses with the command “ip a” in the console but you wrote that WiFi has IP 192.168.1.20 (I don’t know if it’s an example). Enter this IP in the NoMachine Client.

Below you can see the manual on how to add a connection in NoMachine.
https://www.nomachine.com/getting-started-with-nomachine

Regards,
Tom

[Tom]

Manchrys,
I did an experiment in my lab. I checked the possibility of connecting to my laptop with Ubuntu 22.04 and NoMachine free 8.4.2.
Regardless of whether the network cable is connected, I can connect to it via NoMachine via the WiFi interface.

What version of NoMachine are you using?
You can run the netstat -lntu | command grep 4000 and paste its result?

You can try using the options in server.cfg
# Specify the network interface where the NX service will be bound.
# Populate the field with an IP address or a domain name.
#
# NXdListenAddress “”
This option will force nxd listening on a specific IP address.
But if the IP address is assigned dynamically and changes from time to time, it will require changes in the cfg file.

Regards,
Tom

[Tom]

Hi Manchris,
I will summarize what I know about your problem. If I have misunderstood, let me know.

You have two devices: a tablet (NoMachine client) and a computer (NoMachine server).
When both devices are connected to WiFi, the connection from the NoMachine client to the NoMachine server works fine.
When you connect a cable to the network card in the computer, you cannot connect from the tablet to the computer.Or do you want to connect via WiFi because lidar transmits data via ethernet cable.

Which of these statements above is true?

What does “if I gave the PC’s host” mean. are you specifying the hostname e.g. UbuntuTom?
Are you specifying the NoMachine Server’s WiFi IP in the NoMachine client?
What type of connection is IP with X at the end and which with Y at the end?

NoMachine uses interface priorities set in your system, it will not set them itself.

Regards,
Tom

[Tom]

Fabs74,

please check if you have open port 4000 for TCP and UDP protocols in Virtual Cloud Network Details – Security Lists.
You can also test if the port is actually working by setting ssh to this port and connect ssh to port 4000 from client machine.

Perhaps after the upgrade you don’t have the port added in iptables, you can add it by running the command:
iptables -I INPUT 6 -m state –state NEW -p tcp –dport 4000 -j ACCEPT.

Regards,
Tom

[Tom]

Hi Fabs74,

are you connecting to one of the addresses show in the screenshot?
The addresses I see there are private.
Kubuntu (NoMachine client) is also on Oracle Cloud?

Regards,
Tom

[Tom]

Hi Fabs74,
please answer to a few questions that will help us to get rid of some doubts.
How did you do the NoMachine update procedure ? Was it with automatic updates or manual?
Did you have any NoMachine custom settings set for version 7?
When you write “delete everything and installed in as a fresh install” did you delete the entire /usr/NX/ directory?
Did you change anything in Ubuntu settings on Oracle Cloud after NoMachine update?
What is the output after executing the command: sudo /usr/NX/bin/nxserver –status?
What program do you mean by RDP?
Regards,
Tom

[Tom]

I set up a proxy in my laboratory with a user and password, it works without a problem.

Did you try what I wrote last time?

Please configure nxplayer according to https://kb.nomachine.com/AR05S01130
It will allow us to eliminate unnecessary settings that may be the cause of the error.
Can you connect via proxy to ARM64 with the player configured in this way?

Reagards,
Tom

[Tom]

Hi bk1412,
is your proxy Squid, if not what is it?
Does the proxy accept connections on port 8080?
Squid has a default port of 3128.

Please configure nxplayer according to https://kb.nomachine.com/AR05S01130
It will allow us to eliminate unnecessary settings that may be the cause of the error.
Can you connect via proxy to ARM64 with the player configured in this way?

Regards,
Tom

[Author]

Posts