24 Jan 2002 Status report ----------------------------- >1. Yes, you'll defnitely have to get Kaboodle VPN'd to see any of this > work correctly. Please try this: head to ftp.echogent.com, and go > ...
We tried it and... it did not help. We took one machine out of the firewall and the other one was still behind the firewall. Connection failed - just the same way it did with the current Kaboodle version under design. I remember, once we succeeded getting them work, but it was under quite different conditions - since then our corporate network topology and the ip layout have changed. I can assume we had both machines out of firewall then, though I am not sure for there were a whole lot of different combinations we had tried. Each direct-ip machine means for us a separate piece of wire, which has to be mounted and connected and it takes time, you know. And with all that, we are not certain of success. Anyway, our suggestion is to begin work on the project according with the last specification, leaving the obscure points out. Meanwhile, you will provide us with clear requirements that the network topology should meet so to get the inter-lan connection work (one ore both parties must have direct ips, can they have the same default gateway, can the two lans only differ in the ip mask and so on). >2. I'll modify section 4.3 of the spec to clarify scanning for a VNC > server. This can only needs to be performed once per device, not > every time Kaboodle starts up. We could do this by using the VNC > ... The questions are: (1) We see the following states that a machine can be in: a. no Kaboodle, no VNC; b. Kaboodle, no VNC; c. no Kaboodle, VNC; d. Kaboodle and VNC controlled; e. Kaboodle and VNC uncontrolled. Do we need to differently display all the cases at the machine icon? If so, we need two more icons (c and e) and could you help in the icon design? (2) We have put it on the test: the scanning rate makes some 1-1.5 sec per a port. The worst case (99 VNC display) takes 2 minutes per a machine. Mind that. (3) What you are speaking about is: a remote machine is automatically scanned once in the lifetime and then may be rescanned manually. How often do you think the user should do the updates and what is he has forgotten to do it for quite a long time? Will he observe the valid scene? There may have appeared some new out-of-Kaboodle-control VNC servers and some may have gone. >I noticed that EFHelper wasn't in there when I tried >to activate the VPN capabilities of Kaboodle, compiling the >latest source code. EFHelper folder has existed all the time and in the last .zip we just inserted the EFHelper.dsp into the workspace. Have you not got it? >As you know, the GetEngaged website gives >you two files: a RegistrationFile and a PartnershipFile. They >have a .asp extention (don't know why). Those files are, as I Exactly. We noticed that a couple of days ago the extension of the downloaded files was .asp. As EFHelper requires .ecf we did the renaming before applying EFHelper.exe. However, today the files were coming with the correct extension again. >Anyhow...without EFHelper, you can't "install" those >files from the webserver, and so the VPN capabilities will not >initiate. I bet this will matter to you guys as you work on >the VPN tunneling piece. :) We are surely aware. >to work; I'm stil getting a "signature invalid" error when trying >to load the files into the freshly compiled EFHelper... Did you give the downloaded files the right extension? As for us, we certainly did not change a bit of the EFHelper code. And more. All the Kaboodle dialog panels inherit from CEFPropPageBasic class and all of them have their own data and code to create and destroy CEFButton owner-drawn buttons, which are functionally identical. The question is: would you like us to unify this draw functionality by moving the CEFButton-related data and code to the basic class CEFPropPageBasic, thus omitting duplicates? _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
