For Hardy, Intrepid, Jaunty, and beyond, an updated version of this guide is contained here: I would suggest users follow the steps to this new guide and use this guide as a reference. Tutorial inspired by my original post: attempting to get working ssh tunneled FreeNX server with only opengl freenx server package supplied by seveas repositories. There is another how-to guide for setting up FreeNX server under breezy, however installation is with packages supplied by nomachine and to my knowledge are not OpenGL compliant: ġ. Modify /etc/apt/sources.list to include seveas repositoriesĢ. Ensure paths to fonts are correct within nfĤ. Perform some key management functions for ssh server and nx user - copy authorized_keys2 file to authorized_keysĥ. (Optional) - Setup ssh port number on router, sshd_config, and nf fileĦ. Perform key management for individual clients - copy authorized_keys2 file to authorized_keys in user personal. WindowsXP client: NoMachine Nx Client for Windows Version 2.1.0-17ġ. U(K)(X)buntu Feisty Fawn 7.04 distribution (likely to work with earlier ubuntu distros - however this is untested).ģ. Static IP address for server, or a dynamic IP address that is unlikely to changeĤ. Firewall either disabled, or enabled to allow for ssh communication If behind router, ssh port is port forwarded to routerĥ. Windows NoMachine Nx clients may be obtained for free from: Īdd the following at the bottom of the file: The seveas repository provides Nx Client for Linux. List of additional repositories may be found here: If for some reason, these seveas mirrors are broken additional repositories may be added. These packages can be authenticated using gpg - which helps to avoid authentication errors. Gpg -export -armor 1135D466 | sudo apt-key add -Ģ. Go to the section entitled "Files" and look at the different Font Paths. You need to ensure that these font paths are correct. Oddly, I have a third machine (Arch Linux desktop) and my laptop connects to it just fine, and my Arch Linux desktop also reports Error 104 trying to connect to the ElementaryOS desktop, so I suspect the problem is between ElementaryOS and NoMachine, but I’m not sure what to look for.When I originally installed from the Edgy Live CD these paths were totally incorrect, but caused no problem until the FreeNx server installation. Since the error occurs 100%, I cleared all the logs between restarting nxserver with systemctl stop nxserver & clear logs & systemctl start nxserver. I’ve collected the client and server logs after reproducing this issue (it occurs 100%) per the instructions at and attached them to this post. On the client side, the logs mention a failure switching over to proxy. Reach your computer on the other side of the world in just a few clicks. Thanks to our NX technology, NoMachine is the fastest and highest quality remote desktop you have ever tried. There were some errors reported with pulseaudio, so I disabled AudioInterface in node.cfg. NoMachine is free for everybody to use Connect to any computer remotely at the speed of light. I dug through the logs and found little from the server side. I attempted to use the SSH protocol instead of NX, but during the attempt to connect via password, nxplayer announced that SSH was not available and switched back to NX. I purged old settings from both machines: on the server side, I rm -rf /usr/Nx between uninstalling and reinstalling on both machines, I rm -rf $HOME/.nx for the respective users. I upgraded NoMachine to 6.8.1 since I first experienced the issue with NoMachine 6.1 on both machines. The remote side (nxserver) also runs NoMachine 6.8.1 on an ElementaryOS Juno desktop. On the client, I’m running NoMachine 6.8.1 on an Arch Linux laptop. Just prior to the error, nxplayer briefly mentions an attempt to reconnect. The error reported on the client from nxplayer is: I’m having trouble connecting NoMachine to one of the desktops on my LAN.
0 Comments
Leave a Reply. |