kroy

[kroy]

Can you check if port 4000 which is using by NoMachine is opened? You can open PowerShell on client machine, execute command

Test-NetConnection -Port 4000 -ComputerName <ip_of_nxserver> -InformationLevel Detailed

(replace <ip_of_nxserver> with IP which you trying connect) and paste output here.

Next thing is to check nx processes on server side. Please paste here output:

tasklist | findstr nx.

Can you also run debug and send logs? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098. Please send client and server side logs to forum[at]nomachine[dot]com.

[kroy]

…I can do nslookup and ping my linux from windows so ddns working but connection still fails with error 138 from windows side.

Are you connecting via NoMachine using your_domain_name as Hostname and 4000 as Port? You need to configure your router to forward a suitable port to your local IP port 4000. Then connect via NoMachine using your_domain_name as Hostname and a suitable port.

I don’t know why NoMachine is trying to use IPv6 and I cannot turn it off in the GUI.

At the moment there is no way to disable searching for IPv6 in the NoMachine, but you should be still able to use IPv4.

…since I have discovered another product that works…

Can you say what is the product? Did you forward port to using it? If yes – which port?

[kroy]

Yes. If that changing IP isn’t caused with problems on the router, modem or etc. – it’s a good idea to use Dynamic Domain Name System service.

[kroy]

We noticed from the logs that you are using your local network IP. Is that what you want or do you want to connect over the Internet?  Do you have problems connecting on a local network (same home network or LAN at work)?

If you want connect over internet you need to connect with your external IP. Here you can find basic information about using NoMachine https://www.nomachine.com/getting-started-with-nomachine. Please check out section: “Using NoMachine for remote access to a computer over the internet”.

[kroy]

Are you able to verify from which side problem comes? If you try to connect from other device to the server – audio works? And if you connect from tablet to other server you can hear sound?

I haven’t upgraded to 5.2.11 because I don’t want to break my (mostly) working setup.

Did you mean NoMachine setup? During update configuration files are saved so you will keep your settings.

[kroy]

We couldn’t reproduce such problem. Can you write which NoMachine versions do you use on both sides? Please write also what is the device and Android version.

[kroy]

Thanks for the report. We will look at it closer. Meanwhile you can uncomment and change the value in following key in the server.cfg file: DisplayBase 1003 (it mustn’t be 1003 but it needs to be bigger than  your greater display) or just create desktop with smaller display number to :1000.

Also, if I do end up using this option and specify DisplayDefault :1002 , does it mean that my client can only connect to display 1002 and won’t be able to switch?

Yes, exactly.

Ideally I would like to have a connection file specifically for display 0 and one for display 1002.

Unfortunately, it’s not possible to save the session file to autoconnect to a specify physical session. You will still be able to choose between those two displays though.

[kroy]

It’s a known issue but isn’t dependent on NoMachine. There is link with bug report and workaround https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1574886.

Add new symlink from your library video card drivers to libGLX_indirect.so.0. For example:

ln -s /usr/lib64/libGLX_mesa.so.0 /usr/lib64/libGLX_indirect.so.0

[kroy]

Are you logged to the desktop on that machine? If yes – please check if username logged on system is identical as username which is connecting via NoMachine. You can disable authorization on that host to connect without asking. To do it – edit nxserver configuration file on that machine (for example sudo vim /usr/NX/etc/server.cfg) and change line:

#PhysicalDesktopAuthorization 1

to:

PhysicalDesktopAuthorization 0

If you aren’t logged to the desktop – please show the output of command ps -ef on that machine. Please also run debug, restart nxserver (sudo /usr/NX/bin/nxserver --restart) reproduce problem, collect logs and send them to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.

[kroy]

If you forwarded port correctly it should work if you connect to External IP of that ‘mobile hot spot’ and Port 23648 in your case. This should forward it to port 4000 of you local nxserver machine.

Can you write more details about your mobile hot spot? What is the device? Is tethering enabled there? Is it possible to enble UPnP?

[kroy]

Yes, command prompt. Navigate to nxserver script – it’s in NoMachine\bin directory. In default on Windows 64-bit NoMachine is installing in Program Files (x86). So you can execute command: "c:\Program Files (x86)\NoMachine\bin\nxserver" --upnpstatus.

[kroy]

Thanks for the report. It’s a known issue and we are working on a fix. Meanwhile you can check port by using ./nxserver --upnpstatus command on console.

[kroy]

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?

[kroy]

If you use native firewall you don’t need to add new rules to allow NoMachine connections.

Are you sure that you tried to connect to external IP and correct Port which is listed on “welcome window” NoMachine player on Ubuntu? There is an article with instructions on how to connect to NoMachine when the server is behind a NAT router or a firewall https://www.nomachine.com/AR11L00827.

[kroy]

Hi.

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.

[Author]

Posts