: Here is my goal: One user in Chicago must control one PC in St Louis.
: Five users in New York, L.A., and Seattle must be able to view, but
: not control the same PC.
: 1) Two VNC Servers running on the same Windows machine: one for the
: "Controller" and one for "Viewers" Or 2) Two passwords for the same
: VNC Server: one for the "Controller" and one for "Viewers"
I don't think the windows server and viewer is capable enough.
It could be custom-hacked to do it, but not off the shelf.
The way I'd approach it is with an intermediate linux/unix box. On the
PC, you run the server shared, but with a password the other folks don't
know. Then on a linux/unix box, you run an Xvnc which has a password
the others *do* know, in which you open an vncviewer to the PC in
view-only mode. Finally, you connect to the PC to control the demo, and
the other folks connect to the Xvnc in which a view-only vncviewer is
running.
So. You're running two extra processes; an Xvnc process and
a vncviewer. You access the PC directly to control it, but the
viewonly clients access via a viewonly path through Xvnc.
But it *does* depend on having somewhere to run the Xvnc/vncviewer pair.
Alternatively, you can check out somewhat more exotic possibilities,
such as
http://www.informatik.uni-trier.de/~ziewer/MulticastVNC/
http://sourceforge.net/projects/vnc-reflector/
Those also provide methods of having many read-only viewers; I've used
the multicast version and (being a java app) it's a bit slow, but it
seems to work OK. Others have said the vnc-reflector is a good tool,
and from the readme, it looks like the better bet of the two (that is,
it mentions the ability to have a read-only password and a separate
read-write password to the same reflected session), and seems to
have pre-compiled windows binaries as well as unix source (though
I haven't tried it yet myselves).
Wayne Throop [EMAIL PROTECTED]
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
