We use VNC currently to access our regular Windows machines, but it seems pointless adding the network overhead when we're using X to distribute the remote sessions....so we'd rather monitor the X session itself if possible... and surely it must be??? Matt > ----- Original Message ----- > From: "Jim Daleo" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, May 03, 2001 11:57 AM > Subject: RE: [Win4Lin-users] Monitoring Win4Lin sessions > > > > > I use TightVNC to transport the user I/O between the server and the > clients. > > This is a variation of VNC. A VNC server looks like an X server to > > applications and a VNC server to the VNC client software. The client > > software, vncviewer, is available for Windows or Linux and is very small. > > It easily fits on a floppy. It has a number of different compression > > options and, as a result, works well for both local and remote (low > > bandwidth) users. > > > > With VNC you can open the desktop from any machine on the network and the > > desktop, the applications, even the cursor is exactly how you left it. It > is > > also possible to have the desktop shared by multiple users at the same > time. > > > > I have both Windows and Linux clients running this way. I keep the viewer > > and the configuration options file on the server an download them to the > > client each time they are used. This way local machines automatically get > > the latest version of the viewer. > > > > I have written a number of scripts to help to automate and maintain my > > setup. If anyone is interested I can make them available. > > > > Regards > > > > Jim > >
begin:vcard n:Claridge;Matthew x-mozilla-html:FALSE org:Brecon Beacons National Park Authority adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] title:I.T. Systems Officer x-mozilla-cpt:;4960 fn:Matthew Claridge end:vcard
