Forum Replies Created
-
Posts
-
We strongly recommend you update to 5.1.24 and check whether the problem disappears. We haven’t been able to reproduce it on the 5.1.22.
If you still encounter the problem with the latest version, please check that you haven’t disabled “Start automatic services at startup” in nxclient monitor (click on nxclient tray icon, choose “Show the server status”, and then – “Server preferences” – it should say “Running” status)?
If you see that it is enabled already, it is possible that the node is crashing. In that case, we need to investigate. Can you check whether you have nxtrace.log in log directory? If you do, please run debug (check article linked below), restart nxserver and try to reproduce the problem. If you were able to repeat issue, please send all logs from server side to forum[at]nomachine[dot]com or attach them here (size is restricted). Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.
To execute Ctrl+Alt+Delete keys combination, you have to run the nxplayer Menu (Ctrl+Alt+0, or just click on page-peel) and click on the “Special sequences” button (located in the bottom-right corner) and choose “Ctrl+Alt+Delete”, like on the attached screenshot.
Attachments:
We need more information.
It works for a little bit and then the NX service will stop.
It happens in every system’s reboot? NX service – you mean NXservices or nxserver?
If I try to — restart the server, it gives an error that the file isn’t found, even though “ls” shows it.
You have tried restart from GUI or via terminal? Can you do screenshot of the error and attach it here?
Please enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart), reproduce the problem and send all logs from server and client side to forum[at]nomachine[dot]com or attach them here (size is restricted). Instructions about collecting logs you can find there: https://www.nomachine.com/DT04M00076We still cannot locate the reason why you not able to connect to the session. Please try to add line: NXWmRunningTimeout 100000 on the end of server configuration file (/usr/NX/etc/server.cfg).Then restart nxserver (sudo /usr/NX/bin/nxserver –restart).Once again execute:/bin/netstat -ln –protocol=unix > netstat_output.txt
/bin/ps awwxo uid,ppid,pid,sid,comm,args > ps_output.txtAfter that collect logs from server side and sen them and netstat_output.txt, ps_output.txt to forum[at]nomachine[dot]com or attach them here.Please try port forwarding. Configure your router manually to pass traffic to port 4000 (NX protocol). 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. Read part “IMPORTANT”, there is instruction: “if the router doesn’t accept UPnP or NAT-PMP commands, it will be necessary to configure it manually through its administrative interface.”
Can you also write here information about router? Name, version, firmware. There is native software or openwrt?
Take a look at this two topics: https://www.nomachine.com/forums/topic/error-61-error-101
https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home
Can you verify that you haven’t this same problem?Thanks for logs, but we still couldn’t reproduce problem. Can you check netstat and ps commands?
Just execute in terminal:/bin/netstat -ln –protocol=unix > netstat_output.txt
/bin/ps awwxo uid,ppid,pid,sid,comm,args > ps_output.txtSend that two files (netstat_output.txt, ps_output.txt) to forum[at]nomachine[dot]com or attach them here (size is restricted).
We weren’t able to reproduce the problem. Tell me more about this update you did. Was it just:
sudo apt-get updateor have you installed something new on the machine, for example Wayland instead of Xorg?Please enable debug, reproduce the problem and send logs from server and client side to forum[at]nomachine[dot]com or attach them here (size is restricted). Instructions about collecting logs you can find there: https://www.nomachine.com/DT04M00076
Hi.
Also changed to a custom service port (also forwarded on router) and restarted- still no IP listed except the LAN local.
NoMachine would list your public IP if you had enabled UPnP.
What is required to allow WAN connectivity?
Are you sure you are connecting to correct IP? On NoMachine you have only local IP since you’ve disabled UPnP. You can find your public IP by using whatismyip[dot]com, for example. That is what you should use to connect to your machine over WAN.
Error 54 is generally caused by firewall, but it can also be when session fails. Are you able to connect with the server or right after you enter username or password? To test, can you create other user (with entirely different name) on system and try to connect?
If problem is still present, please enable debug, reproduce the issue and send logs from server and client side to forum[at]nomachine[dot]com. Instructions about collecting logs you can find there: https://www.nomachine.com/DT04M00076.
Please show NoMachine processes (execute command
ps -Af | grep nx). If you have a firewall running, disable it first.Please run also debug in NoMachine configuration files, reproduce the problem and send logs from server and client side to forum[at]nomachine[dot]com? Follow this link to find instructions about collecting logs: https://www.nomachine.com/DT04M00076.
If you meant inside nx/xfce session, should I do it like after closing all my other work, then substituting logout with nxserver -restart command?
Exactly.
Please use
<em>sudo /usr/NX/bin/nxserver --restart</em>(or “–startup”) command, for restart/startup nx services. Show also processes (execute command<em>ps -Af | grep nx</em>).Logs would be helpful. Please run debug in NoMachine configuration files, reproduce problem and send logs from server and client side to forum[at]nomachine[dot]com? Here you can find instructions about collecting logs: https://www.nomachine.com/DT04M00076.
We reproduced the problem in our lab. We will take a closer look at it.
As a temporary workaround you can use command:
sudo /usr/NX/bin/nxserver –restart
instead of logging out.
Hi.
It looks like it is firewall or wrong port number problem.
Are you using non-native firewall? For test you can disable it or just add port 4000 as an exception in configuration.
There is possibility to connect in reverse side – from your Ubuntu host to your Windows? Maybe port on server is changed? You can check it in “Server status”, by clicking on NoMachine icon in your linux tray (see section 2 and fig. 1 in https://www.nomachine.com/DT11M00107#2 for more details).
