VK:
Quick answer: all of the GUI's on the LAN should be
synchronized. So if I make a small change in one, that change
should propogate throughout the LAN. I am not sure at all
how well the NID synchronization part of the code does this.
-Scott
On Wed, 3 Jul 2002, mailbox wrote:
> Hello Scott,
>
> I have added the different way of finding the MAC address in code. I hope
> this will eliminate the PC icon duplication bug. Please test it with the
> latest code(without any registry settings). If it does not work at your end
> please send me the debug dump.
>
>
>
> Query:
>
> What should happen in the GUI on PC2 if I change the PC icon group position
> or any property of the PC running kaboodle on PC1?
>
>
>
> Regards,
>
> Varsha
>
>
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, July 01, 2002 9:16 PM
> Subject: Re: [Kaboodle-devel] Re: wincvs update
>
>
> > VK:
> >
> > > >From the debug dump I got that we are getting the Mac address with all
> > > zeros for the WinNT machine that is CONNECTED to the Network. What was
> > > the IP address in this case? I think we should get the MAC address if it
> > > is connected to the network. Do you what could be the reason for this
> > > kind of behavior?
> >
> > Yes: the first machine in my GUI, the primary one with
> > the Kaboodle halo, always has an all-zero MAC address. It is
> > of course connected to the network (it's the machine I'm running
> > Kaboodle on, after all). I have no idea why its MAC address is
> > wrong. I thought once that it was how Kaboodle determined which
> > device was the "Master Node" of the LAN.
> >
> > After network discovery, a second icon is added to the
> > GUI. This device has the same name as the primary device, though
> > all uppercase. This device has the same IP address (192.168.123.130)
> > but is shown with the correct MAC address.
> >
> > > I am getting the MAC address zero only if I disable the "Local area
> > > connection" on windows2000. If I just unplugged the Network cable I get
> > > the correct MAC address and IP address = 127.0.0.1.
> >
> > Strange. Maybe it's a WinNT problem?
> >
> > > I could not replicate win98 crash at my end. I unplugged network cable
> > > and started win98. (with registry and without kaboodle registry)
> >
> > I'll try it again with the latest source.
> >
> > > I have stopped the pinging in case of IP address = 127.0.0.1.
> >
> > Cool, thanks.
> >
> > -Scott
> >
> >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "mailbox" <[EMAIL PROTECTED]>
> > > Sent: Saturday, June 29, 2002 12:50 PM
> > > Subject: Re: [Kaboodle-devel] Re: wincvs update
> > >
> > >
> > > > VK:
> > > > Debug output from tonight attached.
> > > >
> > > > -Scott
> > > >
> > > > On Sat, 29 Jun 2002, mailbox wrote:
> > > >
> > > > > Hello Scott,
> > > > > I used TightVNC and tryed to connect to your vnc server. But I am
> still
> > > > > getting the error "VNC Authentication failed". with IP address
> > > 66.123.20.60
> > > > > and password "scott02".
> > > > > Thanks,
> > > > > Varsha
> > > > > ----- Original Message -----
> > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > To: "mailbox" <[EMAIL PROTECTED]>
> > > > > Sent: Friday, June 28, 2002 9:17 PM
> > > > > Subject: Re: [Kaboodle-devel] Re: wincvs update
> > > > >
> > > > >
> > > > > > VK:
> > > > > > Strange. The log file doesn't show anything obvious.
> > > > > > I've change the color-depth to 16-bit instead of 24-bit, but
> > > > > > I doubt that's the problem. Exactly what error are you seeing?
> > > > > > Also, try using the TightVNC client instead of the WinVNC one.
> > > > > > They behave differently sometimes over little errors.
> > > > > >
> > > > > > -Scott
> > > > > >
> > > > > > On Fri, 28 Jun 2002, mailbox wrote:
> > > > > >
> > > > > > > Hello Scott,
> > > > > > > I am still getting the same error. I have tested from two diff
> ISP
> > > > > > > providers. What could be the problem? Does VNC server need any
> other
> > > > > > > settings?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Varsha
> > > > > > > ----- Original Message -----
> > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > To: "mailbox" <[EMAIL PROTECTED]>
> > > > > > > Sent: Friday, June 28, 2002 10:51 AM
> > > > > > > Subject: Re: [Kaboodle-devel] Re: wincvs update
> > > > > > >
> > > > > > >
> > > > > > > > VK:
> > > > > > > > Just tested with that password. Please note it's
> > > > > > > > all lowercase, with the number zero and two.
> > > > > > > >
> > > > > > > > -Scott
> > > > > > > >
> > > > > > > > On Wed, 26 Jun 2002, Scott C. Best wrote:
> > > > > > > >
> > > > > > > > > VK:
> > > > > > > > > IP address is 66.123.20.60, password is "scott02".
> > > > > > > > > Directory is F:\Echogent\Kaboodle\test which should be
> > > > > > > > > what you see as soon as you connect. You'll also see
> > > > > > > > > that Kaboodle runs pretty slowly over VNC. :)
> > > > > > > > >
> > > > > > > > > -Scott
> > > > > > > > >
> > > > > > > > > On Wed, 26 Jun 2002, mailbox wrote:
> > > > > > > > >
> > > > > > > > > > Hello Scott,
> > > > > > > > > > I think VNC into your system will really help me in
> debugging
> > > the
> > > > > > > problem.
> > > > > > > > > > Can you give me the required information for VNC and the
> > > folder in
> > > > > > > which I
> > > > > > > > > > can work?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Varsha.
> > > > > > > > > >
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > To: "mailbox" <[EMAIL PROTECTED]>
> > > > > > > > > > Cc: <[EMAIL PROTECTED]>
> > > > > > > > > > Sent: Wednesday, June 26, 2002 1:36 AM
> > > > > > > > > > Subject: Re: [Kaboodle-devel] Re: wincvs update
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Kaboodle-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> >
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
