The remote systems are Windows.  The company VPN client does not support Linux too well and a majority (99.9%, especially labtops) of the systems are running MS Windows.  The engineers want and need to see their consoles remotely. 

I appreciate all the suggestions, please don't think I don't.  I have talked with the engineers about all the solutions mentioned, none will work because they involve stopping an already running appication and fireing up vncserver (by what ever means) and then starting the application again.  They want to be able to see their already running desktop remotely.

On 11/17/06, Les Mikesell <> wrote:
On Fri, 2006-11-17 at 22:04, Jamie Bohr wrote:
> This is for engineers at work.  They want to be able to connect to
> their consoles remotely.  We are using RHEL 3 WS, the tool is only
> supported on this platform.  The idea is the same as it would be in
> Fedora though.  Start an X application when the users logs in and kill
> it when they log out.  I don't mind being pointed to a how to or even
> KDE/Gnome documentation.  I was able to get KDE to start the process,
> it just won't die when the user logs out.

If they want to run a single application, they can just
ssh in and start it by typing its name.  The ssh internal
port forwarding magic will forward the window display to the
local desktop.  From newer versions of ssh you may need to
use the -X or -Y options to enable X forwarding.

If you want the whole desktop, you can use native X by
enabling XDMCP logins.  From any other machine, start the
local display with 'X -query remote_host' and you will get
a graphic login prompt followed by a desktop session running
on the remote by displayed local to you.  This works best on
a fast local LAN and is cross-platform with the free Cygwin
windows version or Xming.

After XDMCP sessions are working you can also let vnc start
sessions on demand.  K12ltsp does it something like this:

Add entries to /etc/services like:

vnc-1024x768x16 5900/tcp
vnc-800x600x16  5901/tcp
..etc.. mapping ports to display types
Screen :0 will be port 5900 to vnc, :1 is 5901, etc.

Add a file named /etc/xinetd.d/vncts with entries like:

service vnc-1024x768x16
        disable         =  no
        socket_type     = stream
        wait            = no
        user            = nobody
        group           = tty
        server          = /usr/bin/vncts
        server_args     = -geometry 1024x768 -depth 16

service vnc-800x600x16
        disable         =  no
        socket_type     = stream
        wait            = no
        user            = nobody
        group           = tty
        server          = /usr/bin/vncts
        server_args     = -geometry 800x600 -depth 16

And add /usr/bin/vncts:
[ -f /etc/sysconfig/vncts ] && . /etc/sysconfig/vncts
                                                                               exec ${XVNC:-/usr/bin/Xvnc} ${VNCTSOPTIONS} ${1+"$@"}

And restart xinetd.  This makes a vnc connection start
up an X session which will go away when you disconnect.

  Les Mikesell

fedora-list mailing list
To unsubscribe:

Jamie Bohr