# cp authorized_keys client.id_dsa.key server.id_ /opt/NX/home/nx/.ssh/ Add those files to your new server, they need the same permissions, names, group and directory!./opt/NX/home/nx/.ssh contains the key files.Transferring nx keys to another freenx server: opt/NX/bin/nxsetup -install -setup-nomachine-key To get the server to accept the default client keys run: In this case you do not need to copy a custom generated key to each client. You will need to copy this client key to each of your clients that want to connect (Windows and linux).Īlternatively you can use the default key that is provided by NoMachine with all clients. By default a new set of random keys are generated during the install, one for the server and one for the clients. Keys are used to authenticate the clients with the server. Note: You should also install "xdialog" on the server or you will not see the "suspend/terminate" dialog when you try to close the window or hit "ctrl-alt-T": pacman -S xdialog 2.1.1 Keys If you are running your SSH daemon on a port other than the default port 22, you'll need to uncomment and update: SSHD_PORT=22 The main configuration file is located at: Verify the following entries in /etc/ssh/sshd_config: Add 'sshd' to daemons array in /etc/rc.conf and ensure your ny/hosts.allow allows ssh services.įor freenx to authentication to work, sshd has to be setup properly. The sshd daemon must be installed and running for it to function properly. If you plan using freenx to connect to a headless PC, keep in mind that you'll also need an X server configured, so you should install any relevant xorg package. 6.8 Cannot connect because command sessreg not found.6.7 GDM/XDM Session Menu Error with non-KDE or Gnome Desktop Managers (more common with non-Arch Linux users).6.5 Wrong password / No connection possible.6.2 Authentication OK, but connection fails.5 Setting up non-KDE or Gnome desktop managers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |