Remote Desktop for *nix

Is there a remote desktop for Red Hat linux?

I have a remote game server running Red Hat 3.0 Enterprise edition and would like to be able to have a GUI accessible on the srever like the one you can use with Windows Servers Remote Desktop.

Thanks.

Sure... VNC. Just remember... its not encrypted... so tunnel that over ssh. :)

http://www.uk.research.att.com/archive/vnc/sshvnc.html

Wonder why I didn't think of that?
lol

Think I'll blame it on my College professors. lol

Thanks phish.

or try ssh -CX host or ip

the capital C is for Compression
the capital X is for X (graphics)

you need to have some settings in your ssh config and X config changed (perhaps) but usualy this works straigt from the box...

on both computers you need to have an server ( XFree86 or simmilar) installed
and on the client you need to have X running..

Are you running gdm/xdm ?

Do you want to connect from another machine on the LAN or WAN ?

If it's LAN what about loging on remotly using gdm:

On the server run gdmsetup and under security remove the tick from 'Always disallow tcp connections' or similar.

Then on the client <CTRL> <ALT> <F1> to a console & log in then try

X :1 -ac -query server_ip

and you should then on Screen :1 be presented with a gdm login for the server - This ok over a decent bandwidth - if you want to do this over a WAN try looking at this : www.nomachine.com

Steve

TightVNC http://www.tightvnc.com

TightVNC automatically tunnels a VNC connection over SSH. Also supports read only and full access passwords. And it tastes delicious!

Quote:

---

Originally posted here by kr5kernel
TightVNC http://www.tightvnc.com

TightVNC automatically tunnels a VNC connection over SSH. Also supports read only and full access passwords. And it tastes delicious!

---

Actually, TightVNC only encrypts the password, the rest of the communication is not.

http://www.tightvnc.com/faq.html#howsecure:

Quote:

---

How secure is TightVNC?
Although TightVNC encrypts VNC passwords sent over the net, the rest of the traffic is sent as is, unencrypted (for password encryption, VNC uses a DES-encrypted challenge-response scheme, where the password is limited by 8 characters, and the effective DES key length is 56 bits). So using TightVNC over the Internet can be a security risk. To solve this problem, we plan to work on built-in encryption in future versions of TightVNC.

In the mean time, if you need real security, we recommend installing OpenSSH, and using SSH tunneling for all TightVNC connections from untrusted networks.

---