----- Original Message -----
Sent: Tuesday, September 17, 2002 7:03
PM
Subject: Re: [Kaboodle-devel] Re:
Kaboodle + zebedee Status
----- Original Message -----
Sent: Tuesday, September 17, 2002 2:15
AM
Subject: Re: [Kaboodle-devel] Re: Kaboodle +
zebedee Status
> VK:
> Hello! Welcome back. Some
comments to your answers:
>
> > > 1782
and 4182 being port-forwarded. That's good. I *think*
> >
> that 1782 was used by the old JetSend stuff; I'll
experiment
> > > to see if it's needed at
all.
> > >
> > I tried with only port 4182 and the VPN
worked behind the firewall.
>
> Great! Did both VNC and
file-transfer work?
>
No. I was able to just VPNed behind
the firewall.
> > >
2. With the VPN running, I can go to my Partner's Network GUI,
> >
> and initiate a VNC connection to the "VPN node" on
their side
> > > of the connection. But only in
one direction: my two endpoints
> > > are
Windows98 and WindowsNT: I can connect from the WinNT
> >
> to Win98, but not from Win98 to WinNT. When I try, I
see 3
> > > Zebedee command-shell popups go past
very quickly, with some
> > > mention of some
error in one of them (too fast to read, and
> >
> it's not logged). After the failure, I see in my Task
Manager
> > > that Zebedee has stayed active;
each time I try to connect and
> > > fail,
another Zebedee process is spawned. I am unable to test
> >
> PC1 to PC4 yet (with PC2 and PC3 being the two VPN
endpoints)
> > > because of this.
> >
>
> > In the above case, is the VPN running behind the
firewall? Even I have
> > observed the same at my end. Sometimes I
can only connect VPN from one
> > use side only. I do not know why
this is happening. But sometimes I can
> > get the VPN connection
from both the sides and all the VNC paths works.
>
>
> I
think we need to figure this bug out. Also, can you do
> something about
the Zebedee processes which remain active? If the
> tunnel fails, the
processes should be terminated.
>
I am in process of killing
all the zebedee through kaboodle.
>
> > > 3. To
start a VNC session, I have to scroll to the device in my
> >
> partner's network GUI. I cannot use the VNC Service
icon,
> > > because no active VNC servers appear
in the list. They should,
> > > of course: each
available VNC server should show by device
> > >
name *and* by network: eg, "Dad's PC on Scott's LAN" should
> >
> be in there.
> > >
> > Please
clear the registry and start all the VNC servers before running
> >
the kaboodle instance as the kaboodle does VNC port scanning for all
the
> > devices at the startup only if the kaboodle is started for
the first
> > time. If user follows the steps he will see all the
devices in the VNC
> > service icon list as soon as user get the VPN
connection.
>
> I did this and the bug remains: I don't see a
list of
> available VNC machines in my VNC service icon after I get a
VPN
> connection. My WinNT machine is behind a firewall, my
Win98
> machine is connecting via AOL.
>
We have separate VNC service icons
for each LAN so I had added the list of all the target machines for that
particular LAN in corresponding LAN's VNC service icon. So I have not
merged all the VNC targets in my LANs VNC icon. You will see the list of VNC
servers for that particular LAN in the VNC service icon in the service group
for that particular LAN and can connect to the VNC server.
>
> > > 4. File-transfer and
web-config do not work yet with the VPN tunnel.
> >
> I'm hoping you're just planning on getting to that
after we
> > > debug this. The VPN connection
should, after all, work for any
> > > Kaboodle
service, transparent to the user, and it should be
> >
> easily scalable for other services not yet built
(chatting,
> > > folder sync, etc.).
>
> >
> > I have tried file transfer with port 7000 and it worked
behind the
> > firewall as well. I have added the code for the
pc2-pc3 file transfer in
> > wincvs today. User will see the list of
the devices for file transfer in
> > the file transfer service icon
list.
>
>
> I'll test this ASAP.
