HOWTO: Install freenx

[arrowood]

Thanks for all the tips in this thread. This weekend, I successfully migrated from the nomachine server to the freenx.

This is what I did:

Code: Select all

ACCEPT_KEYWORDS="~x86" emerge -p =nx-x11-1.4.0-r3 =nxclient-1.4.0-r3 =nxproxy-1.4.0-r2 =nxserver-freenx-0.2.7 =nxssh-1.4.0-r1

I did this next part just in case; You probably don't need to...

Code: Select all

rm -Rf /usr/NX/home/nx/.ssh/authorized_key*
rm -Rf /usr/NX/home/nx/.ssh/client.id_dsa.key
rm -Rf /usr/NX/home/nx/.ssh/server.id_dsa.key
keygen (replaces above except for authorized_key2)
cp /usr/NX/home/nx/.ssh/server.id_dsa.key /usr/NX/home/nx/.ssh/authorized_key2

Now install client.id_dsa.key into the clients share directory
(C:\Program Files\NX Client for Windows\share if windows client)

Finally

Code: Select all

chmod u+x /usr/NX/var/db/*
chown -R nx:root /usr/NX/
chmod +x /user/NX/etc
nxserver --userlist
nxserver --userdel arrowood
nxserver --useradd arrowood
nxserver --passwd arrowood

Good luck!

[arrowood]

Reconnecting to a suspended session does not work for me, like most other people. Since I haven't seen anyone post the exact details from the client when it fails to reconnect to a suspended session, I thought I would:

Code: Select all

NXPROXY - Version 1.4.0

Copyright (C) 2001, 2004 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '3320'.
Info: Waiting for connection from any host on port '2745'.
Info: Accepted connection from '127.0.0.1' on port '2827'.
Info: Connection with remote proxy established.
Info: Handshaking with remote proxy ':5000' completed.
Info: Synchronizing local and remote caches.
Info: Using cache parameters 4/262144/8192KB/8192KB.
Info: Using image cache parameters 1/1/32768KB.
Info: Using adsl link parameters 8192/80/16/4096.
Info: Using pack method '16m-jpeg-7' with session 'unix-kde'.
Info: Using ZLIB data compression level 3.
Info: Using ZLIB data threshold set to 32.
Info: Using ZLIB stream compression level 6.
Info: Using remote ZLIB data compression level 3.
Info: Using remote ZLIB stream compression level 6.
Info: Using cache file 'C:\DOCUME~1\USER~1.ADM\NX73F8~1/cache-unix-kde/S-651ACBCE1B458C673DAB4F1753E7D932'.
Info: Using remote server connected on port '2745'.
Info: Starting X protocol compression.
Info: Established X server connection.
Error: Decompression of data failed. Error is 'data error'.
Error: Lost connection to peer proxy on FD#5.
Error: Connection with remote peer broken.
Error: Please report this problem to support personnel.

with the relevant part being

Code: Select all

Error: Decompression of data failed. Error is 'data error'.
Error: Lost connection to peer proxy on FD#5.
Error: Connection with remote peer broken.
Error: Please report this problem to support personnel.

The packages I have installed are:

• nx-x11-1.4.0-r3
  nxclient-1.4.0-r3
  nxproxy-1.4.0-r2
  nxserver-freenx-0.2.7
  nxssh-1.4.0-r1

The details above are from the latest windows client from nomachines site.

Has anyone else got this same error message? Is this a issue with the various NX libs or the freenx wrapper?

Has anyone been able to reconnect to sessions using the NX client and server (not freenx)?

[jinzishuai]

I am almost there. Now I am authenticated in and there is a X window poped up which I think is the nxagent. But I don't see my KDE desktop coming out.
Here is the /tmp/nxserver.log:

Code: Select all

-- NX SERVER START:
HELLO NXSERVER - Version 1.4.0-02 OS_(GPL)
NX> 105 Hello NXCLIENT - Version 1.3.2
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: seki
NX> 102 Password:
NX> 103 Welcome to: jinshi.homelinux.net user: seki
NX> 105 startsession --session="home" --type="unix-kde" --cache="8M" --images="32M" --cookie="1a4f1aa57a73ba7be7bc2f52a87a691e" --link="lan" --render="1" --imagecompressionlevel="-1" --backingstore="never" --imagecompressionmethod="2" --geometry="fullscreen" --keyboard="us" --kbtype="pc102/us" --media="0" --agent_server="" --agent_user="" --agent_password=""

user=seki&userip=192.168.88.2&uniqueid=4B43DA4B08A908B3F3F7782157D8CFE4&display=1001&&session=home&type=unix-kde&
cache=8M&images=32M&cookie=1a4f1aa57a73ba7be7bc2f52a87a691e&link=lan&render=1&imagecompressionlevel=-1&
backingstore=never&imagecompressionmethod=2&geometry=fullscreen&keyboard=us&kbtype=pc102/us&media=0&agent_server=&
agent_user=&agent_password=
NX> 1000 NXNODE - Version 1.4.0-02 "OS_(GPL)"
NX> 700 Session id: jinshi.homelinux.net-1001-4B43DA4B08A908B3F3F7782157D8CFE4
NX> 705 Session display: 1001
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 09d43e09a7d83ba558169ec05bda48c2
NX> 702 Proxy IP: 192.168.88.2
NX> 706 Agent cookie: 1a4f1aa57a73ba7be7bc2f52a87a691e
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 exit
Exit
NX> 999 Bye
NX> 1006 Session status: closed
NX> 1001 Bye.

It seems to me all right because it is the same as the Redhat machine with nxserver working properly.

Do you what's going wrong?
Thanks a lot.

[coffeemike]

Guys --

Great work on getting this set up.

I emerged the latest nxserver-freenx package last night, and am close to getting it to work. Note that I did not have any other X environment set up previously. Here's what I need help with:

-- I had sshd configured for pubkey authentication prior to the install; however, the sshd package assumes that keys are stored in authorized_keys, not authorized_keys2. I've not edited that setting myself, so I don't know if that's a mismatch between the two packages. Moving the contents of authorized_keys2 into authorized_keys solved my first connection problems.

-- I have no nxnode.conf file, nor a sample to start from.

-- Any tips on how to point to a desktop other than GNOME/KDE? I'm running this on a computer that has been challenged to run these before, so I'd like to use a lighter WM.

Other than that (and a compilation error with another required library), everything went smoothly.

[coffeemike]

Sorry - I meant node.conf, not nxnode.conf.

see http://www.nomachine.com/documentation/admin-guide.php

[sibov]

Hi, i have the following problem

NX> 203 NXSSH running with pid: 3512
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.3.195 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
awk: cmd. line:2: fatal: cannot open file `/etc/ssh/sshd_config' for reading (Permission denied)
HELLO NXSERVER - Version 1.4.0-02 OS_(GPL)
NX> 105

Any help would be appreciated.
Thanx and best regards.

[vdboor]

Any tips on how to point to a desktop other than GNOME/KDE? I'm running this on a computer that has been challenged to run these before, so I'd like to use a lighter WM.

You can choose this in the NXClient somewhere under options.
I guess you can point it to any other script if you add a new entry. Start your window-manager (or /etc/X11/something.sh) from that script.

[djco]

arrowood's tutorial seems to have helped me since my last try, but the authentication is now buggered:

NX> 203 NXSSH running with pid: 2672
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.0.13 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

I wonder what the problem could be here?

[spanommers]

arrowood's tutorial seems to have helped me since my last try, but the authentication is now buggered:

NX> 203 NXSSH running with pid: 2672
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.0.13 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

I wonder what the problem could be here?

I think I would get that error if I hadn't updated the public key on the client (this is assuming you generated a new key for the server).

[djco]

I did copy the client.blabla to my client's share directory, though.

[spanommers]

Have you tried enabling debugging on the server? In /usr/NX/bin/nxserver around line 29, set NX_LOGGING to 1. Then you can take a look in the log file after trying a connection.

BTW, did you copy the key from the server's "/usr/NX/home/nx/.ssh/client.id_dsa.key" (not "/usr/NX/share/client.id_dsa.key")?

[sibov]

arrowood's tutorial seems to have helped me since my last try, but the authentication is now buggered:

NX> 203 NXSSH running with pid: 2672
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.0.13 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

I wonder what the problem could be here?

I think I would get that error if I hadn't updated the public key on the client (this is assuming you generated a new key for the server).

m2 my awk error is away but the authentication failed!

It also failes with the client.id_dsa.key copyed into /usr/NX/share/

[djco]

Code: Select all

cp /usr/NX/home/nx/.ssh/server.id_dsa.key /usr/NX/home/nx/.ssh/authorized_key2

spanommers, thanks for the help, but I have no conquered this problem. It has to do with the above line in arrowood's tutorial that seems to be wrong. I think it should be authorized_keys2? Or maybe authorized_keys, I made both.

Next problem: when opening the NX client on my Windows machine (in the same network, I get a black screen with a cursor likes a cross. Nothing else. In the client preferences, I've set NX to open up startxfce4, but no X stuff is ordinarily running on my server (because, hey, it's a server). So, I guess it has something to do with that. If anyone could tell me how to fix this, I would be very grateful.

[buchan]

Code: Select all

ACCEPT_KEYWORDS="~x86" emerge -p =nx-x11-1.4.0-r3 =nxclient-1.4.0-r3 =nxproxy-1.4.0-r2 =nxserver-freenx-0.2.7 =nxssh-1.4.0-r1

Thank you for posting that arrowood. I have been following this thread since it was started trying to get a FreeNX server running on my gentoo server, resulting in a failure each time. Emerging all the packages you mentioned above surprising fixed all my problems. My clients connected perfect.

What is also surprising is that resuming apears to work fine! I guess I'm just lucky.

Thanks guys.

[coffeemike]

Just a word about changing keys. After running nxkeygen and copying the server.id_dsa.pub.key to authorized_keys, I had to change ownership of the authorized_keys file from 'root' to 'nx' in order for authentication to work:

Code: Select all

# chown root /usr/NX/home/nx/.ssh/authorized_keys

I had deleted the previous file before copying that across, so this may not apply if you copy the new key into the existing file.[/code]

[rasmussen]

I've gotten freenx up and running, but cannot seem to get the floating window mode working. Has anyone had luck with that?

[sibov]

Code: Select all

NXPROXY - Version 1.4.0

Copyright (C) 2001, 2004 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '1464'.
Info: Connecting to remote host '192.168.3.195:5002'.
Info: Aborting procedure due to signal '15'.

[Magnum_]

I've just done this :

ACCEPT_KEYWORDS="~x86" emerge nxserver-freenx
nxserver --userlist
nxserver --useradd blabla
nxserver --passwd blabla
nxserver --status (it should be "running" here)
then /etc/init.d/sshd (re)start

Connected with the latest NXclient from nomachine.org, and it worked without a flaw. The latest client asks you if you want to accept the auth key, like putty does. If you accept, the connection is made automatically. It works amazingly well, even on a slow machine (P1 200, windows 2000), I can connect to my much much faster machine, and it works great. Think of the possibilities E.g. for schools, they have a classroom with 20 old P1's. They just buy one decent A64/P4 machine with some extra memory, and the entire classroom is "upgraded" with a relatively small cost !

[codeine]

jinzishuai, it seems that you can't resume session because nxclient closes session too fast - server didn't get your answear to question(suspend/terminat/..)?

check ps output carefully.

18141 ? S 0:00 0 475 1752 1052 0.2 /bin/bash /usr/NX/bin/nxnode --startsession
18146 ? S 0:00 0 2339 10636 4308 1.1 \_ /usr/NX/bin/nxagent -persistent -name NX - p2p@codeine:1005 - server (GPL Edition) -geometry fullscreen -bs when_requested :1005
18172 ? S 0:00 0 1176 15139 7952 2.0 \_ nxclient -dialog yesnosuspend -caption NX - p2p@codeine:1005 -message Press the suspend button to disconnect the running session.?You will be able to resume the session at later time. Press the?terminate button to exit the session and close all the running?programs. -display :1005
18348 ? S 0:00 0 2339 12400 5940 1.5 \_ /usr/NX/bin/nxagent -persistent -name NX - p2p@codeine:1005 - server (GPL Edition) -geometry fullscreen -bs when_requested :1005
18142 ? S 0:00 0 475 1752 1056 0.2 /bin/bash /usr/NX/bin/nxnode --startsession
18155 ? S 0:00 0 235 5312 2532 0.6 \_ /usr/bin/xterm
18168 pts/13 Ss+ 0:00 0 475 1964 1276 0.3 \_ bash

btw, i have to delete ~/.nx contents and kill nx processes to start new session.

[codeine]

with that ps output is everything is ok ;] because i have got resume working.
just start new session in fullscreen mode.

[RattyMan]

FYI, Just tried to emerge from the ebuilds and that failed. I am using gcc 3.4.3 which failed on the build of nx-x11-1.4.0-r3.

Changed to gcc 3.3.4 and it has built fine.

[vdboor]

FYI, Just tried to emerge from the ebuilds and that failed. I am using gcc 3.4.3 which failed on the build of nx-x11-1.4.0-r3.

Changed to gcc 3.3.4 and it has built fine.

I think you should look for some incompatibilities between libstdc++.so.6 and libstdc++.so.5. If some of your libraries still use the .5 version, new stuff can break. (also check config.log from the build/work folder)

There is a reason why developers suggest

Code: Select all

emerge -e system;  emerge -e system; emerge -e world; emerge -e world

, and I'm experiencing this right now. I'm still trying a quicker way, with a lot of dependency-conflicts involved.

[Gandalf98]

I've installed the freenx-server following the instruction, but when I try to connect to my linux-box from a remote win-xp client, I've got the folowing error:

Code: Select all

Loop: PANIC! Error in environment option 'cookie'. No value found.
Error: Error in environment option 'cookie'. No value found.
Error: NX transport initialization failed.

I can't find the option 'cookie', can someone give a clue where to search?

Thanks in advance

[Evangelion]

Any news on getting FreeNX to run on AMD64?

[thebigslide]

FYI, Just tried to emerge from the ebuilds and that failed. I am using gcc 3.4.3 which failed on the build of nx-x11-1.4.0-r3.

Changed to gcc 3.3.4 and it has built fine.

I think you should look for some incompatibilities between libstdc++.so.6 and libstdc++.so.5. If some of your libraries still use the .5 version, new stuff can break. (also check config.log from the build/work folder)

There is a reason why developers suggest

Code: Select all

emerge -e system;  emerge -e system; emerge -e world; emerge -e world

, and I'm experiencing this right now. I'm still trying a quicker way, with a lot of dependency-conflicts involved.

No, I did an emerge -e system; emerge -e system; emerge -e world; emerge -e world as has been suggested. I also tried emerging with basic CFLAGS and nx-x11 any version WILL NOT BUILD with gcc-3.4.

Tried again after switching to gcc-3.3.5 and still using libstdc++.so.6 and it built just fine. It build with crazy CXXFLAGS, too. It simply won't compile cleanly with gcc-3.4.anything because for a reason unknown to me, a bunch of symbols get trashed. It fails on compiling just about any of the source files, even if they are built in a different order.

If someone has been able to compile nx-x11 with gcc-3.4, you're my hero.