Displaying X remotely ?

[Nailz]

Ok, the basics: XWindows is comprised of an Xserver AND and Xclient. If you're in front of your linux box and you start xwindows, then you're Xserver is serving your local client. Correct so far?

Now, if I have a linux box and want to display X11 on another workstation, whether its another Linux box or Windows (running Exceed or something), where do I set the parameters (and what are they)?

I've heard that I need XDM running on the linux box, but don't know more than that. Where can I find more info?

Thanks

[sym]

One option is also to use VNC for remote desktop connections.

[Hena]

You can use ssh to give tunnel to x. Atleast windows with xserver can show xapps through ssh.

[Nailz]

Thanks guys... I'm familar w/ VNC, but I'd rather take over the entire X session (which IS possible) rather than just view an individual x-application.

The reason for this is 1) lack of a spare monitor/kb/mouse and 2) lack of space in my home office. I have a spare linux box (running RH72) that I'd like to just move completely into a remote section of my house leaving only a power cord and ethernet cable to it. Then I can xlogin from my laptop (using Exceed in Win2K or from another linux install).

[bdg1983]

You can try using Xnest as I do at work for AIX access.

Description:

Can I get a graphical login to a remote computer?

Solution:

Remote X-sessions are possible, but recommended only for fast connections with plenty of bandwidth, as a graphical session requires alot of communication.

NOTE: To start additional X-session you will need to be logged in as the root user.

In short, a remote session requires the cooperation of both computers. The X access of the computer you wish to access must be modified to include any client that you want to connect from,
and you must start a new X-session on your local computer.

To allow a graphical connection to a remote linux box, the computer you wish to connect to must allow graphical connections from your system. This is done by editing the Xaccess file in
/etc/X11/kdm/ to allow the client computer(s) -- None is the default for Caldera Openlinux, but uncommenting the line

#*#any host can get a login window

allows all clients to connect, which may be a security risk, so you may want to specify clients. For this faq, we will just uncomment this line (it is the first non-comment commented line). Once
this change is made, you will need to re-start the X-server. You can use the login manager, or just use a terminal to go to runlevel 3 then back to 5:

init 3
init 5

Second, the client will execute this command:
X :1 -query 192.168.1.5

The numbers will be different for your system; the ":1" is the next X-session - If you already have 2 X-sessions, use :2, etc. The ip, obviously is the system you want to connect to - this can be a
fully qualified domain name if it is known by your system. This session will be on the next virtual terminal (typically F9) and will be the active one until you switch back.

To start a new X-session in a window of your current X-session (nested), use the Xnest command in place of X:

Xnest :1 -query 192.168.1.5

NOTES:

- To run this in the background, you just add the ampersand [&], and to disconnect it from a terminal, just [ctrl]-[d] out of the terminal window once it is in the background. If you forgot to send the
process to the background, type [ctrl]-[z], then 'bg' [enter], then [ctrl]-[d] out.

- You can connect to any computer which can run an X-session and which uses standard X protocols, such as SCO unixware. They may require changes to X access as well, but configuring
them is beyond the scope of this faq. Some systems default to allow all clients to connect, in which case you may not need to change anything.

- Firewalls will disrupt this setup. You will need to find out what ports are being used and how to get through before this will work for those systems.