[FreeNX-kNX] FreeNX trouble

[Claudia Neumann]

Hi Jan!

Don't despair!
I just managed to get a freeNX server working on Debian Etch using the 
packages from http://kern.nl/freenx and the clients from 
http://www2.math.uni-paderborn.de/?id=1354
You have to set 
ENABLE_1_5_0_BACKEND="1" 
in /etc/nxserver/node.conf 
and configure 
AuthorizedKeysFile   %h/.ssh/authorized_keys2 
in /etc/ssh/sshd_config.
Next you have to copy the public keys to $HOME/.ssh/authorized_keys2.

Hope that helps

Claudia


Am Montag, 21. Mai 2007 23:04 schrieb Jan Luehr:
> Hello,
>
> sadly I've come again to the point where my FreeNX-Server ist completly
> unuseable.
> If've run freeNX on Debian Etch for months. When Etch finally become stable
> (or around that time), some dist-upgrade broke my installation.
> Broke means:
> - Users were unable to login
> - NXClient itself was able to establish a public key based ssh connection
> - NX logs authentication failures using ssh auth attempts,
> - sshd logging showed some connections but no authentication attempts.
>
> However, at first I suspected zum libraries got incomptible with some new
> etch ones wants and rebuilt the nomachine sources.
> I also upgraded freeNX to 0.6. But that didn't change anything.
> I began playing around with the installation - scripts, but did'nt solve
> the problem.
> However, after a some try-outs I broke NX completely
> - NX doesn't log
> - NXClients timeout:
> NX> 203 NXSSH running with pid: 23412
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: 192.168.1.205 on port: 20290
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> NX> 280 Ignoring EOF on the monitored channel
> NX> 280 Ignoring CLOSE on the monitored channel
> Killed by signal 15.
>
> and ssh logs successful connections
> May 21 22:43:36 alpha sshd[12996]: Accepted publickey for nx from
> 192.168.34.0 port 53791 ssh2
> May 21 22:44:38 alpha sshd[13016]: Accepted publickey for nx from
> 192.168.34.0 port 54625 ssh2
> May 21 22:45:49 alpha sshd[13037]: Accepted publickey for nx from
> 192.168.34.0 port 54626 ssh2
> May 21 22:47:45 alpha sshd[13072]: Accepted publickey for nx from
> 192.168.34.0 port 40863 ssh2
> May 21 22:48:17 alpha sshd[13080]: Accepted publickey for nx from
> 192.168.34.0 port 34256 ssh2
>
> In an act of despair I renamd all my NX-libs, bins and dirs, killed the NX
> users and installed freenx from
> http://kern.nl/freenx/ ./
>
> But that haven't changed anything at all.
> Do you have any ideas how to repair my installation?
>
> Thanks,
> Keep smiling
> yanosz
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

-- 
Viele Grüße

Claudia Neumann