ssh is great. But sometimes I just need a desktop. The remote desktop functionality offered by Ubuntu is kind of limited. For example, I just don’t know how I can enable remote desktop easily in the first place if one is not in front of the host already. Moreover, Ubuntu’s remote desktop is limited to LAN. I would love to do something similar to the Linux version of teamviewer.

It turns out that free remote desktop over the Internet is already out there for Linux/Ubuntu users! Better still, it is a piece of cake to install.

Host Ubuntu 9.04,rodando uma Vitual Machine Windows XP, acessando um servidor FreeNX Ubuntu 9.04, via Hamachi…

The ability to login graphically into any computer from a remote location has a number of uses. In my case it allows me to create a setup where students in my school can easily login graphically into the universities computer lab and use many of the applications which are installed there (like Matlab which is only licensed to run on our lab computers) It also allows me to log into my work computer from home. To create this setup we would need a tool called Freenx.

FreeNX
FreeNX is a system that allows you to access your desktop from another machine over the Internet. You can use this to login graphically to your desktop from a remote location.

Advantages of FreeNX
One advantage of FreeNX is that it is based on the SSH Protocol so your packets are transferred over an encrypted channel which in human language means nasty people can’t see what you are doing and potentially compromise your computer

Installation

Installation FreeNX is in Two Phrase the server and the client

Server Installation

The server version is installed on the remote system you want to login to. To install the server version you need to add the following repository to your sources.list

Hardy Heron
deb http://ppa.launchpad.net/freenx-team/ubuntu hardy main
deb-src http://ppa.launchpad.net/freenx-team/ubuntu hardy main

Intrepid Ibex
deb http://ppa.launchpad.net/freenx-team/ubuntu intrepid main
deb-src http://ppa.launchpad.net/freenx-team/ubuntu intrepid main

Jaunty Jackalope
deb http://ppa.launchpad.net/freenx-team/ubuntu jaunty main
deb-src http://ppa.launchpad.net/freenx-team/ubuntu jaunty main

Now we add the public Key for the FreeNX PPA with:
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 2a8e3034d018a4ce

and we install with:
sudo apt-get update ; sudo apt-get install freenx

That is all that is needed for the installation of freenx server on our remote machine.

Client Installation

The client is installed on the machine you want to login from.

There are Two type of FreeNX clients available the non free and open source version (and freedom hating version ) and the free and open source version

The Non-free version
This is the official NX version and can not be installed from the Ubuntu repository but can be deb version for ubuntu can be downloaded from here
Double click to install.
Once installed you find it at Application-Internet-NX Client for Linux

The Free and Open Source version can be downloaded from the Ubuntu repository by running:
sudo apt-get install qtnx
Once installed you find it at Application-Internet-QTNX

Usage
What i really love about FreeNX is its usage, its very easy to use and all your do is launch the client which once installed can be found under /Application/Internet/Nx Client for LInux

Once you start the Program it displays a wizard which would guide you through the configuration process

=Session: First Thing you do is create a session which is like a profile of the remote machine you want to connect to. You can have many sessions of different remote machines which allows you to easily choose a session and login to the machine configure to the session.
Host: The IP address of the remote machine you want to login to
Select you Internet Type: Here is were you also get to indicate what type of internet connection you are running, NX compresses your data over the network so the slower your internet connection the higher the compression rate of your data (or so it seems) then you also put in the . Leave the port as 22 since that is the default that ssh uses (unless you have ssh using another port on the remote machine)

General Config

Desktop: Here you get you choose the platform the remote machine is running windows? *nix ? and also what graphical enviroment? kde, gnome ?

Display You are allowed to set how big you want the resolution of the remote machine to be on your current machine once you arte logged in.

Advanced Configuration

Here you have the ability to use a network proxy if you are behind a firewall, There are also option that allows you to disable encryption ( why would you ever want to do that) which is not advisable for security reasons.

Here you can enable services like samba share or cups printing between the remote machine and your current machine, in case you want to share files or print something from the remote machine. pretty neat hey

Once all the settings are configured to your taste. Its time to run your connection to the remote machine.

The end result is something similar to this

The remote machine will be running within a windows which can be minimized or resized, or moved to another work space while you continue work on your local machine.

Overall I find Freenx to be very useful and comes in very handy in my day to day work as a system administrator. Its cross platform which means you can even login to a windows machine from your linux box and vice versa.

Hope someone finds this useful

En este post quiero comentar los pasos que seguí para instalar FreeNX en un nuevo servidorcito que estoy preparando en el cual corre openSUSE 11.0, para mí FreeNX es el gran sustituto de VNC, para más información acerca de FreeNX por favor visitar su SITIO OFICIAL o el artículo en WIKIPEDIA.

Lo bueno de FreeNX es que corre sobre el protocolo ssh permitiendo que la información viaje segura, además, trabaja directamente con el servidor X lo que permite que no se necesite ninguna intermediación de una placa gráfica. El servicio lo tenemos que instalar en la máquina a la cual vamos a querer acceder con los cliente, el paquete de instalación viene junto en el DVD de openSUSE 11.0 así que no habrá problemas con eso:

globalserver:/ # zypper install freenx

Una ves instalado el paquete tenemos que configurar el servicio de la siguiente forma:

globalserver:/ # nxsetup --install --setup-nomachine-key --clean

y eso es todo, ya podemos conectarnos con cualquier cliente para FreeNX, yo para Windows utilizo el cliente de NoMachine que lo podemos descargar desde su sitio oficial: http://www.nomachine.com/download.php, para GNU/Linux hay varios clientes también como por ejemplo qtnx que se encuentra disponible en los repositorios.

Si por algún motivo hemos decidido cambiar el puerto del protocolo ssh (configurándolo en /etc/ssh/sshd_config), también lo tenemos que cambiar en la configuración del servicio FreeNX en el archivo /etc/nxserver/node.conf, no hay que olvidarse de reiniciar el servicio sshd y FreeNX para que todo funcione correctamente:

globalserver:/ # service sshd restart
globalserver:/ # nxserver --restart

Gabriel K.

It looks like OpenSSH Keys generated on Debian derived distros (Ubuntu/Voyage etc.) are REALLY bad. I’m currently rolling out OpenSSL key updates as adviced on http://wiki.debian.org/SSLkeys.

One casualty of this update was my NX server using freenx. It just tells me that I can’t be authenticated. In the log /var/log/freenx.log it shows the following:

– NX SERVER START: -c /usr/lib/nx/nxserver – ORIG_COMMAND=
HELLO NXSERVER – Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT – Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: shuerlimann
NX> 102 Password:
NX> 404 ERROR: wrong password or login
NX> 999 Bye

This post talks about the NoMachine NX Server, but gave me the necessary clues: http://lists.kde.org/?l=freenx-knx&m=116542288527396&w=2

The magic command for freenx from http://datakeylive.com
on Ubuntu is

sudo rm /var/lib/nxserver/home/.ssh/known_hosts

This is necessary, as the SSH host key has been updated… Well, a more informative error message would’ve been nice, but I’m thankfull to the guys who produce freenx, anyway;-)

Muchas veces hemos querido acceder a nuestro pc desde otra parte, ya sea para poder obtener alguna información o para trabajar con nuestros programas favoritos, los cuales ya estan instalados y configurados en nuestro computador. Bueno, eso es posible con con FreeNX , esta aplicación nos permite acceder de forma gráfica a nuestro computador y a diferencia de otras aplicaciones, esta no toma el control de la sesión que se encuentra actualmente en uso, sino que crea una nueva sesión , así el usuario que está utilizando el computador en ese momento no se será interrumpido.

Para instalar FreeNX necesitamos 3 archivos, los cuales son :

1. NxClient
2. NxNode
3. NxServer

Puedes bajar las últimas versiones de la página oficial AQUí

Ahora para instalarlos, lo haremos de la siguiente manera, es importante mantener el orden de instalación:

sudo dpkg -i nxclient_xxxx.deb

sudo dpkg -i nxnode_xxxx.deb

sudo dpkg -i nxserver_xxxxx.deb

Donde se reemplazan las xxx por la versión del paquete.

y listo …

Ahora en el menu de Aplicaciones -> Internet nos aparecerá “NX Client for Linux”, dentro de este menú podremos encontrar un asistente de instalación el cual nos guía para hacer la conexión.

Luego de esto ya podemos conectarnos remotamente a nuestro pc.

Para que esto funcione es necesario instalar el servidor FreeNX en la máquina a la cual nos queremos conectar.

Y eso sería

Saludos.

NoMachine NX is a Terminal Server and remote access solution based on a comprising set of enterprise class open source technologies. NX makes it possible to run any graphical application on any operating system across any network connection at incredible speed. FreeNX application/thin-client server is based on NoMachine’s NX technology. It can operate remote X11 sessions over 56k modem dialup links or anything better. FreeNX package contains a free (GPL) implementation of the nxserver component. The following workshop describes the FreeNX installation on a Mandriva 2008 Free server. Additionally it explains how to access it using a Windows XP and an OpenSuse 10.3 client.

more…

Fuente: https://help.ubuntu.com/community/FreeNX

FreeNX

FreeNX is a system that allows you to access your desktop from another machine over the internet. You can use this to login graphically to your desktop from a remote location. One example of its use would be to have a FreeNX server set up on your home computer, and graphically logging in to the home computer from your work computer, using a FreeNX client.

Terminology

The Server is the computer you want to connect to. This is the computer where the FreeNX server will need to be installed. The name of the Ubuntu package providing the server is “freenx”. For the example used here, the home computer is the server.

The Client is the computer from which you want to be able to access the Server. The name of the Ubuntu package providing the client is “nxclient”. For the example used here, the work computer is the client.

Installing the FreeNX server

We will be installing the FreeNX server on the Server machine, i.e., the machine that you want to access remotely. In the stated example, this is your computer that is at home. Open your aptitude sources list and append the two lines for the repository.

gksudo gedit /etc/apt/sources.list

For Ubuntu 5.10 and 6.06, they are:

deb http://free.linux.hp.com/~brett/seveas/freenx dapper-seveas freenx
deb-src http://free.linux.hp.com/~brett/seveas/freenx dapper-seveas freenx

For Ubuntu 7.04, they are:

deb http://free.linux.hp.com/~brett/seveas/freenx feisty-seveas freenx
deb-src http://free.linux.hp.com/~brett/seveas/freenx feisty-seveas freenx

(For future versions, visit the FreeNX repository site to check for other repositories.)

Save and then close.

Add the GPG key:

wget http://free.linux.hp.com/~brett/seveas/freenx/seveas.gpg -O- | sudo apt-key add -

Then Update Apt

sudo apt-get update

After you add the repository, then install the freenx package.

sudo aptitude install freenx

(Using aptitude to install extra needed packages) [Note: You can manually perform the setup with: sudo nxsetup --install --setup-nomachine-key]

During installation you will be given the option to select NoMachine keys, or custom keys. It is best to select NoMachine keys. For the paranoid: there is absolutely NO added security risk involved in using the default keys. Read an SSL primer if you want to know the details about why this is the case

(I am not so sure about that absolutely NO added security risk; anyway, official word seems to be that this is a non-issue: see http://mail.kde.org/pipermail/freenx-knx/2005-August/001900.html )

On the server, add your user to nxserver

sudo nxserver --adduser <username>
sudo nxserver --passwd <username>
sudo nxserver --restart

[Note: I don't know if this is still needed, but it helps - JeremySchroeder]

Configuring SSH

By default, nxserver uses port 22 for communicating over SSH. On some machines or networks, port 22 may be blocked. For example, some providers block port 22. To make the SSH server listen on port 8888, you can do the following:

Edit the file /etc/ssh/sshd_config

gksudo gedit /etc/ssh/sshd_config

Find

Port 22

and change it to

Port 8888

You then need to restart SSHD. Try

/etc/init.d/ssh restart

Edit the file /etc/nxserver/node.conf

gksudo gedit /etc/nxserver/node.conf

Find

# The port number where local 'sshd' is listening.
#SSHD_PORT=22

and change it to:

# The port number where local 'sshd' is listening.
SSHD_PORT=8888

That is, change the port number to the one that sshd is listening to, and uncomment the line.

Installing the NX Client

sudo aptitude install nxclient

You should be able to access your Ubuntu box from any Windows or Linux box using the free client from NoMachine’s website. You can also embed your NX Server in a webpage by installing the Nomachine Web Companion and the Apache webserver.

Note on nomachine web site there is new version off nxclient version 2.0 and it don’t work with freenx so you should better use nxclient from Seveas’ Packages!

Now you can execute the installed client using the following command:

/usr/NX/bin/nxclient &

Or by looking it up in the menu

This will start the NX client in a GUI, and step you through getting connected to the FreeNX server, and you will be on your way! [Note: If you are behind a firewall you may need to enable SSL encryption under the Advanced configuration tab - JeremySchroeder]

Useful Resource for installing client on 64-bit Ubuntu

Miscellany

FreeNX on PowerPC

There are no precompiled binaries of FreeNX on this platform, so FreeNX have to be compiled from source. Sources for breezy can be found at SeveasPackages

These steps will build FreeNX from source:

1. Create a directory to hold the FreeNX source, and cd into it.

   mkdir freenxSource; cd freenxSource

2. Build the freenx pacakges and install related packages.

   sudo apt-get build-dep nx freenx
   apt-get -b source nx freenx

   This will download the souce tarballs and build the freenx packages (*.deb) in the current directory.

3. Install the FreeNX packages.

   sudo dpkg -i *.deb

4. If dpkg complains about missing packages, let apt fix it

   sudo apt-get -f install
   sudo dpkg -i *.deb

FreeNX on 64bit

FreeNX is not 64-bit safe, so you will have to build a 32-bit chroot.

How to start/stop FreeNX

The FreeNX server is not a service but uses ssh. The following command will stop the FreeNX program from accepting connections.

sudo nxserver --stop

(Replace –stop by –start for starting it again)

Using custom SSH keys

This is NOT supported by the FreeNX developers – only do this if you have no other option

1. Generate the DSA private-public key pair.

    ssh-keygen -t dsa

   By default this key is places in ~/.ssh/id-dsa. You can leave the passphrase empty, this will not pose a security risk.

2. Install the public key in the FreeNX serving machine. The key should be placed in the file authorized_keys2 in the .ssh dir of the user named nx.

   cat ~/.ssh/id_dsa.pub | sudo -u nx tee -a ~nx/.ssh/authorized_keys2

3. Install the private key in the NX client software. When creating a session, press the button labeled “Key” and select your new key in the window that pops up.

References

• FreeNX on Wikipedia
• Seveas’ Packages FreeNX repository
• Ubuntu Forums HowTo FreeNx How to remote desktop using SSH and FreeNX – OpenGL Seveas Repositories

Instalar FreeNX. Control remoto Ubuntu

31 Enero, 2007

Ads by Google
Desarrollo rapido REDHAT
Arquitectura WEB 2.0, AJAX, SOA de
forma estandard y facil.
www.TransTOOLs.com/Expand REDHAT
Reparacion PC Impresoras
Mantenimiento Empresas Cyber, Redes
Cableado AMP Siemon Abonos, Insumos
www.mymhard.com.ar

Está el radmin para windows, que a mi me parece una magnífica herramienta para control remoto de windows. (Teniendo un subdominio, si no tienes ip fija y abriendo los puertos del router). Se conecta por el puerto 4899 y es configurable. Algunos antivirus lo identifican como peligroso o potencialmente peligroso, pues hay hackers que utilizan su código. El sinónimo al radmin en linux es el vnc, una herramienta gratuita, pero para el tema de puertos, hay que abrir más de uno.

Para Ubuntu estuve buscando herramientas, me encontré con esta, también maravillosa herramienta, más parecida al terminal server, pues ejecuta una sesión en escritorio remoto, como dice esta página:

“Además al contrario de VNC no se trata de compartir una conexión, sino de crear una nueva sesión que se puede dejar abierta y retomarla otra vez.”

Tutorial en pdf

para instalarlo en Ubuntu:

me copio el enlace que actualmente está roto: www.guia-ubuntu.org/index.php/FreeNX

FreeNX es un software que permite acceder remotamente y de forma gráfica a nuestro PC. Al contrario que VNC, en vez de usar el protocolo RFB (Remote Frame Bufer), FreeNX usa un nuevo esquema de compresión del entorno X-Window, que permite controlar un escritorio remoto incluso con una conexión de módem de 56 Kbps. El tráfico del servidor X se comprime y transmite por SSL usando una conexión SSH que puede ser resumida automáticamente en caso de ser interrumpida.

Además tiene la ventaja de que el programa guarda en caché los elementos gráficos ya mostrados (menús, iconos, decoraciones de ventanas…) por lo que en lugar de hacer una segunda petición para mostrar esos elementos, se muestran desde local.

[editar]

Instalar FreeNX (servidor)

Para instalar FreeNX en Ubuntu debemos añadir el repositorio necesario:

$ sudo gedit /etc/apt/sources.list

Al final de dicho archivo añadimos la siguiente línea:

Para Dapper:

deb http://mirror.ubuntulinux.nl/ dapper-seveas custom extras freenx java seveas-meta all

Para Edgy

deb http://mirror.ubuntulinux.nl/ edgy-seveas custom extras freenx java seveas-meta all

Instalamos la claves de autenticación:

$ sudo gpg –keyserver subkeys.pgp.net –recv-keys 1135D466 $ sudo gpg –export –armor 1135D466 | sudo apt-key add -

Instalamos el servidor:

$ sudo apt-get update $ sudo apt-get install freenx

Configuración del Servidor:

Si queremos usar las no-machine keys ejecutamos:

$ sudo nxsetup –install –setup-nomachine-key –clean –purge

Si por el contrario, preferimos usar nuestras propias claves (mucho más seguro, pero con el inconveniente de que tenemos que llevarnos las claves haya donde vayamos):

$ sudo nxsetup –install –clean

NX necesita por defecto tener el demonio sshd escuchando el el puerto 22 y con las claves públicas activadas. Para ello debemos comprobar que en el fichero /etc/ssh/sshd_config tengamos las siguientes líneas:

Port 22 PubkeyAuthentication yes

Si por el contrario preferimos tener ssh en otro puerto, debemos indicárselo a NX. Para ello editamos el siguiente fichero:

$ sudo gedit /etc/nxserver/node.conf

Editamos la línea:

#SSHD_PORT=22

Y ponemos el puerto que queramos. Por ejemplo 1234:

SSHD_PORT=1234

Firewall: NX utiliza el puerto del ssh y además el puerto 5000, por lo que si disponemos de firewall, tendremos que abrir dichos puertos.

Instalar el cliente NX
Para instalar el cliente abrimos un terminal y escribimos:

$ sudo apt-get install nxclient

Lo podremos localizar en el menú Aplicaciones >> Internet >> NX Client for Linux >> NX Client for Linux.

Si no aparece en el menú, reinstala nxclient desde Synaptic, y listo.

Ads by Google
Desarrollo rapido REDHAT
Arquitectura WEB 2.0, AJAX, SOA de forma estandard y facil.
www.TransTOOLs.com/Expand REDHAT
Notebooks
¡Las marcas más vendidas con excelentes precios!
www.MercadoLibre.com.ar
Placas Pcmcia de Notebook
Todas las opciones en placas Pcmcia buscalas en nuestra web. Ofertas!
www.distrinotebook.com
Escritorio Remoto
Acceso seguro a la Computadora sin instalación. Pruébelo gratis!
www.LogMeIn.com

http://www.gpltarragona.org/index.php?p=316

Administración gráfica remota con FreeNX
Novembre 6, 2004 a les 12:26 am | Categoria Internet |

FreeNX es una nueva aplicación cliente/servidor que permite acceder al escritorio GNU/Linux de forma remota al estilo de VNC pero con un método muchísimo más eficiente. VNC traspasa imagenes comprimidas del escritorio remoto, sin embargo FreeNX baja un nivel más y comprime directamente el protocolo de las X, de esta forma se consigue un rendimiento espectacular.

El programa ha sido desarrollado por la empresa NoMachine y ha sido liberado bajo la licencia GPL.

Lo he probado en diversos escenarios y en todos me ha sorprendido:
Servidor GNU/Linux en LAN a 100 Mbps: Es posible trabajar con la máquina remota con total comodidad
Servidor GNU/Linux en ADSL 512Kbps/128Kbps: El rendimiento es inferior al anterior pero se sigue podiendo trabajar comodamente, supera con creces VNC.

Se debe tener en cuenta que FreeNX trabaja utilizando el servicio SSH y por tanto toda la identificación y la comunicación es encriptada, con VNC no lo tenemos de forma nativa y hay que hacer túneles SSH lo que hace inusable el acceso en redes lentas como Internet.

El único posible inconveniente de FreeNX es que no permite acceder al escritorio actual del usuario que este trabajando fisicamente con el servidor (con VNC se puede conseguir usando gemsvnc, x11vnc o vino), pero como ventajas podemos acceder al escritorio de cualquier usuario y suspender la aplicación de forma que en una siguiente conexión recuperemos el estado del escritorio tal y como lo dejamos.

En definitiva estoy encantado con el programa dado que con mi conexión ADSL solo tengo 128 Kbps de subida y el servidor VNC no era muy usable, sin embargo con FreeNX puedo acceder remotamente a mi escritorio (incluso a pantalla completa) sin problemas y con poco retardo.

Para instalar en Ubuntu:
Añadir a “/etc/apt/sources.list”:

deb http://www.kalyxo.org/debian/ experimental main
Actualizar el listado de aplicaciones: “aptitude update”
Es importante disponer ya de un servidor SSH activo, en Ubuntu se instala con “aptitude install openssh-server” y se guardan los archivos de configuración en “/etc/sshd/”. La configuración por defecto suele funcionar y automáticamente en la instalación se activará el servidor. Para probar su funcionamiento podemos usar “ssh usuario@localhost” o “ssh usuario@ip_maquina” si lo hacemos remotamente. Es importante que el firewall (en caso de disponer de uno) del servidor tenga abierto el puerto 22 para poder establecer conexiones SSH y en consecuencia, FreeNX.
Instalar el servidor “aptitude install freenx” y el cliente “aptitude install nxclient” en diferentes máquinas (existen clientes para MS Windows en la página de NoMachine)
Comentar la línea que añadimos a “/etc/apt/sources.list”, es importante no hacer una actualización del sistema (aptitude dist-upgrade/upgrade) con este repositorio activado ya que se nos instalarán programas que no corresponden a Ubuntu. Este repositorio solo lo usamos para instalar FreeNX, nada más.
Actualizar de nuevo el listado de aplicaciones con “aptitude update”
Configurar el servidor, tenemos 2 opciones:
Utilizar la clave SSH por defecto de NX, con esto no tendremos que facilitar ninguna clave a nuestros clientes (aunque seguirá siendo necesario el login/password), esta opción es menos segura ya que estamos permitiendo a cualquiera poder conectarse al servidor NX aunque después se encontrará con la barrera del login/password, sin embargo resulta más sencillo de configurar el acceso de los clientes. Para usar esta vía: “nxsetup –setup-nomachine-key”.
Generar una clave SSH nueva, esta tendrá que ser repartida a todos los clientes que deseen conectarse. Para usar esta vía: “nxsetup”. La clave se guarda en el directorio del usuario “nx”, en Ubuntu será en “/home/.nx/.ssh/”, debemos copiarla (”client.id_dsa.key”) a “/usr/NX/share” (o el directorio donde hayamos instalado en MS Windows) de todos los clientes (si ya existe una, reemplazarla o renombrarla).
A partir de ahora el servicio NX se activará automaticamente en cada arranque, para pararlo se usa “nxserver –stop” y para volverlo a poner en marcha “nxserver –start”.

Para acceder con el cliente:
Ejecutamos “nxclient” o “nxclient –wizard”. Pulsamos Next.
Le damos un nombre a la sesión, indicamos la máquina a la que queremos conectarnos y el tipo de conexión que tenemos (ADSL, LAN…). Pulsamos Next.
Seleccionamos que la conexión será a un UNIX con GNOME y especificamos la resolución con la que queremos que arranque, por ejemplo 1024×768. Activamos la encriptación SSL, así solo es necario que tengamos acceso al puerto 22 de la máquina remota. Pulsamos Next.
Dejamos marcado la creación de un icono en el escritorio y pulsamos Finish.
Ahora ya podemos conectarnos a la máquina remota indicando nuestro login y password

Autor: marble
4 comentaris »

Suscripció RSS als comentaris de la entrada.

primer de tot dir que si no es una molestia caldria actualitzar la linea del repositori ya que lan canviat.

deb http://archive.kalyxo.org/kalyxo/ experimental main
o
ftp http://archive.kalyxo.org/kalyxo/ experimental main

Tambe dir que potser l’error que em dona es una xorrada, pero com no se com solucionario deixo el comentari a veure si algu mo pot explicar. Gracies.

Quan intento instalar el FreeNx em diu que no es satisfan les dependencias pel nxagent i el nxproxy, alhora quan intento instalar el nxagent em dona l’error de que tambe fallen les dependencias i aixin fins arribar a les llibreries libnxcomp0. Aquestes em diuen que depenen aixo:
libnxcomp0: Depende: libpng12-0 (>= 1.2.7) pero está instalado 1.2.5.0-7ubuntu1.

Que tindria que fer?

Comentari per Anònim — Desembre 3, 2004 #

Baixa els debs d’aqui, aquests son els que jo vaig utilitzar i en principi funcionen. Per instalar-ho:

dpkg -i *.deb

El repositori es per Debian, no per Ubuntu… per això ara hi han tants problemes.

Comentari per Anònim — Desembre 4, 2004 #

gracies ara no puc pero ho provare

Comentari per Anònim — Desembre 4, 2004 #

Jo ho vaig provar ahir. Primer em va donar una errada de dependències, però el gestor de paquets Synaptics ho va sol·lucionar.

Ara estic escrivint des d’un P150 amb debian woody i nxclient de www.nomachine.com. El nxserver està instal·lat en una ubuntu 4.10.

Gràcies.

Santi

FreeNX

De Guía Ubuntu

Saltar a navegación, búsqueda

FreeNX es un software que permite acceder remotamente y de forma gráfica a nuestro PC. Al contrario que VNC, en vez de usar el protocolo RFB (Remote Frame Bufer), FreeNX usa un nuevo esquema de compresión del entorno X-Window, que permite controlar un escritorio remoto incluso con una conexión de módem de 56 Kbps. El tráfico del servidor X se comprime y transmite por SSL usando una conexión SSH que puede ser resumida automáticamente en caso de ser interrumpida.

Además tiene la ventaja de que el programa guarda en caché los elementos gráficos ya mostrados (menús, iconos, decoraciones de ventanas…) por lo que en lugar de hacer una segunda petición para mostrar esos elementos, se muestran desde local.

[editar]

Instalar FreeNX (servidor)

Para instalar FreeNX en Ubuntu debemos añadir el repositorio necesario:

$ sudo gedit /etc/apt/sources.list

Al final de dicho archivo añadimos la siguiente línea:

Para Dapper:

deb http://mirror.ubuntulinux.nl/ dapper-seveas custom extras freenx java seveas-meta all

Para Edgy

deb http://mirror.ubuntulinux.nl/ edgy-seveas custom extras freenx java seveas-meta all

Para Feisty:

deb http://mirror.ubuntulinux.nl/ feisty-seveas custom extras freenx java seveas-meta all

Instalamos la claves de autenticación:

$ sudo gpg --keyserver subkeys.pgp.net --recv-keys 1135D466
$ sudo gpg --export --armor 1135D466 | sudo apt-key add -

Instalamos el servidor:

$ sudo apt-get update
$ sudo apt-get install freenx

Configuración del Servidor:

Si queremos usar las no-machine keys ejecutamos:

$ sudo nxsetup --install --setup-nomachine-key --clean --purge

Si por el contrario, preferimos usar nuestras propias claves (mucho más seguro, pero con el inconveniente de que tenemos que llevarnos las claves haya donde vayamos):

$ sudo nxsetup --install --clean

NX necesita por defecto tener el demonio sshd escuchando el el puerto 22 y con las claves públicas activadas. Para ello debemos comprobar que en el fichero /etc/ssh/sshd_config tengamos las siguientes líneas:

Port 22
PubkeyAuthentication yes

Si por el contrario preferimos tener ssh en otro puerto, debemos indicárselo a NX. Para ello editamos el siguiente fichero:

$ sudo gedit /etc/nxserver/node.conf

Editamos la línea:

#SSHD_PORT=22

Y ponemos el puerto que queramos. Por ejemplo 1234:

SSHD_PORT=1234

Firewall: NX utiliza el puerto del ssh y además el puerto 5000, por lo que si disponemos de firewall, tendremos que abrir dichos puertos.

[editar]

Instalar el cliente NX

Para instalar el cliente abrimos un terminal y escribimos:

$ sudo apt-get install nxclient

Lo podremos localizar en el menú Aplicaciones >> Internet >> NX Client for Linux >> NX Client for Linux.

Si no aparece en el menú, reinstala nxclient desde Synaptic, y listo.

Obtenido de “http://www.guia-ubuntu.org/index.php?title=FreeNX“

Categorías: Administración del sistema | Escritorios remotos

Now that most of the installations are done, would we do the same decisions and processes again? Would we make the same choices?

Overall we are quite happy with Concorde and our installations…

Hardware & System config

In the ideal world, how about a Dual Processor, Dual Core Blade Server with lots of RAM and a huge disk array of big and ultra fast SCSI disks in a SAN configuration. Well the choice of our used x345 is actually a good compromise, good value, nice RAID adapter and despite being a flat rack model, the Server has still room for 6 hot-pluggable SCSI 320 disks.

The two array, RAID 1 (for Linux) and RAID 10 configuration for “/var” and the virtual machines works fine. The chosen stripe size of 64kbyte of the RAID adapter config seems to have worked out as well. We haven’t tested the performance, but until proof of the contrary as well as a good gut feeling, the choice was sound.

The stripe size of the RAID unit seems to me like one of the last mysterious settings of big server environments.  Very little information can be found.  As an example, at the time of this article, the stripe size is only mentioned in one paragraph of the German wikipedia article on RAID, the english RAID article omits the stripe size.

In our understanding however, the stripe size is having a big impact on overall performance of a system as it looks like the classic bottleneck setting. And it also seems that Domino is preferring rather larger stripe size configs, and we assume so does VMware. (see here, and here, and here)

The IBM ServeRAID (really an Adaptect) gives 4kb as default (or 8kb, I don’t exatly remember).  Modern adapters suggest 128kb, which is much more logical.  Our rule of thumb is rather bigger than smaller, if too big performance might suffer a bit, make the size too small, and it really could hurt (as in our first trials).   If anybody disagrees, please feel free to comment and explain.

Ubuntu

read installation article

We chose the Ubuntu 6.06 because of LTS, long term support that is. Although 6.10 is certainly very nice. Some little but effective things have been improved. Try to remove the games from the Ubuntu 6.06 desktop. Exactly. It wants to remove the entire Ubuntu Gnome Desktop. Under 6.10, removing the games is a child’s play . OK games on a server a just unused programmes that don’t do anything, unless you play. It just seems bizarr to have games on a server, doesn’t it?

VMware Server

We had many reactions such as “Doesn’t that impact on the performance?” Well, it probably does, but it’s a fast machine, a good RAID system with fast disks. And it seems, that we have done the right config choices of the RAID system and the OS / VMware settings. Performance is still very good. VMware ESX is certainly better, but also mighty expensive and for our environment it just would be over the top.

FreeNX

Yes, FreeNX is a curious mix of open source (the FreeNX server) and closed source (the client from NoMachine). But the seveas ubuntu packages work and FreeNX is really a pleasure to work on (and with). So much better than VNC.

Domino

Not a question of choice, Domino is currently the engine for the member system and directory of the association. 7.0.2 for Linux is a lot less choosy then previous 6.X.X versions regarding Java versions and some libraries. So far it is very reliable and performance is good.

Yes, we did the dirty trick and did a clean re-install using the same nominations (domains, server names, users). The previous installations (and certifications / keys) were the result of years of updates & upgrades, migratrions and installations originating from the first trials in 1993/94. The certifications for example expired once after just 2 years due to a bug of 4.x. Since then the public keys never were quite right. That meant, no enforced rule of encryption, which makes migration much easier. So this time, no old IDs were used or (re-)certified to create the new Domino infrastructure.

A very nice collection of performance tips for  Domino can be found on nfstools.com.  (Although we would politely disagree with the size stripe suggestion of only 16kb, see above)

Now the biggie, because Lotus Domino is quite choosy regarding libraries and Java. For once the Ubuntu help pages didn’t help me. Try to find the compat RPMs, not easy. And then I found a couple of sites which seemed to have succeeded without those RPMs. Specifically this thread in the forum was promising…

As detailed in the previous post, I created a new drive and partition for the VM. The new partition is for the /local directory. I honestly don’t know if keeping the notesdata files of the VM on that partition has any performance advantages like it may have when the disk is a physical one… In this case, the only reason is the need for larger capacity than the 8GB of the pre-configured Ubuntu 6.06 appliance.

As mentioned in the Ubuntu forum as well as on the notes.net one, installing GAWK might help smoothing some issues. And if not, no harm done. So we installed it via the Synaptic Package Manager.

Domino needs a user and a group under Linux which has no root rights. In the forum, you’ll find the choice of “domino” as the name for both, out of habit I prefer “notes” as user and group name. It also is the default choice for the installation options. Does this have any other consequences? No, do as you please.

The installation went without a hitch, here is the final Domino message:

The Domino Server installed successfully.

Please manually configure the Domino Server as follows:
1) Login as the appropriate UNIX user: ‘notes’;
2) Change to the data directory using the command: ‘cd /local/notesdata’;
3) Configure the server using the command: ‘/opt/ibm/lotus/bin/server’
To configure the server remotely, the remote server setup tool is required and you can use the command:
‘/opt/ibm/lotus/bin/server -listen’
After issuing this command, additional instructions will appear for remote server setup…

In order to recover an “old” server config of Lotus Domino with a fresh installation, there are different ways:

1. Of course, updating the server by simply installing a complete version over an existing one usually works absolutely fine with Domino.  The update replaces the old files and when restarting the server, the design of the databases will be automatically refreshed.
2. In case you want an absolute clean install, you can use the old ID files (admin, cert, server etc) to freshly install everything.  If you haven’t got the “old” Public Names & Address Book (Domino Directory), don’t forget that although your old certifications will be integrated into the new setup, but the old “users” aren’t.
3. The dirty way to reinstall is to do a clean install, create new certifications using the old naming conventions (for the Notes domain, server nam, admin name etc).

• If you have go the old files, including the ID-files and important databases such as the Public NAB and if possible the certification related databases, simply copy everything into the freshly installed directory (/notesdata/) and restart the server.  Should work fine.  Becareful not to mix up new and old IDs.

• You haven’t all necessry files, recreate or recertify the users.  All old databases can be reintegrated without a big trouble as long as all naming conventions are similar and no encryption has been used. Encrypted email for example can only be read with the right user ID. To “un-encrypt” local databases, you have to use the old user ID (or recertify the old one).  The dirty re-install is a last resort, when lot’s of backup systems have failed or for any reason were insufficient to recover old Lotus installations.  Large Domino implementations should avoid at any cost ever reaching such a desperate stage, because many of individual manipulations have to take place and some data might be lost forever.

Even without the compat RPMs Domino 7.0.2  seems to run fine on Ubuntu 6.06  desktop (dapper drake) for the last couple of days.  I didn’t touch the Ubuntu JVM -  which until Domino 6.5 was a very delicate issue, because Domino liked only specific Java-flavours such as the IBM Java 1.4.1 (1.3.1).  So far so good, no problems have occured yet.  In fact I am surprised about how few manipulation I had to do.

OK, now the groundwork for a Ubuntu-based VMware system is done. Now we install the workhorse. So rather than creating a new Ubuntu 6.06 desktop virtual machine, VMware offers us a marketplace of free pre-configured “appliances”, where, of course, a Ubuntu 6.06 VM can be found…

Download and unzip it, copy it to the directory used for virtual machines (/var/lib/vmware/Virtual Machines/).

Then open it in the VMware Server Console (Applications – System Tools – VMware Server Console). There you edit the machine and configure it to your needs. In our case, we add more RAM, add a processor and add a disk, because Lotus Domino will be asking for a bit (5 mail files and the directory which can become quite sizable when incl all the indexes.). Also we chose NAT which worked immediately, contrary to the bridge solution. Don’t know why, but NAT works and we don’t see any disadvantage using NAT.

Because we added a processor to the VM, it makes sense to install the ubuntu SMP Kernels (header & image) similarly to the host system. Another thing which quickly got our attention was the screensaver. Don’t want that on a server. Screen goes dark or stays active. And of course we immediately updated what was updateable.

Next is the installation / updating of the VMware tools in the VM / guest system. That is easy, again just follow the excellent “VMware tools” instructions of Ubuntu.com. Just remember to install the 686 SMP Kernels (in case you need/want them) before running the VMware Tools installation.

In order to use the added virtual disk we need to create a partition in our VM. An easy way is to install <gparted> via the Synaptic Package Manager. Here is a blog explaining the resizing of a partition using gparted. After the installation you can find gparted in the System – Administration menu as the Gnome Partition Manager.

Using the Disks tool (System – Administration – Disks), we create a new folder in the new partition called “local”. That’s where Domino likes to install all the “notesdata” files.

Again we installed FreeNX. Yes, VMware comes with remote access tools, but we like FreeNX, it works and we are familiar with it. (read post on Ubuntu FreeNX installation).

Once FreeNX is running, nearly everything can be done remotely. That may not be important when you are installing a machine at your home, but remote admin of a server is nice and very helpful. Also I try to spend as little time as possible in server rooms, which are cold, dry and loud. So follow the FreeNX instructions on ubuntu.com, which includes adding the seveas repositories.

Just copy the sources from the web pages and paste them into the synaptic package manager.

I love the terminal console of the Ubuntu Gnome desktop. Copy the command line from an install instructions page on the web. Paste it into the console and >enter<. So that’s how I quickly installed the GPG-Keys necessary for the Seveas repositories.

The FreeNX Ubuntu page also recommends to change the default SSH port from 22 to 8888, which I did as well. Ubuntu by default is NOT root, although those changes are better done using root. So either use the terminal console with sudo and an editor such as “vi” or use the Gnome UI, which again is simple. Alt-F2 opens a command line window, type “gksudo nautilus” and the File Manager is run as root. Then select the config text files as described in the instructions and right mouse click “open with text editor”, do the changes and save the files. Again when copying the command line to restart the SSHD I used sudo, don’t know if it was necessary.

So that’s it, FreeNX is running, all you need now is to install a NXclient on your Linux/Mac/Windows computer, configure the connection and … connect. Don’t forget to set the port to 8888. If it is not working check the firewalls and routers between your machine and the “server”, if the port 8888 is blocked. Enjoy the FreeNX experience.

So here we are, the nth installation. I downloaded 6.06 again, burned another copy and finally the installation went without a hitch.

The only important question during the installation is how to partition the system.

I chose a classic config for the OS: All on RAID1 with a swap partition 1.5 times the size of RAM, so in my case 6GB.

The only unusual config due to our applications is to mount /var on the RAID 10, because the VMware machines are typically installed in /var/lib/vmware/…

Then we updatedthe system and installed multiprocessor support…

Updating

First things first, updating Ubuntu as soon as the machine has Internet access. As this is a server and there is no DHCP in the DMZ, I quickly edited the IP config, IP number, Gateway and DNS servers. BTW, when talking to Andy he recommended OpenDNS. Great idea, being able to have “your” DNS server wherever your omputer is, although I haven’t had time yet to check it out.

SMP

Next was to install the SMP Kernel for multiple processor support. Using the desktop Ubuntu, you start the Synaptic Package Manager (System-Administration-…), search for SMP and then select the latest SMP Ubuntu headers and images.