If there's no proper way to run it on current glibc version we eventually can drop this compatibility completely. Currently we are trying to keep nx-libs compatible to the original nomachine nxclient. For me this is a sufficient way to test what I wanted to test. Regarding 'is it worth': I don't know if there are people using the old nxclient. Maybe we could convince the glibc developers to add an env var that switches to old behaviour?

Now you can connect to your server using your NoMachine NX client.+++ -469,10 +469,12 _IO_new_file_underflow (FILE *fp) Sudo iptables -A INPUT -p udp -match multiport -dports 4011:4999 -j ACCEPTįor default ports in NoMachine NX see here. In iptables: sudo iptables -A INPUT -p tcp -dport 4000 -j ACCEPT Note: If you are using a firewall, you must allow incoming connections to ports 4000 (TCP) and ports from 4011 to 4999 (UDP): If you want audio support, you should install PulseAudio before installing NoMachine NX: sudo apt-get install pulseaudio You may check for newer releases on the official site. Prerequisites:ĭisplay Manager (SDDM, KDM, LightDM, etcâ¦) installed on your Instance.ĭesktop Environment (KDE, Mate, LXDE, XFCE, etcâ¦) installed on your Instance.ĭownload and install the NoMachine NX package on your server. Note: NoMachine NX is free for both commercial and personal use, however if you need more features and support you must purchase an Enterprise license. In this tutorial we will covering the process of installing and configuring NoMachine NX on Ubuntu. NoMachine NX is a proprietary remote desktop program which offers more features compared to VNC.

Nomachine ubuntu command line