[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[school-discuss] Re: Remote GUI access (was Re: Emulation via Windows)

on Tue, May 31, 2005 at 03:54:32PM +0200, Jimmy Pierre (jpierre@xxxxxxxxxxx) wrote:
> Greetings,
> Thanks a million to all for replying to my posting. I spent the last 24
> hours testing your solutions and as I ma not a Linux GURU, I settled for
> Xming.
> The server is on line cisware.tzo.com and the username : student and the
> password: student123

You *really* don't want to do that.

X is suitable for running among systems in a trusted lab, if there's no
critical data on 'em.  Opening up a system to random, unsecured,
over-the-Net access, full interactive access is a really bad idea.
> Please give it a try and let me know if how it goes... I might need to open
> some ports on the firewall...

Um.  I'd strongly recommend *closing* 5900 - 6099.

> Cheers
> Jimmy
> -----Original Message-----
> From: Karsten M. Self [mailto:kmself@xxxxxxxxxxxxx]
> Sent: Tuesday, May 31, 2005 7:34 AM
> To: schoolforge-discuss@xxxxxxxxxxxxxxx
> Subject: [school-discuss] Remote GUI access (was Re: Emulation via Windows)
> on Mon, May 30, 2005 at 11:55:56AM +0200, Jimmy Pierre (jpierre@xxxxxxxxxxx)
> wrote:
> >  <http://www.cisware.com>
> >
> > Has anybody got any experience on running some sort of Terminal Server
> > on a linux box and connect via a Windows Box?
> FYI, that's generally referred to as "remote access" rather than
> "emulation".
> Several options, the main factors are server load and users supported
> (dozens to ~100 clients under X, for light loads, vs. a dozen or so VNC
> clients), and security -- few of these methods offer integrated security,
> and may not be suitable for open networks as passwords and other data are
> transmitted "in the clear".  Securing the systems via SSH tunnels or systems
> such as FreeSWAN are possible, but require additional effort.
>    - X server.  Install an X server on the legacy MS Windows box.  You
>      then connect to a GNU/Linux system for applications.  Using XDMCP
>      (X display manager control protocol) will provide the user with a
>      user/pass login.  This is probably your best bet and the most
>      widely used solution.
>      Advantages:  simple, low cost, fast, low server load, many users
>          per server (20-40+).
>      Disadvantages:  unsecured, not appropriate for open / unswitched
>          networks.  May be tunneled over SSH for security.
>    - VNC  Users run VNC client on desktop, connect to VNC server.
>      Running servers out of inetd / xinetd allows for automated
>      connections (but no session persistance).
>      Advantages:  minimal client software.
>      Disadvantages:  heavier server load, slower than X, unsecured,
>          fewer clients / server than X.  May be tunneled over SSH for
>          security.
>    - NoMachines "NX".  Haven't used it, though it's supposed to be
>      faster/lighter than VNC, and offers built-in security.
> I'd recommend trying  the X server solution first.  There are several free X
> servers available for legacy MS Windows, of which the XMing server is free,
> fast, and can be run from CD.
>     http://freedesktop.org/Xming
> For run-from-CD, I found that copying the Xming directory tree to a CD and
> launching 'xlaunch' from the CD a no-install X server is possible.
> Neat as a demo.
> Peace.
> --
> Karsten M. Self <kmself@xxxxxxxxxxxxx>        http://kmself.home.netcom.com/
>  What Part of "Gestalt" don't you understand?
>     So it is down to you, and it is down to me. If you wish her dead, by
>     all means, keep moving forward.
>     - Princess Bride

Karsten M. Self <kmself@xxxxxxxxxxxxx>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    18.8% of all browsers that claim to be MSIE, aren't.
    - http://www.virtuelvis.com/archives/35.html

Attachment: signature.asc
Description: Digital signature