I would need a magnifying glass to read this. Please don't use HTML on this list.
On Wednesday 25 November 2015 18:50:14 Bill Damage wrote: > I have exactly the same problem mentioned in this thread. I think > something changed and broke the authentication during an update. i found > this message by Googling and just joined the mail list to ask for help. I > have done everything mentioned in the thread, and here's where I'm at: > (it worked fine before some regular update broke it) Thanks! > [root@tiger ssh]# nxsetup --test > ----> Testing your nxserver configuration ...Warning: Invalid value > "APPLICATION_LIBRARY_PRELOAD=/usr/lib64/nx/libX11.so.6:/usr/lib64/nx/libX > ext.so.6:/usr/lib64/nx/libXcomp.so.3:/usr/lib64/nx/libXcompext.so.3:/usr/l > ib64/nx/libXrender.so.1". /usr/lib64/nx/libX11.so.6 could not be found. > Users will not be able to run a single application in non-rootless > mode.Warning: Invalid value "COMMAND_START_CDE=cdwm" Users will > not be able to request a CDE session.Warning: Invalid value > "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA.Warning: > Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use > SAMBA.Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version > 1.2. Users will not be able to enable printing. Ignore if you use > cups > 1.2Error: Could not find 1.5.0 or 2.[01].0 or 3.[012345].0 version > string in nxagent. NX 1.5.0 or 2.[01].0 or 3.[012345].0 backend is needed > for this version of FreeNX. Warnings occured during config check. To > enable these features please correct the configuration file. <---- done > ----> Testing your nxserver connection ...Permission denied > (publickey,gssapi-keyex,gssapi-with-mic,password).Fatal error: Could not > connect to NX Server. Please check your ssh setup: > The following are _examples_ of what you might need to check. > - Make sure "nx" is one of the AllowUsers in sshd_config. (or > that the line is outcommented/not there) - Make sure "nx" is one > of the AllowGroups in sshd_config. (or that the line is > outcommented/not there) - Make sure your sshd allows public key > authentication. - Make sure your sshd is really running on port > 22. - Make sure your sshd_config AuthorizedKeysFile in sshd_config > is set to authorized_keys. (this should be a filename not a > pathname+filename) - Make sure you allow ssh on localhost, this could > come from some restriction of: -the tcp wrapper. Then add in > /etc/hosts.allow: ALL:localhost -the iptables. add to it: $ > iptables -A INPUT -i lo -j ACCEPT $ iptables -A OUTPUT -o lo -j > ACCEPT[root@tiger ssh]# -- Rgds Peter
