It may be possible to use the default keys generated during the freenx ebuild, but I chose to regenerate mine for security and clarity: You can fix SSH by modifying the file above and restarting ssh: Either way, these two systems have to reference the same file, or it won't work. You can fix this by using one of the two following methods: Either fix the sshd_config to use authorized_keys2, or fix freenx to use authorized_keys.
The next pitfall occurs because openssh uses the authorized_keys file, while freenx defaults to using the authorized_keys2 file. The second line is not activated by default, I think. Also, make sure you have the following lines enabled in your ssh config snippets: Make sure you have SSH installed, if you don't already ("emerge openssh"). Most of the initial setup problems revolve around SSH setup. The above line should pull in everything. $ echo "net-misc/nxserver-freenx commercial" > /etc/portage/e So, after experimenting with both versions, and falling in several pitfalls, here's my HOWTO on Connecting a WinXP box to a Gentoo box via FREENX server and NoMachine WinXP client:įirst, you will want to add the commercial USE flag for the nxserver otherwise, you will encounter blocking issues with the client: If any of you have a simple step min-howto for me I would sure appreciate it!! I'm talking about not being able to get ANY version to work. Hey guys - I'm not talking about being unable to get 1.5.0 to work, or whatever. Posted: Mon 8:27 pm Post subject: HOWTO Connect a WinXP box to a Gentoo box via FREENX server I thought this was fixed in later ebuilds.
The file NX.h needs to be 'ln -s'ed in a standard location like /usr/include after the nx-x11 install. Gentoo Forums Forum Index Documentation, Tips & TricksĪny ideas about the compile error I posted a while back?
#Nomachine disable alt f4 install
Gentoo Forums :: View topic - HOWTO: Install freenx
0 kommentar(er)
