3 Jan 2002 Status report -------------------------- > Also, I wanted to confirm: suppose host-A and host-B are on > my LAN, and host-C and host-D are on a remote LAN. Hosts A, B and > ... > tunneling work you've done smart enough to allow this to work: > > A (VNC client) => B (Kaboodle) => C (Kaboodle) => D (VNC server)
I am afraid this feature was not mentioned in the initial specification and so it is not currently implemented. We were talking about running Kaboodle and VNC on the same computer while the new feature implies having a sort of Kaboodle gate - a machine that is not running VNC itself but is capable of forwarding VNC traffic. Commonly, your chart would look like this: [K.+VNC client] => [K. gate] ...(x N times) ... => [K.+VNC server] which would be useful to connect several computers on a LAN each running VNC Server to a remote Kaboodle machine through just one Kaboodle gate resident on the LAN. This feature may be added as a future enhancement. > VNC-Detection > I'm thinking that this VNC auto-detection should be part of > Kaboodle's overall LAN detection. Here's how I think that old part Agree. > For the server detection of other devices, what the VNC auto > detect should do is simply attempt to connect to TCP port 5900-5999 > on a device, and grep for an RFB reply. If it fails to connect or if I am afraid this will take longer than we expected. Moreover, among the detected computers there will also be the ones with VNC Server not under Kaboodle control. It would happen because the server may have been launched either at Kaboodle start-up or independently (e.g. manually). If that is the case Kaboodle had not set the proper registry options and is now unable to establish connection to 127.0.0.1. Thus, Kaboodle-independent VNC Servers are not the matter of concern until Kaboodle gates are allowed. I suggest the following solution. The device list shows special icons for the machines on which the checkbox is set so to run VNC Server on startup. The existing Kaboodle algorithm of LAN auto-detection is used to deliver this additional yes/no bit. > The "VNC Setup" PropertyTab Your suggestions are fine, but it is an additional work. So, along with the abovementioned VNC Server detection mechanism it will make the delivery date January 21, 2002. _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
