Hello Steffen,
>>>>> O. STeffen BEYer wrote:
> is there a way to restrict TightVNC connections to a LAN, e.g. to
> non-routable reserved IP blocks such as for instance
> 192.168.0.0-192.168.255.255, via configuration in TightVNC itself?
TightVNC supports IP-based access control via the AuthHosts option which
was inherited from VNC 3. Here is the documentation (search for
"AuthHosts" on that page):
http://www.realvnc.com/products/free/3.3.7/winvnc.html#4Current version of TightVNC (1.3.10) does not allow to configure this
setting from the user interface, so it has to be edited in the registry.
Next major TigthVNC release will include a proper user interface for
configuring IP access control rules.
--
With Best Wishes,
Constantin
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july___________________________________________________________
TightVNC mailing list,
VNC-Tight-list@...
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list