Like many other before you, I think you are confused about what exactly an X server is.
When you run an application that requires an X server, the server normally runs on the host local to you. With Exceed or X-Win32, the X server is running on your Windows host locally. Similarly, when you use a Linux desktop, there is an X server running on that host. It can be used by local applications, or by applications running on a remote host, where the X traffic is typically tunneled through the ssh connection that you used to login (but not necessarily). When you login and run applications, they use the X server identified by the $DISPLAY environment variable. For an application that is running locally, that will normally be localhost:1. The X tunnel mechanism sets up a listener on the remote host which is identified with $DISPLAY, and sends the X traffic back to your local X server, through the tunnel.
It is possible that you want to run X applications locally, but attach to a remote X server (where you won't be able to see the display, or manipulate the keyboard or pointing device). The same mechanism applies: set $DISPLAY to point to the remote server. >For example, 184.108.40.206:1. Doing this will cause any X application that you run to attempt to connect to the specified X server. If the server is reachable, and is configured to accept TCP connections, then the application should run, and send its output to the specified server. It will, of course, expect its keyboard and pointing device to be there, too.
Last edited by theNbomr; 10-09-2009 at 05:27 AM.