This will force nx to use ssl encryption at all times. For added security you might also want to go back to the server machine and edit the /usr/NX/etc/server.cfg file again. You should now be able to connect to the nxserver on a non-standard port with a custom ssh key.Ĩ. Just log into the server (or ssh to the server) and do the following:Ĭode: sudo /etc/init.d/ssh restartOn the client machine you should then launch the nx client, press the configure button, and enter the new port in the general tab. Not good! However, changing these keys is simple. Potentially this means that anyone with the nxclient package installed could authenticate against your server. #NOMACHINE SET USERNAME AND PASSWORD INSTALL#When you first install the nx packages they ship with default keys that are the same for everyone. If all went well you will now want to change the default ssh keys that the NX server uses. If all goes well a session should open on your desktop displaying the server machine's desktop.Ħ. You should be able to log in as a normal user with the user name and password that you normally log into the system with. Open the NX connection wizard and follow along. You may have to do a 'killall gnome-panel' before the NX entry appears in the menu, but once it has you'll find it under applications/internet. At this stage it's worth testing that everything works 'as is'. Repeat the above on the client machine - on the client you only need the nxclient package and not the nxserver and nxnode packagesĥ. deb packages in your home directory when you do this.Ĥ. Put the files in the home directory of the machine you want to use as the server, open a terminal, and install them:Ĭode: sudo dpkg -i *.debnote: make sure that these are the only. Initially you should also use the standard port 22 for ssh as well.ģ. You must ensure that password based authentication is enabled in the /etc/ssh/sshd_config file of the server machine. Make sure openssh-server is installed on the server machine/s and that you can ssh into into those machines. I believe FreeNX is very similar, but having never tried it I don't know if these instructions will work with that as well. #NOMACHINE SET USERNAME AND PASSWORD SOFTWARE#Just for information, both the server and client software were installed on Hardy, and I've used the latest version of the Nomachine packages and not the FreeNX packages. This isn't strictly necessary, and so I haven't included it. I know there are other how tos on the forum, but most seem to include a step about adding users. I'm posting what I did here in case someone else wants to give NX a try. What I wanted was for the connection to a remote machine to be as secure as possible, and more usable than VNC through an ssh tunnel, without having to jump through too many configuration hoops. So in the end I just waded through Nomachine's online documentation and help system. #NOMACHINE SET USERNAME AND PASSWORD HOW TO#However, searching this forum and google turned up lots of conflicting instructions about how to configure things. Overall it's much faster than VNC and very simple to set up. After struggling with VNC for some years I finally tried out Nomachine's NX server instead.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |