Code: Select all
export DISPLAY=192.168.1.1:0
mozilla &Code: Select all
xhost +The main issues with plain X protocol are bandwidth and security. NX solves both issues. VNC can tunnel through ssh for security (what NX does).opensas wrote:I thought that X11 was inherently net enabled. So I guess that all the products you've been recommending me are just improvements to X11
You can set up xdm (or kdm or gdm) on the Linux server and connect to it with cygwin X but it is insecure and high bandwidth. Go ahead and try it for kicks but in the end you will probably want to use NX or VNC.opensas wrote:First of all I'd like to learn how to set a linux box an X11 server, in order to access it from a windows client (there's an opensource source win32 X11 client based on Cygwin, I think)
You are correct but nomachine has GPL'd parts of NX so you can use nxclient and nxserver-freenx ebuilds without actually paying anything (nxserver-freenx is all GPL but the nxclient is not).opensas wrote:I've been surfing around, and I think that nx is commercial, while tightvnc is free (am I wrong)
Code: Select all
1. Iniciar XWindow por el metodo elegido (X o startx).
2. Obtener nuestra direccion IP utilizando ifconfig. Este sera el valor que usaremos para la variable DISPLAY en el sistema remoto.
3. desde un shell (sea de otra consola, o desde una xterm en el XWindow recien cargado) conectarnos por ssh, telnet o el metodo que sea a otro sistema GNU/Linux o U*nix, tambien, ya que el protocolo X es comun a todos.
4. Obtener la IP del sistema remoto (otra vez ifconfig).
5. Localmente, habilitar dicha IP con xhost +IP.
6. Remotamente, ejecutar "export DISPLAY=ip_nuestra:0". ip_nuestra es el valor obtenido en el paso (2).
7. Ultimo paso, ejecutar el cliente X en cuestion, claro esta desde el sistema remoto.
Code: Select all
tux root # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:8C:4C:88
inet addr:192.168.67.128 Bcast:192.168.67.255 Mask:255.255.255.0
...
tux root # ssh larry
Password:
Last login: Mon May 23 23:48:49 2005 from 192.168.67.128
larry root # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:B0:F7:AE
inet addr:192.168.67.132 Bcast:192.168.67.255 Mask:255.255.255.0
Code: Select all
tux root # xhost +
access control disabled, clients can connect from any host
Code: Select all
larry root # export DISPLAY=192.168.67.128:0
Code: Select all
twm .display 192.168.67.128:0
Code: Select all
tux root # uname -a
Linux tux 2.6.11-gentoo-r8 #1 Sun May 15 20:32:34 ART 2005 i686 AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux
tux root # eix xorg-x11
* x11-base/xorg-x11
Available versions: 6.8.2-r1 [M]6.8.2-r2 [M]6.8.99.3 [M]6.8.99.5
Installed: 6.8.2-r1
Why startx? I thought an X server was already running on tux (that's why you ran xhost +).opensas wrote:and then at larryCode: Select all
tux root # xhost + access control disabled, clients can connect from any host
If, at larry, I execute "startx"Code: Select all
larry root # export DISPLAY=192.168.67.128:0
Are you sure that the X server on tux is configured to listen on TCP/IP? It is disabled by default. If you use startx then edit that and remove "-nolisten tcp" from the X server arguments. You may want to look at the man pages for startx and Xserver.Also tried with "xcalc" and I got
Error: Can't open display 192.168.67.128:0
Am I missing something???
Code: Select all
tux root # which startx
/usr/bin/startxCode: Select all
bash-2.0b# xhost +
access control disabled, client can connect from any host
Code: Select all
bash-2.0b# ssh tux
Password:
tux root # export DISPLAY=192.168.132:0
Code: Select all
tux root # konqueror &
Code: Select all
tux root # konqueror: cannot connect to X server 192.168.167.132:0
Code: Select all
tux root # export DISPLAY=192.168.132:0
tux root # xcalc
Error: Can't open display: 192.168.67.132:0
Code: Select all
tux root # useradd guest
tux root # passwd guest
tux root # /etc/init.d/sshd start
tux root # /usr/NX/bin/nxserver --start
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 '3100'.
Info: Connecting to remote host '192.168.67.128:5000'.
Info: Aborting procedure due to signal '15'.
Code: Select all
# Free implementation of nxserver components
#
# To use nxserver add the user "nx"
# and use nxserver as default shell.
#
# Also make sure that hostkey based authentification works.
Code: Select all
tux portage # usermod -G root,wheel,adm guest
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 '2332'.
Info: Waiting for connection from any host on port '2006'.
Info: Accepted connection from '127.0.0.1' on port '2088'.
Info: Connection with remote proxy established.
Error: Remote NX proxy closed the connection.
Error: Please check your authorization credentials.
When I first tried nxclient I got the above error. After some searching I found out about the nxsetup command that comes with freenx.NX> 203 NXSSH running with pid: 8406
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.0.254 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.
Code: Select all
nxsetup --install --setup-nomachine-keyYou need windows apps? If you're using win4lin or vmware then you're still using windows. You might as well use Terminal Server too.opensas wrote:Now I'll be struggling with win4lin and vmware, 'cause in fact I'm looking for something to replace Micro$oft Terminal Server![]()
Qemu is open source and similar to vmware but the performance is not very good. The qemu developer maintains a proprietary accelerator module but I haven't tried it. Wine is the only other thing I can think of if you need windows apps.opensas wrote:If you know of any open source alternative to VmWare (plex86 is not very healthy nowdays) just let me know