freenx acceso remoto

FREENX, ACCESO REMOTO AL ESCRITORIO LINUX DESDE WIN

En el servidor:

Añadir en /etc/apt/sources.list (mientras funcione): deb http://krnl.nl/freenx/ ./

# apt-get update
# apt-get install ssh freenx
# apt-get install freenx

Durante la instalación seleccionar “NoMachine key”. Finalizado el proceso:

# gedit /etc/nxserver/node.conf

Añadir la línea (en una sola línea y sin espacios):

APPLICATION_LIBRARY_PRELOAD=/usr/lib/libX11-nx.so.6.2:/usr/lib/libXext-nx.so.6.4:
/usr/lib/libXcomp.so.2:/usr/lib/libXcompext.so.2:/usr/lib/libXrender-nx.so.1.2

# nxsetup

——> You did select no action.

FreeNX guesses that you want to _install_ the server.
Type “y” to abort the installation at this point in time.
“N” is the default and continues installation.
Use “/usr/sbin/nxsetup –help” to get more detailed help hints.

Do you want to abort now? [y/N] N

——> It is recommended that you use the NoMachine key for
easier setup. If you answer “y”, FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
“N” is default and uses the NoMachine key for installation.

Do you want to use your own custom KeyPair? [y/N] N
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

—-> Testing your nxserver configuration …
Warning: Could not find nxdesktop in /usr/lib/nx. RDP sessions won’t work.
Warning: Could not find nxviewer in /usr/lib/nx. VNC sessions won’t work.
Warning: Invalid value “DEFAULT_X_SESSION=/etc/X11/xdm/Xsession”
Users might not be able to request a default X session.
Warning: Invalid value “COMMAND_START_KDE=startkde”
Users will not be able to request a KDE session.
Warning: Invalid value “COMMAND_START_CDE=cdwm”
Users will not be able to request a CDE session.
Warning: Invalid value “COMMAND_SMBMOUNT=smbmount”. You’ll not be able to use SAMBA.
Warning: Invalid value “COMMAND_SMBUMOUNT=smbumount”. You’ll not be able to use SAMBA.

Warnings occured during config check.
To enable these features please correct the configuration file.

<—- done

—-> Testing your nxserver connection …
HELLO NXSERVER – Version 1.5.0-60 OS (GPL)
NX> 105 quit
Quit
NX> 999 Bye
<— done

Ok, nxserver is ready.

PAM authentication enabled:
All users will be able to login with their normal passwords.

PAM authentication will be done through SSH.

Para comprobar que el servidor está funcionando:

# nxserver –status
NX> 100 NXSERVER – Version 1.5.0-60 OS (GPL)
NX> 110 NX Server is running
NX> 999 Bye
Si despues del ‘<—— done’ sale algo parecido a :

—-> Testing your nxserver connection …

Ubuntu 8.04

Permission denied (publickey,password).
Fatal error: Could not connect to NX Server.
Please check your ssh setup:
The following are _examples_ of what you might need to check.
- Make sure “nx” is one of the AllowUsers in sshd_config.

(or that the line is outcommented/not there)
- Make sure your sshd allows public key authentication.
- Make sure your sshd is really running on port 47321.
- Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to authorized_keys2.
(this should be a filename not a pathname+filename)

Editar /etc/ssh/sshd_config y en AllowUsers añadir nx, asegurarse de que port sea el especificado (si no es el 22) y está descomentado y descomentar AuthorizedKeysFile añadiendo 2 al final:

# What ports, IPs and protocols we listen for

Port 47321
AuthorizedKeysFile %h/.ssh/authorized_keys2
AllowUsers linux@192.168.2.4 pepe antonio nx

En el cliente

Descargar e instalar NX Client (http://www.nomachine.com/download.php)

Despues de los clásicos “next”, especificar nombre de sessión, IP, puerto (el mismo que consta en /etc/ssh/sshd_config y en /etc/nxserver/node.conf) y determinar el tipo de conexión (ADSL si en conexión remota y LAN si es red local) en la pantalla desktop especificar el tipo de servicio (UNIX), escritorio (GNOME o KDE) y la dimensión de la pantalla. Se creará un lanzador que cuando se clique pedirá nombre y contraseña (del remoto).

Nota.- Se deberá desbloquear el contafuegos de windows y tener el puerto especificado del router remoto abierto.