Multiple People Hooking In
Jesse
jlc "at" msdlg.com
Mon Sep 4 13:31:02 2006
Actually, we're running the free version of RealVNC, and I did see that
option there, and set it up. I haven't had a chance to test it yet, though.
Jesse
----- Original Message -----
From: "Calvin Webster" <cwebster "at" ec.rr.com>
To: "Neal Hartgrove" <nealh "at" nortel.com>
Cc: "Jesse" <jlc "at" msdlg.com>; "VNC Mailing List" <vnc-list "at" realvnc.com>
Sent: Sunday, September 03, 2006 2:33 AM
Subject: Re: Multiple People Hooking In
> Jesse,
>
> That's a handy feature that appears to be missing from RealVNC Free
> Edition. However, RealVNC Personal ($30) and Enterprise ($50) Editions
> have this capability and much more. If you have a simple, home or small
> business network you probably don't need all that, though. TightVNC
> might be one options to look at, but I'm not convinced it's better than
> RealVNC overall, especially for our network.
>
> When I want to setup a training or demonstration Windows system I use
> the following server configuration:
>
> Double-click on VNC icon in system tray
> Opens "VNC Server Properties" dialog.
> Click [Authentication] tab
> Check (enable) "VNC Password Authentication"
> Click [Configure] button
> Enter a new password in both boxes.
> Click [OK] button
> Click [Inputs] tab
> Un-check (disable) all options on this tab.
> Click [Sharing] tab
> Check (enable) "Always treat new connections as shared"
> Un-check (disable) "Non-shared connections replace existing ones"
> Click [OK] button
> Dialog closes and changes are effective immediately
>
> Then I send a local email notice to those invited to join the training
> or demonstration session. Users connect to "server:0" using their
> RealVNC Free Edition 4.1.2 client. The default client settings are fine
> since I've already setup the server.
>
> When I'm done with the session I reset the password to a secure, unknown
> one and change the properties back to our standard ones. Then I restart
> the service to disconnect everyone.
>
> For Windows workstations on our intranet, VNC Server is only used by
> systems/network administrators for helpdesk and software installation.
> Users are not given the server password and are prevented from disabling
> the server.
>
> I have Windows virtual machines that I use for training and
> demonstration as referenced above.
>
> Windows and Linux VNC clients are used by everyone to connect to Linux
> development machines where multiple, separate, private connections can
> be made at various resolutions and color depths. Authentication is
> handled by XDM (GDM) and access control is handled by local server
> mechanisms. Since we have pretty tight perimeter security and other
> network protection, risk is minimal using non-tunneled connections.
>
> Note: If you are making VNC connections over the Internet or any other
> untrusted network you should always tunnel them using a secure method
> such as Secure Shell or an encrypted VPN.
>
> --Cal Webster
>
>
> On Fri, 2006-09-01 at 13:21, Neal Hartgrove wrote:
>> tightvnc will allow that
>>
>> www.tightvnc.com
>>
>> it allows multiple people in and they can either work or observe,
>> depends on password
>>
>>
>> Jesse wrote:
>>
>> > Is it possible to have multiple people log in to a VNC Server? In
>> > other words, if I have VNC Server running on a PC, can we somehow set
>> > it where two people can log in to that server at the same time, and
>> > both see the screen?
>> >
>> > We've tried that, and what happens is when the 2nd person logs in, the
>> > 1st person is disconnected. But, I didn't know if there were some
>> > settings somewhere that would allow us to share the connection.
>> >
>> > Thanks,
>> > Jesse _______________________________________________
>> > VNC-List mailing list
>> > VNC-List "at" realvnc.com
>> > To remove yourself from the list visit:
>> > http://www.realvnc.com/mailman/listinfo/vnc-list