No I hadn't and it seems to do the trick!
Thanks very much
No I hadn't and it seems to do the trick!
Thanks very much
Thanx for this How-To.
It wasn't working directly, but that was my fault; I selected the wrong desktop (KDE), which was on the host not available
I setup freenx a few weeks ago based on similar instructions.
I was curious if you or someone else could tell me the reason for this step.
>> 3) modify the "AuthorizedKeysFile" line in "AuthorizedKeysFile %h/.ssh/authorized_keys2" (default is "%h/.ssh/authorized_keys")
I recently spent a lot of time setting up key authentication in ssh and I think the above instruction might be outdated/uneccessary but I'm not certain. I think recent versions of ssh don't use authorized_keys2 anymore. I can't figure out why it really matters what the file is called. It seems like changing the name would also cause existing keys to stop working.
I will look forward to learning more.
Thanks
Ryan
Thanks for this thread...
I have FreeNX working well with on of my 2 linux boxes, but I can't figure out how to handle connecting to either of 2 boxes (which are both behind the same router and firewall).
If I port forward port 22 to one of the boxes I can access that box without problem. If I try to port forward a different port for the other box. my connection is refused.
Other than changing the router to forward to a new port in the host, changing /etc/ssh/sshd_config to listen for the new port, and adding the new port to the NX client, are there and additional settings I should modify to get this to work??
Thanks...
does anyone know if freenx is being maintained by anyone? seems like a new version hasn't come out in some time. the website i have for them is
http://freenx.berlios.de/
just trying to make sure I have the latest version of hte server running. Maybe there are some improvements in performance etc....
I've installed FreeNX thru apt-get and I've got problems to setup a gnome session. I've followed the instructions at the start of this post. SSH key authentication works on the nxserver. I've enabled gnome sessions in /etc/nxserver/node.conf . But when I try to connect with the NoMachine NX client after authentication a window pops up for a short time showing the NoMachine logo.
The /var/log/nxserver.log output:
Another question I've got is which protocol nx uses, is it a nx protocol or is it also posible to use GDM + xdmcp on port 177? Because xdmcp is enabled, and it is working with a thin client. But selecting xdm in the Nomachine client results in an error that unix-xdm is not supported.NX> 1000 NXNODE - Version 1.4.0-45-SVN OS (GPL)
NX> 700 Session id: boolean-1000-332E484B92FBC5E168B7151EB796B57D
NX> 705 Session display: 1000
NX> 703 Session type: unix-application
NX> 701 Proxy cookie: ac67a433e3357400eb50c258c6c1dd49
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: ac67a433e3357400eb50c258c6c1dd49
NX> 704 Session cache: unix-application
NX> 707 SSL tunneling: 1
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
NX> 1006 Session status: closed
NX> 1001 Bye.
Any one know of a breezy repo with AMD 64 packages for freenx? compiling it from source is a nightmare.
Cool howto, had it going famously in Breezy..
Anyone managed to serve from dapper?
Got it working on the first try. Great instructions.
I've got one question: will FreeNX start on bootup or do I need to start it manually? I didn't see it anywhere in /etc/init.d
Coogan
freenx starts at bootup.Originally Posted by Coogan
Bookmarks