FreeNX

The NX protocol aims at offering a stateful desktop session to remote users, like VNC. The most prominent difference is that NX requires less bandwidth. FreeNX is one implementation of the NX protocol.

QuickStart

In this chapter, the SUSE Linux distribution is used as example.

• Install FreeNX

yast -i FreeNX

• Setup FreeNX:

nxsetup

continue as advised. The NX server is started automatically.

• Connect to the NX server

nxclient

You can now log in.

Trial 2

FreeNX server is not available with SUSE 13.1 so I

# yast -i expect
# wget http://download.opensuse.org/repositories/home:/beyerle:/NX/openSUSE_13.1/i586/NX-3.5.0-123.1.i586.rpm
# wget http://download.opensuse.org/repositories/home:/beyerle:/NX/openSUSE_13.1/i586/FreeNX-0.7.3-7.1.i586.rpm
# rpm -ivh NX-3.5.0-123.1.i586.rpm FreeNX-0.7.3-7.1.i586.rpm

now qtnx asks me for a password but I don't know which one

but ps -Hef helps:

root      4173  3692  3 06:17 pts/4    00:00:00       qtnx
root      4174  4173  0 06:17 pts/4    00:00:00         ssh -p22 -iid.key nx@localhost -x -2 -oRhostsAuthentication no -

TroubleShooting

• starting the nxagent, you get

/usr/NX/bin/nxagent: error while loading shared libraries: libXcomp.so.3: cannot open shared object file: No such file or directory

Download nxcomp from http://www.nomachine.com/sources.php and install it. Copy libXcomp.* to /usr/lib.

• during nxsetup, you get

strings: '/usr/bin/nxagent': No such file
Error: Could not find 1.5.0 or 2.[01].0 version string in nxagent. NX 1.5.0 or 2.[01].0 backend is needed for this version of FreeNX.

copy /usr/NX/bin/nxagent to /usr/bin

• The connection fails during the "Negotiating link parameters" step.

Stop the fireWall on the target computer.

• The connection fails after the "Authentication completed" step.

you get an error message like that:

NX> 1004 Error: NX Agent exited with exit status 1.
Can't open /var/lib/nxserver/db/running/sessionId{CBE6C1DE8281C9A77A5F72F05947EE1F}: No such file or directory.
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{CBE6C1DE8281C9A77A5F72F05947EE1F}': No such file or directory

Possible workaround: re-install the NX server

• You get an error when logging in

Test the connection using ssh, there may be no lines of text sent when logging in. So, e.g. not

hello world
$