Oleg:
Heya. Some quick comments:
> >1. Yes, you'll definitely 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.
As you know, the best way to set up the two VPN'd Kaboodle
machines is to connect them to the Internet via two different ISPs.
I use my corporate LAN for one, and an AOL dialup for another. Perhaps
you have a machine with a modem you could use? If not, I could setup
a machine here on my LAN with a VNC account, and you can connect to
it remotely.
Regarding the firewall, Kaboodle uses port 4182 for it's VPN.
You'll need to allow port 4182 into your firewall and (if the firewall
NATs as well) you'll have to port-forward it to the IP address of the
machine running Kaboodle. That's how my corporate LAN is setup and it
works okay.
Please let me know when it does work, as this means of setting
up the VPN piece is central to this modification, and central to how the
end user will use the application. I can't see how you're going to code
or evaluate unless you can actually see the code working.
> 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?
Nope, we don't need to display all the cases at the machine
icon. In fact...I'm not sure about changing the icon at all just
because of VNC.
> (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.
Ah, MFC sockets. What a pain. Try this instead:
nmap -sT -p 5900-5999 192.168.0.1-254
That takes about 10 seconds.
> (3) What you are speaking about is: a remote machine is automatically
> scanned once in the lifetime and then may be rescanned manually.
Yes. If the user subsequently installs VNC on a machine that
was previously determined to not be running VNC...all they have to
do is hit the "Check Again" button when they open the Property Panel.
That should be fine.
> >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?
Yup, got it now so that it compiles. I redid the project
settings so that it compiles to "GetEngaged.exe". I should send you
the code snapshot I have that we can start working with on this new
project. It contains some of my icon work as well.
> >As you know, the GetEngaged website gives
> >you two files: a RegistrationFile and a PartnershipFile. They
> >have a .asp extension (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.
Yeah, I noticed the same thing. Very weird. Of course...
without an install script, it's tricky to get the GetEngaged.exe
(aka, EFHelper) executable to be the default app for this file
extension. It used to be that the InstallShield script took care
of this. We *may* need to change it so that the first time you
run Kaboodle, it affects this. It's not as if users will try and
install a RegistrationFile before they even run Kaboodle for the
first time.
> 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?
Sounds good!
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
