Igor:
        Some thoughts on what you're seeing:

1. If PC1 is running an independent VNC server with Kaboodle, and
   "Enable Kaboodle Tunnels for VNC" is set, then AllowLoopback
   should be set. That's what "Enable Kaboodle Tunnels" is
   supposed to do: set that registry key. Whenever Kaboodle is
   running and this Checkbox is selected, that key should be set.

2. Let's change the Checkbox which reads "Use Kaboodle to startup
   VNC Server only when it's needed" to read "Let Kaboodle auto
   start and restart the VNC Server when it needs to". If this
   box is selected, Kaboodle won't prompt the user when it makes
   a change to the VNC registry and restarts the VNC service.
   When the user first activates the "Enable Kaboodle Tunnels"
   checkbox, we should activate this checkbox by default if
   Kaboodle finds a WinVNC.exe server.

3. If Kaboodle makes any changes to the VNC registry, and the
   user clicks "Okay", and the "Let Kaboodle..." checkbox from #2
   is not selected, it should prompt the user with "Your VNC
   Server needs to be restarted for these Kaboodle settings to
   take effect." We can have two buttons: "Let Kaboodle Do this
   Now" and "I'll Do This Later".

4. If Kaboodle is started up with some VNC Server settings that
   require changes to the VNC Registry, we'll need to prompt the
   user in the same way as #3 if the "Let Kaboodle..." checkbox
   of #2 is not selected. If it is selected, we can just make
   the changes and quietly restart the VNC service.

        Sound good?

-Scott


On Fri, 3 May 2002, Igor Kotelevsky wrote:

> Hello Scott.
> I have found a following problem of the independent VNC server.
> PC1 is running independent VNC server and Kaboodle.
> Kaboodle on PC1 is "Enable Kaboodle Tunnels for VNC".
> User on PC2 checks radio button "Connect through Kaboodle (more secure)" and
> push button "Connect".
> Then user on PC2 see MessageBox("Local loop-back connection are disabled").
> The caption of this MessageBox is "VNC info".
> In this case Kaboodle on PC1 tries to connect with own VNC server on IP
> address of the LAN interface,
> and if it failed, then on loopback IP address...
>
> I have checked the source code of WinVNC server.
> I have found that in above case Kaboodle have to set VNC server registry key
> *AllowLoopback*.
> It is not difficult. But Kaboodle have to show MessageBox("The VNC Service
> needs to be restarted...").
>
> I have following suggestion.
> - Kaboodle checks VNC server registry key *AllowLoopback*.
> - If there is not above key, then Kaboodle show next MessageBox
> "Kaboodle have to put VNC server registry key *AllowLoopback* and restart
> VNC server."
> "Kaboodle don't will restore above key at the finishing of the VNC session".
> There are two buttons: "Let Kaboodle do this now", "Cancel VNC session".
>
> -Igor
>
>



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to