VK:
        Bugs still there. Here's the tcpdump that goes off
every 10 seconds:

21:06:05.694429 192.168.123.130 > 192.168.123.123: icmp: echo request
21:06:05.738385 192.168.123.130 > 192.168.123.4: icmp: echo request
21:06:05.757561 192.168.123.130 > 192.168.123.20: icmp: echo request
21:06:05.757852 192.168.123.130 > 192.168.123.128: icmp: echo request
21:06:05.758380 192.168.123.130 > 192.168.123.10: icmp: echo request

        The devices .123 (appliance), .4 (PC), and .20 (PC) are
not shown in the GUI. The .128 (Mac) and .10 (Printer) are shown
correctly. Maybe it's an OS detection process problem?

        The MACID's are:

.123 : 00:A0:24:3B:23:A7
.4   : 08:00:20:1A:29:4B
.20  : 00:60:1D:03:1B:2B
.128 : 00:50:E4:C0:30:34
.10  : 00:60:B0:73:63:B4

        Hope this helps. Let me know if you need to VNC into
my system to debug this.

-Scott

On Tue, 25 Jun 2002, mailbox wrote:

> Hello Scott,
> Please test bugs#1 and #2 with latest Wincvs code. I have added some code to
> it.
> (Can I get the description(IP address+MAC address) of the devices in the
> ping list(extra 5 devices) ?)
>
> Regards,
> Varsha.
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, June 24, 2002 10:07 PM
> Subject: Re: [Kaboodle-devel] Re: wincvs update
>
>
> > VK:
> >
> > > > 1. The "active list", what gets ping'd every 10 seconds, is
> > > >    not the same as what's in the GUI. In the ping list, I
> > > >    see 10 device, in my GUI I see only 5.
> > > >
> > > I cannot replicate the above bug. Please give me the more details to
> > > replicate the same.
> >
> > This is just how it acts on my WinNT box. Both Debug
> > and Release builds.
> >
> > > > 2. The PC which is running Kaboodle has a duplicate icon.
> > > >    One has the right MAC address, the other has the Kaboodle
> > > >    icon and an MAC address of all zeroes.
> > > >
> > > I cannot replicate the above bug with the latest code. Please give me
> > > the steps that need to replicate the bug and the operating system on
> > > which you tested the code
> >
> > Again, this is just WinNT. The duplicate icon comes up
> > after I hit Refresh after it settles out initially.
> >
> > > > 3. My network printer has two icons: one for the driver
> > > >    which was detected, and one for the IP address.
> > > >
> > > Here is the suggestion. While enumerating the printer drivers we can
> > > get the attribute and depending on the attribute we can add the printer
> > > drivers. If the attribute is PRINTER_ATTRIBUTE_NETWORK we simply ignore
> > > the driver. The network discovery code will add the network printer
> > > after that.
> > > Can you please suggest the better work around to this problem?
> >
> > That's a good idea. Is it possible from the driver to
> > detect what the printer's IP address is? That might help to
> > associate the two, so we can easily "detect" the Printer's Name
> > for the GUI (right now it comes up as the IP address).
> >
> > -Scott
> >
> >
> >
> >
> > -------------------------------------------------------
> > Sponsored by:
> > ThinkGeek at http://www.ThinkGeek.com/
> > _______________________________________________
> > Kaboodle-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> >
>
>



-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to