Hello!
Why does Xwindows listen on port 6000, isn`t it just the service for the GUI on the workstation itself?

http://www.linuxplanet.com/linuxplanet/tips/1124/1/
here's an article on how to shut down the x-window tcp ports.

what is it good for .... (absolutely nothing?)

X applications talk the the X server using networking protocols, the X server then displays the window.

You can run a program on one computer but display it on another (which is handy when you want to sit at a P75 and run Mozilla and StarOffice at the same time!)

So xwindows can be used like pcanywhere?
If this is right, how can I use it?
Just using the web browser and adding an ":6000" to the ip adress to let the browser know what port I want to connect?

A bit like PC Anywhere, but not entirly.

You can't use a web browser, becuase browsers don't support the X protocol, and X doesn't support http.

The method I use to run remote X applications is as follows. Assume I am sitting at machine A and want to see programs on machine A but run them on Machine B.

[code]
ssh -X -C dorward@machineb.host.name
Password: ***********

dorward@machineb:~$mozilla &
[code]

The -X to ssh enables X forwarding, it may be enabled by default on your system. The -C enables compression, this eats more CPU but speeds things up over a slow network.

Mozilla will then run on Machine B and display on Machine A. Remember that if you refer to any file within Mozilla it will look on Machine B and not Machine A.

A program more like PC Anywhere is VNC, this includes a Java Applet client so you can point your web browser at it. There are also Linux, Windows, Palm Pilot, and other client applications. Servers are available for Linux and Windows (among others).

Thank you for your help!
I tried this and it worked as you said!
But as always I have one last question:
Isn`t it the same as telnet? I couldn`t see any diference!

Ssh is somewhat similar to telnet, but considerably more featureful and encrypted.

If you didnt see any difference thats all the better, a proof the system works.

The difference is SSH is able to handle authentication plus datastream encryption plus datastream compression in one (and still be easy to handle), where telnet does everything (auth & datastream) in cleartext.