remoteto Red Hat Linux server

Newbie question.
How do I 'remote' to a Red Hat linux server?  In other words, what is the Windows-equivalent of Remote Desktop Protocol / Terminal Services for Linux?
Who is Participating?
TintinConnect With a Mentor Commented:
Most people use VNC.

vncserver comes standard with Redhat (assuming it's a recent version)
ppfoongConnect With a Mentor Commented:

You can also use XWindows with SSH. Majority of Windows based XWindows client fall on commercial software with a small price.

nociConnect With a Mentor Software EngineerCommented:
Look into no machines NX, it's X with low latency & compression optimisations.

There are RPM's available.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

cliffordgormleyAuthor Commented:
that url takes forever to open.....

What is an RPM (I told you I was a newbie).
nociSoftware EngineerCommented:
an rpm is an installable image following the Redhat Package Management format.

After you download an rpm file you can install them with

rpm -i {packagename}

I have the whole nomachine page opened in about 25 seconds.
The URL you might need is:

That save you the attempted download of some flash pictures.
cliffordgormleyAuthor Commented:
Hi Noci,
Do I use the NX Node or NX Client?
Does the NX Server have to be on the Red Linux Server?
Thanks for your patience.
On the Linux server you install NX Server, NX Node and NX Client for Linux.  On your PC you install NX Client for Windows.
nociSoftware EngineerCommented:
Have been away this day,
Tintin is correct.

Have you got NX software to work well for you?

I tried on Solaris 10 and it wouldn't even get to the stage of running/starting.

The Windows client gave me cygwin DDL errors.
nociSoftware EngineerCommented:
Yes, I only use the Gentoo install kits. (1.5) currently, the 2.1 is not out yet...,

I had some troubles, but that was mainly with getting the key management straightend out.

(Starting out with the standard installation and then upgrading meant that that
the keys got invalidated in the upgrade, and I needed all clients to have a new
certificate. But that just once, that you make a backup of your keys
and restore that after install.)

Just be sure to start with a Self generated keyset from the start out.
(BTW it is ssh based, so the PRIVATE KEY, should be sent out to
all clients for inclusion, DON"T also use you real SSH key for this.)

I used to use it from a clients office to reach my home, I don;t have windows myself.
Well, NX and VNC is nice and all, but ... NX isn't that easy to get going for a newbie... VNC can be rather straightforward though.
But... X is actually all you need... Ever heard of XDMCP?

On the winoze side, get cygwin/X (from, then (assuming no intervening firewalls:-) just execute
XWin -query name_or_IP_of_redhat_box
... On the redhat, you might have to enable XDMCP (first) for remote clients, but... that should be easy... I'm sure there is a redhat-config-whatever that does it, but you could find your way with these instructions:

The fun thing is that you can use cygwin to manage the solution suggested (with ssh -X) by ppfoong too:-). Just fire up an XWin (IIRC, you might need create a /etc/X0.hosts containing the name or IP address of the localhost and the redhat box, each on a separate line), then (make sure you have "export DISPLAY=:0" first) "ssh -X name_or_IP_of_redhat_box" ... This assumes X tunneling is turned on in the sshd server.

VNC (as suggested by Tintin) is also rather easy... Might be as easy as running vncpasswd for the user mentioned in the /etc/sysconfig/vncservers file, starting the service by "service vncserver start" then getting a windows vnc client (one of the best is UltraVNC from very easy.

-- Glenn
Oh, forgot what I intended to close with... Since remote to ... in the *nix camp... used to be how to establish a remote _terminal_ session, ssh or somesuch is all you need :-):-).

-- Glenn (who has been sampling brews in preparation for X-mas...:-)
nociSoftware EngineerCommented:
Pure X can work, the problem with pure X is latency because most actions are of a query/response or command/return-status type.
The round trip delays add up.

VNC updates the least possible on screen updates, it passes bitmap portions of a screen/
In my experience it either hogs bandwidth or it loses parts of updates on the screen that are not exactly in

NX works as an X server, but it removes the query/response types, by bundling them as much as possible, it will become

command, command, command, command, command, command - final result is really reported, the intermediate results are
just local success returns. Then a stream of command travels with out delay.
With X that same sequence would bee Command/Status, C/S, C/S,C/S, C/S, C/S  where you have network travel time a every
C/S pair.

Also bitmaps are compressed. (there used to be a tool for that in the past allready something like xd, or dx not sure there).

That's why I like NX better. just my .02.

And indeed if X is not needed, ssh would be good enough ofcourse.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.