Well, my squiggly nature took over again and I was off to setting up FreeNX over SSH. I started off by installing the freenx server for Arch Linux by following this post and downloading the compiled arch package from here. The install went smoothly but when I tried connecting I kept getting the following error:

1
2
3
4
5
6
7
NX> 203 NXSSH running with pid: 3920
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.6.103 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

After spending quite some time researching and trying several different ways I finally figured out what I was doing wrong. Basically you have to generate a new key pair using `ssh-keygen -d` and tell it to save the key at /usr/NX/home/nx/id_das with no passphrase. Afterwards you save id_dsa.pub to /usr/NX/home/nx/.ssh/authorized_keys2.
Once you do this then you should copy the id_dsa file as server.id_dsa.key to the client’s share/keys directory; for default Windows client installation this was c:\Program Files\NX Client for Windows\share\keys\server.id_dsa.key. Now comes the most important part, make sure that you import this key into the connection that you make, see the screenshot below for more information.

Importing the Private Key

So finally after lots of hard work I got freenx to run over SSH on windows. Below are some screenshots for your pleasures 🙂 Sorry for the humougous size 🙂

GIMP Loading inside a FreeNX Session

A simple Rails application inside a Firefox over a FreeNX session! :)

XFCE4 settings in a FreeNX session

Back to blog...