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
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Matt
Claridge
Sent: Thursday, May 03, 2001 5:53 AM
To: [EMAIL PROTECTED]
Subject: [Win4Lin-users] Monitoring Win4Lin sessions
We're using XDM to run remote Win4Lin sessions from a server. What we'd
like to be able to do is to view/take control of remote Win4Lin sessions
from the server - for upgrades, installations and problem solving.
Now obviously this should be possible, what with X & Linux being what
they are, but does anybody have any ideas as to the best way to enable
this?
cheers
Matt
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
