David:
Heya. Thanks for the positive comments, let me dive into
your questions:
> First let me say that I am now VERY excited about Kaboodle/getEngaged.
> Previously I had been moderately interested but after having played
> around with both I'm very impressed. This is my first foray into remote
> computing, however, so I intend to ask what are likely redundant
> questions.
>
> Imagine if you will that my setup is 3 PC's at the main site (hereafter
> SERVER, DESK1, and DESK2) and 2 remote sites (from now on STORE1 and
> STORE2). We'll say that I have [EMAIL PROTECTED] and [EMAIL PROTECTED]
> addresses to work with. I install Kaboodle99 on all 5 systems, 3 of
> which are together behind the company firewall and 2 of which are in
> remote locations. myself@ and admin@ both setup Registration files at
> getEngaged.net. myself@ furthermore creates a partnership with [EMAIL PROTECTED]
For VPN'ing, you really only need one Kaboodle instance per
network, not one on every PC in a network. Not that I mind. :)
> NOW the fun begins. Is it possible to use this one partnership for all
> 5 locations? If not, will there have to be a separate partnership (and
> therefore email address) for each of DESK1, DESK2, STORE1, and STORE2?
Right now, you need one registration file per network, and one
partnership per connection. So for what you describe, you will need to
install a regfile on either DESK1/DESK2, plus a regfile on both STORE1
and STORE2. Then create two partnerships: one between DESK1/DESK2 and
STORE1, the other between DESK1/DESK2 and STORE2. Given that, you'll be
able to VPN from your main-site to each of your remote sites, or from
either remote-site back to your main-site.
I've given some thought to "self-partnerships", but I haven't
sold myself a good way to do it yet.
> How do I set up Kaboodle to use VNC over Zeb on the LAN (I tried
> earlier today and it poked around at the LAN's public IP; will this
> require KaboodleProxy?
On the same LAN, if you have Kaboodle installed on both the
VNC Viewer and VNC Server machine, and you initiate the VNC connection
with Kaboodle, it will "automatically" tunnel the VNC connection thru
an encrypted channel. The encryption process isn't as robust as Zebedee
(which is used when Kaboodle talks to Kaboodle across the Internet),
but it should be sufficient for intra-LAN use.
As for KaboodleProxy, it's used to connect Kaboodle VPN endpoints
together without anyone having to adjust any firewall or NAT'ing router
"port-forwarding" settings. It's in a state of repair right now, though,
should emerge again for real at the end of this month.
> Is there a method for not allowing DESK1, STORE1, etc.
> to either a) seize control of SERVER, b) kill Kaboodle/Zeb/VNC, or c)
> even know that k/z/v are running (no tray icons, no task-manager entry)?
> Can Kaboodle be run as an untouchable service?
I'm sure it could be done, but since Kaboodle is built to enable
"easy" remote-control of stuff on your LAN, it's a bit tricky to install
it and then turn off its capabilities. Perhaps the easiest place to
start is to install Kaboodle on your SERVER, and then indicate in the
VNC options which PC you want to be allowed to make VNC connections to
it. If you don't want *anything* to be able to "seize control", I'd
advise not installing either Kaboodle, or VNC for that matter.
As for the try icons, the easiest way to remove those is to
tinker with the Windows registry. You can remove the keys in one of
these registry places:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run or
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run or
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Of course...as always...tinkering with your Windows registry is
like tinkering with your car's transmission. I wouldn't advise it. :)
> This ought to get me started. I'm sorry if all of this seems like
> rehash -- I google'd up a bunch of VNC references, but of course the
> kaboodle/engage specifics just weren't there (yet).
>
> On a different yet entirely relevant note, I'm surprised at how quiet
> this list is, and at how relatively unknown kbProx and Zeb are. I had
> never heard of them until I saw a comment on /. I anticipate being on
> the leading edge of a wave of mass adoptions, once others discover how
> useful and practical this technology is.
The comment on /. might explain the recent rush of traffic.
Do you know exactly which article?
cheers,
Scott
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Kaboodle-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-user
To UNSUBSCRIBE, click on the above link.
