I will look next time for freenx If necessary.ġ°) Have removed nxserver and associate directories.Ģ°) Have removed ssh config files and keysĤ°) Have modify new ssh config file. The second thing you can try if it still doesn't work is adding any users you want to grant nx access to the nx group If after doing that you still have issues there are two things you can try, firstly remove all the files under /home/username/.nx, this will make sure the user you are trying to connect with won't have anything like old configuration or session data that may be interfering You may not actually need the -clean & -purge switches but if you do the settings from your old version will be removed before applying the settings for your updated server and that way you are less likely to have any erroneous settings from your old configuration causing any problems I don't know whether you're using nomachine's server or the freenx server, I've only used the freenx server and this is how you set it up:Īs root, in a terminal (konsole if you use kde) run this command: nxsetup -install -setup-nomachine-key -clean -purge Nxserver typically uses nomachine's key, sounds like you haven't configured your server to use it

Normal because user nx as no key so how can he authenticates ? In fact, reading the logs I see that the key is not found. Merging key in AuthorizedKeysFile NX side or SSH side seems not to work. NX or SSH or BOTH : It seems you cannot change the owner ( I am not sure ) SSH : the builtin user root is added by hand to an ssh_user group. NX : the builtin user nx is added by hand to an ssh_user group. I can connect with SSH from the two computers from any side. SSH : : You can change the ssh AuthorizedKeysFile pathĪuthentication only by Key, not by password. NX : You canNOT change the NX AuthorizedKeysFile path I know that i had to tweek the previous install, but I can't imagine now what I did. After doing somme test (NX ran correctly for a month), I reinstalled NXSERVER from the new version 3.5.

Nx nomachine display quality