FreeNX Remote Control Linux Platform solution

FreeNX is a new remote control solution after VNC in recent years, the basic principle is to compress the xwindows signal and transmit it to the remote client to display, while VNC is to intercept the screen image processing transmission directly. Thus, under the same transmission channel conditions, FREENX can provide better operational sense and real-time performance than VNC, and because its implementation relies on Xwindows, FreeNX currently does not support windows as a remote control server side.

FreeNX Server-side installation

1, http://www.aliyun.com/zixun/aggregation/10482.html "> download software:

#wget http://fedoranews.org/contributors/rick_stout/freenx/freenx-0.3.1-0.fdr.0.noarch.rpm

#wget http://fedoranews.org/contributors/rick_stout/freenx/nx-1.4.0-0.fdr.4.i386.rpm

#wget http://www.linux-tip.net/cms/workshop/freenx_FC3/expect-5.42.1-1.i386.rpm

#wget ftp://fr.rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/nc-1.10-18.i386.rpm

2, installation software:

#rpm-IVH nc-1.10-18 rpm for i386

#rpm-I nx-1.4.0-0.fdr.4.i386.rpm

#rpm-I expect-5.4.2.1-1.i386.rpm

#rpm-I freenx-0.3.1-0.fdr.0.noarch.rpm

3. Configure Nxserver

#/usr/bin/nxsetup--install

Setting up/etc/nxserver ... done

Setting up/var/lib/nxserver/db ... done

Setting Up/var/log/nxserver.log ... done

Setting up known_hosts and authorized_keys2 ... done

Setting up permissions ... done

Ok, Nxserver is ready.

PAM Authentication enabled:

All Users is Inc. to login with misspelling normal passwords.

PAM authentication is done through SSH.

Please ensure the SSHD on localhost accepts password authentication.

You can change this behaviour in the/etc/nxserver/node.conf file.

Have fun!