Hello Scott.
I implemented iterating via list all network's interfaces.
In my test I see that now Kaboodle receives all LAN devices
if PC has two network cards also.
But Kaboodle thinks that above devices *isn't valid*
(in some inner context)
and don't pushes them into the NID data.
Please see strings like following
* CSearchNetworkManager::StartPing - entry 0
(MAC address 00-e0-18-0b-23-f7, IP address 192.168.1.225)
removed because of: dwIndex != interfaceIndex *
in my attachment NidLog.txt.
Kaboodle needs changes in the implementation of
the class CSearchNetworkManager.
Till now the class CSearchNetworkManager expects
that there is a single network's interface only.
It seems to me that author of the class CSearchNetworkManager
is better person, who can make above implementation.
(I didn't see any comments for that class in the source code.)
All my source code changes in that part have directives
#ifdef _ITERATE_ALL_INTERFACES
- Igor
----- Original Message -----
From: "Igor Kotelevsky" <[EMAIL PROTECTED]>
To: "Scott C. Best" <[EMAIL PROTECTED]>
Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
Sent: Wednesday, August 28, 2002 2:20 PM
Subject: Re: [Kaboodle-devel] Re: Bug Report, 22 July (invalid subnet mask?)
> Hello Scott.
> You wrote:
> > For each, if the IP address of the interface is the same as the
> > IP address of the default gateway (or if either of these two IP
> > address is 0.0.0.0 or undefined) Kaboodle should ignore that
> > interface.
> In my test (the PC has single network card) I see following
> IP addresses of interfaces:
> - 192.168.1.2 - default gateway,
> - 127.0.0.1,
> - 192.168.1.134 - my PC IP address.
> It seems to me that there need little changing of your sounds:
> iterate list of all IP addresses of interfaces, except:
> - IP address of my PC,
> - loopback address "127.0.0.1",
> - empty address "0.0.0.0".
> I'll try to do above changes.
>
> - Igor
>
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> Sent: Wednesday, August 28, 2002 8:49 AM
> Subject: Re: [Kaboodle-devel] Re: Bug Report, 22 July (invalid subnet
mask?)
>
>
> > Igor:
> > If I understand you correctly, I think situation #2 below
> > is the bug I'm trying to describe.
> >
> > Here's how Kaboodle should act: it should iterate thru
> > the list of *all* interfaces. Not just the first one, and not just
> > the one with a /24 subnet mask. It should iterate thru all of them.
> > For each, if the IP address of the interface is the same as the
> > IP address of the default gateway (or if either of these two IP
> > address is 0.0.0.0 or undefined) Kaboodle should ignore that
> > interface. For any remaining interfaces, Kaboodle should run the
> > network discovery process.
> >
> > -Scott
> >
> > On Tue, 27 Aug 2002, Igor Kotelevsky wrote:
> >
> > > Hello Scott.
> > > I completed next test:
> > > a) OS Win2kPro,
> > > b) I installed second network card into the my PC,
> > > c) I connected my PC to LAN via second card,
> > > d) I used next "Local Area Connection" properties
> > > for "Internet Protocol (TCP/IP)":
> > > - obtain an IP address automatically,
> > > - obtain DNS server address automatically,
> > > e) I cleared Kaboodle registry setting on my PC,
> > > f) I started Kaboodle on my PC.
> > > Here is what I see:
> > >
> > > 1 - Kaboodle checks that LAN isn't empty.
> > > Please see into the log file NidLog.txt.
> > > I found next string in that file
> > > - CheckLan::CheckIsLan() - find other device <DEVLIN>,
> > > the default gateway is <192.168.1.2>
> > > It is my special debug log string, which belong to the
> > > a WinApi function WNetEnumResource.
> > > Please repeat that test and let me know if your NidLog.txt log file
> > > doesn't contains that string.
> > > (I attached my NidLog.txt log file.)
> > >
> > > 2 - Kaboodle doesn't checks any device in my LAN.
> > > I prompted next command line - ipconfig /all.
> > > (I attached my ipconfig_all.txt file.)
> > > There is following interesting string:
> > > - Subnet Mask.........: 255.255.0.0
> > > It seems like Windows automatically assign that mask.
> > > I didn't familiar with
> > > current Kaboodle's LAN detection procedure in details.
> > > But as I know Kaboodle expects that LAN has next subnet mask
> 255.255.255.0.
> > > It seems to me that above *INVALID SUBNET MASK* is the reason
> > > of bug for my test.
> > >
> > > - Igor
> > >
> > >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>; "Aryeh
> > > Goretsky" <[EMAIL PROTECTED]>
> > > Sent: Sunday, August 25, 2002 6:35 AM
> > > Subject: Re: [Kaboodle-devel] Re: Bug Report, 22 July
> > >
> > >
> > > > Igor:
> > > > Hello again. Okay, it has nothing to do with the
> > > > installation of an AOL client or not. But try this: install
> > > > two network cards into the same PC. Set them both up to get
> > > > their IP address via DHCP. Connect one of them to your LAN,
> > > > leave the other floating, see if Kaboodle works from a clean
> > > > install. If it does, switch the cables (connect the 2nd,
> > > > leave the first floating), then try it.
> > > >
> > > > I suspect that one of these arrangments will break
> > > > Kaboodle's ability to detect the network. My customer today
> > > > had a USB LAN adapter disconnected and that must be what
> > > > was confusing things (I saw the 169.x.y.z IP address, from
> > > > a failed DHCP request, in the 'route print' list).
> > > >
> > > > Aryeh:
> > > > Have you a PC to test this on?
> > > >
> > > > -Scott
> > > >
> > > > PS: I updated the background tiles today. I think they look
> > > > better.
> > > >
> > > >
> > > > On Sat, 24 Aug 2002, Scott C. Best wrote:
> > > >
> > > > > Igor:
> > > > >
> > > > > Hello! Just found out today that this existing solution
> > > > > doesn't completely work.
> > > > >
> > > > > I was working on a customer's ethernet network, and I
> > > > > installed Kaboodle on a Win2kPro PC. This PC had an AOL client
> > > > > installed on it, which they use to connect to AOL via the LAN
> > > > > connection. So I start Kaboodle, and it skips the LAN-detection
> > > > > completely. I am going to install an AOL client on my WinNT
> > > > > PC and see if I can see the same effect.
> > > > >
> > > > > We need to fix this. Kaboodle needs to evaluate all of
> > > > > the TCP/IP interfaces, and skip all of the ones where the IP
> > > > > address of the interface and the default gateway are the same.
> > > > >
> > > > > -Scott
> > > > >
> > > > >
> > > > > On Fri, 2 Aug 2002, Igor Kotelevsky wrote:
> > > > >
> > > > > > Hello Scott.
> > > > > > You wrote:
> > > > > > > ...could you implement a check so that Kaboodle skipped the
> > > > > > LAN-detection...
> > > > > > > if it detected that the IP address of the interface matches
the
> IP
> > > address
> > > > > > of the default gateway.
> > > > > > I'll think how it can be implemented.
> > > > > >
> > > > > > Now I have following proposition.
> > > > > > Kaboodle can use a WinApi function WNetEnumResource (please see
> MSDN).
> > > > > > If that function finds any network resource, then Kaboodle skips
> the
> > > > > > LAN-detection.
> > > > > > That proposition has implemented.
> > > > > > Please CVS update and check it.
> > > > > > If you'll want remove it, please comment out a macros
> > > > > > #define _USE_CHECK_LAN
> > > > > > from the file stdafx.h.
> > > > > > - Igor
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
> > > > > > <[EMAIL PROTECTED]>
> > > > > > Sent: Friday, August 02, 2002 1:44 AM
> > > > > > Subject: Re: [Kaboodle-devel] Re: Bug Report, 22 July
> > > > > >
> > > > > >
> > > > > > > Igor:
> > > > > > > Heya. As per the data I found today, could you implement
> > > > > > > a check so that Kaboodle skipped the LAN-detection (and hence
> the
> > > > > > > OS classification) process if it detected that the IP address
of
> > > > > > > the interface matches the IP address of the default gateway.
> > > > > > > This might be the best way, for now, of Kaboodle surviving an
> > > > > > > AOL-dialup setting.
> > > > > > >
> > > > > > > Once you get that check done, I think we can release
> > > > > > > a 0.90 version publically.
> > > > > > >
> > > > > > > I'm also interested in what you think Kaboodle should
> > > > > > > do if it detects it has more than one active LAN interface.
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > -Scott
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 1 Aug 2002, Igor Kotelevsky wrote:
> > > > > > >
> > > > > > > > Hello Scott.
> > > > > > > > You wrote:
> > > > > > > > > ... It lessens
> > > > > > > > > Kaboodle's effectiveness as a network scanner if something
> > > joined
> > > > > > > > > the LAN and could somehow dodge Kaboodle's detection by
> causing
> > > > > > > > > an exception during OS detection and then hiding as a
> > > EF_NID_NONE.
> > > > > > > > I restored old code of the function AutoDetectDeviceType()
> > > > > > > > without *try-catch* block.
> > > > > > > > If any exception will occur at that function,
> > > > > > > > then there isn't a way for both
> > > > > > > > defending against exception and
> > > > > > > > don't hiding a device as an EF_NID_NONE.
> > > > > > > > - Igor
> > > > > > > >
> > > > > > > >
> > > > > > > > ----- Original Message -----
> > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
> > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > Sent: Wednesday, July 31, 2002 9:27 PM
> > > > > > > > Subject: Re: [Kaboodle-devel] Re: Bug Report, 22 July
> > > > > > > >
> > > > > > > >
> > > > > > > > > Igor:
> > > > > > > > > Will re-run shortly. A quick comment or two:
> > > > > > > > >
> > > > > > > > > > The really reason of that crash is unknown for me yet,
> > > > > > > > > > but I think that we have to defend Kaboodle against
that.
> > > > > > > > > > Therefore I have inserted a *try-catch* block into the
> > > function
> > > > > > > > > > DWORD CSearchNetworkManager::AutoDetectDeviceType(...).
> > > > > > > > > > If any exception will occur, and *try-catch* block can
> > > intercept it,
> > > > > > > > > > then that function will return EF_NID_NONE
> > > > > > > > > > and Kaboodle doesn't will add that device into itself.
> > > > > > > > > > (Old source code of AutoDetectDeviceType(...) is
> commented.)
> > > > > > > > >
> > > > > > > > > Hmmm. I like defending against exceptions, but I like
> > > > > > > > > being able to detect all network devices as well. It
lessens
> > > > > > > > > Kaboodle's effectiveness as a network scanner if something
> > > joined
> > > > > > > > > the LAN and could somehow dodge Kaboodle's detection by
> causing
> > > > > > > > > an exception during OS detection and then hiding as a
> > > EF_NID_NONE.
> > > > > > > > >
> > > > > > > > > There's *got* to be a way to detect what interfaces a PC
> > > > > > > > > is using, and to prevent Kaboodle from running
> auto-detection on
> > > > > > > > > the WAN-side interface.
> > > > > > > > >
> > > > > > > > > > Also I want to notice following.
> > > > > > > > > > The function AutoDetectDeviceType(...) checks type of
> device
> > > > > > > > > > in following sequence: PC, Printer, Macintosh,
Appliance.
> > > > > > > > > > If all these checks failed, then the function returns
the
> type
> > > > > > > > EF_NID_PC.
> > > > > > > > > > May be in this point the function have to return
> EF_NID_NONE?
> > > > > > > > >
> > > > > > > > > No, it needs to default to EF_NID_PC. The PC detection is
> > > > > > > > > really just "Windows detection". If I'm running a *nix
> machine
> > > (Linux,
> > > > > > > > > Solaris, BSD, etc), I want the PC icon to come up.
> > > > > > > > >
> > > > > > > > > -Scott
> > > > > > > > >
> > > > > > > > > > > Igor:
> > > > > > > > > > > Updated, re-run, log files attached. Again, it looks
> > > > > > > > > > > like its crashing after successfully discovering
> something
> > > on
> > > > > > > > > > > the same subnet. Weird.
> > > > > > > > > > >
> > > > > > > > > > > -Scott
> > > > > > > > > > >
> > > > > > > > > > > On Tue, 30 Jul 2002, Igor Kotelevsky wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > The log file WithAOL\NidLog.txt (connection via AOL
> and
> > > crash)
> > > > > > > > > > > > shows following.
> > > > > > > > > > > > The latest 3 strings are next:
> > > > > > > > > > > > - StartOSDetection: BEGIN
> > > > > > > > > > > > - AutoDetectDeviceType: BEGIN
> > > > > > > > > > > > - AutoDetectDeviceType: 172.194.188.224
> > > > > > > > > > > > It seems to me that crash has occurred
> > > > > > > > > > > > - inwardly to the function
> > > > > > > > > > > > DWORD
> CSearchNetworkManager::AutoDetectDeviceType(...), or
> > > > > > > > > > > > - inwardly to some function, which called from
> > > > > > > > AutoDetectDeviceType().
> > > > > > > > > > > > (The log process is made so that if function ends
then
> we
> > > see
> > > > > > > > something
> > > > > > > > > > > > like
> > > > > > > > > > > > - AutoDetectDeviceType: BEGIN
> > > > > > > > > > > > ...
> > > > > > > > > > > > - AutoDetectDeviceType: END)
> > > > > > > > > > > > I have added enhanced information into the file
> > > NidLog.txt.
> > > > > > > > > > > > Please update latest CVS source and run Kaboodle in
> debug
> > > build.
> > > > > > > > > > > > Please send to me NidLog.txt.
> > > > > > > > > > > >
> > > > > > > > > > > > You wrote:
> > > > > > > > > > > > > ...Perhaps the OS detection process is not being
> > > bypassed
> > > > > > > > correctly?
> > > > > > > > > > > > Yes. From above log file I see, that OS detection
> process
> > > starts
> > > > > > in
> > > > > > > > case
> > > > > > > > > > of
> > > > > > > > > > > > connection via AOL.
> > > > > > > > > > > > I didn't found Kaboodle's source code, which detect
a
> > > modem.
> > > > > > > > > > > > Now I don't know as to detect a modem.
> > > > > > > > > > > > I'll try to search that.
> > > > > > > > > > > > - Igor
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > > > > Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
> > > > > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > Sent: Tuesday, July 30, 2002 8:44 AM
> > > > > > > > > > > > Subject: Re: Bug Report, 22 July
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > Hello! I ran the latest CVS code in debug mode on
my
> > > > > > > > > > > > > Win98 laptop. It crashed whenever I ran it with
AOL
> > > connected.
> > > > > > > > > > > > > The attached zipfile has three log file sets in
> there.
> > > > > > > > > > > > > One with no-AOL and no-LAN connection (no crash),
> one
> > > with
> > > > > > > > > > > > > a LAN connection (no crash) and one with AOL
> (crash).
> > > The AOL
> > > > > > > > > > > > > case looks like it does in fact start running OS
> > > detection.
> > > > > > > > > > > > > I know we agreed that the network detection
process
> > > > > > > > > > > > > should be bypassed when Kaboodle connects to the
> > > Internet via
> > > > > > > > > > > > > a modem. Perhaps the OS detection process is not
> being
> > > > > > bypassed
> > > > > > > > > > > > > correctly?
> > > > > > > > > > > > >
> > > > > > > > > > > > > -Scott
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, 29 Jul 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > I don't found any information about error.
> > > > > > > > > > > > > > Please update latest CVS source and run Kaboodle
> in
> > > debug
> > > > > > build.
> > > > > > > > > > > > > > You will find new log file - NidLog.txt.
> > > > > > > > > > > > > > Please send that file to me.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The log files vpnsocket1.txt, vpnsocket2.txt now
> > > generate in
> > > > > > > > > > Kaboodle
> > > > > > > > > > > > > > install directory.
> > > > > > > > > > > > > > That files appeared in pre-Akmosoft period.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > To: "Igor Kotelevsky"
> <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > Cc: "mailbox" <[EMAIL PROTECTED]>;
> "Kaboodle-devel"
> > > > > > > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > Sent: Friday, July 26, 2002 8:32 PM
> > > > > > > > > > > > > > Subject: Re: Bug Report, 22 July
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > The Kaboodle log files are attached. I didn't
> even
> > > > > > > > > > > > > > > know Kaboodle was generating these. :) Can we
> write
> > > them
> > > > > > > > > > > > > > > into the Kaboodle install directory instead of
> C:\.?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Please let me know what progress you make on
> this
> > > > > > > > > > > > > > > error source. It's holding up the public
release
> of
> > > 0.90.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, 26 Jul 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > The output files you have attached were
really
> > > short.
> > > > > > > > > > > > > > > > Please attach the Kaboodle's log files
> > > vpnsocket1.txt,
> > > > > > > > > > > > vpnsocket2.txt.
> > > > > > > > > > > > > > > > You can find these files in the directory
C:\.
> > > > > > > > > > > > > > > > Please remove these files before your test.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The description of "A fatal exception OE"
can
> be
> > > finding
> > > > > > on
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > >
> > >
>
http://support.microsoft.com/default.aspx?scid=/support/windows/topics/error
> > > > > > > > > > > > > > > > msg/kbfe0e.asp
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > To: "mailbox" <[EMAIL PROTECTED]>;
> > > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > Sent: Friday, July 26, 2002 10:57 AM
> > > > > > > > > > > > > > > > Subject: Re: Bug Report, 22 July
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > VK, Igor:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I tested this again tonight. I installed
> VC++ on
> > > my
> > > > > > > > > > > > > > > > > poor little Win98 laptop, applied the
latest
> SP5
> > > > > > service
> > > > > > > > pack.
> > > > > > > > > > > > > > > > > I compiled the latest source, connected to
> AOL,
> > > and
> > > > > > > > started
> > > > > > > > > > > > > > > > > the debug. Output attached (I don't know
why
> > > it's so
> > > > > > > > short,
> > > > > > > > > > > > > > > > > but it is).
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Kaboodle starts, and the "Detecting
Network"
> > > message
> > > > > > > > > > > > > > > > > box comes up. At this point, in my
opinion,
> it
> > > should
> > > > > > > > detect
> > > > > > > > > > > > > > > > > that it's on a modem and give up. It
> doesn't.
> > > About
> > > > > > half a
> > > > > > > > > > > > > > > > > minute later, "Classifying New Devices"
> comes
> > > up.
> > > > > > About 10
> > > > > > > > > > > > > > > > > seconds later, Windows then blue screens
> with
> > > the
> > > > > > message:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > "A fatal exception OE has occurred at
> > > 0028:C004A08B in
> > > > > > VXD
> > > > > > > > > > > > NDIS(01) +
> > > > > > > > > > > > > > > > > 00002F1F. The current application will be
> > > terminated."
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > The second time I tried this, the debug
> output
> > > looks
> > > > > > > > > > > > > > > > > like it started the VNC auto-detection
> before it
> > > > > > crashed.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Any advice appreciated.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Mon, 22 Jul 2002, Scott C. Best wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I tested Kaboodle on a un-networked
Win98
> > > machine
> > > > > > which
> > > > > > > > > > > > > > > > > > uses AOL as the dialup ISP. I connected
to
> > > AOL, then
> > > > > > > > started
> > > > > > > > > > > > > > > > > > Kaboodle, and it blue-screen'd the PC
when
> it
> > > got to
> > > > > > the
> > > > > > > > > > > > > > > > > > "Classifying Devices" part of startup.
> > > > > > > > > > > > > > > > > > Ouch.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Is it possible to restrict network
> detection
> > > to use
> > > > > > only
> > > > > > > > > > > > > > > > > > LAN-based interfaces, as opposed to
> > > > > > modem-interfaces? I
> > > > > > > > > > can't
> > > > > > > > > > > > > > > > > > imagine that we'd ever want to ping 255
> > > devices on
> > > > > > one
> > > > > > > > of
> > > > > > > > > > AOL's
> > > > > > > > > > > > > > > > > > subnets...
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -------------------------------------------------------
> > > > > > > > > > This sf.net email is sponsored by: Dice - The leading
> online
> > > job
> > > > > > board
> > > > > > > > > > for high-tech professionals. Search and apply for tech
> jobs
> > > today!
> > > > > > > > > > http://seeker.dice.com/seeker.epl?rel_code=31
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Kaboodle-devel mailing list
> > > > > > > > > > [EMAIL PROTECTED]
> > > > > > > > > >
> https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > This sf.net email is sponsored by: OSDN - Tired of that same old
> > > > > cell phone? Get a new here for FREE!
> > > > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > > > > _______________________________________________
> > > > > Kaboodle-devel mailing list
> > > > > [EMAIL PROTECTED]
> > > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
CheckLan::CheckIsLan() - find other device <DEVLIN>, the default gateway is
<192.168.1.2>
CNetworkLocalView::RebuildNIDTopology( 0 ) device count 10 [entry 0]
Receive device #0 <WS19's Network>, m_nType 1 <EF_NID_NETWORK>
- identifier <{0cfe8bbe-d90c-48fd-a8fb-3219ac2575be}>
- m_nFlags 1 ( DEVICE_CONNECTED )
- m_dwStatus 0
Receive device #1 <WS19>, m_nType 2 <EF_NID_PC>
- identifier <{0189fb02-aba1-45e2-b307-de922ac62aa7}>
- m_nFlags c1 ( DEVICE_CONNECTED | PC_RUNNING | PC_RUNNINGKABOODLE )
- m_dwStatus 0
- MAC address <00-40-95-02-05-2c>
- IP address <169.254.132.217>
Receive device #2 <Services>, m_nType 7 <EF_GROUP>
- identifier <{b33d94af-7cb3-452a-bcf6-6088a06f78b5}>
- m_nFlags 0
- m_dwStatus 0
Receive device #3 <PCs>, m_nType 7 <EF_GROUP>
- identifier <{92041a75-aadc-4790-b208-25721b38a53b}>
- m_nFlags 0
- m_dwStatus 0
Receive device #4 <Macs>, m_nType 7 <EF_GROUP>
- identifier <{4b3dc6d8-a1cb-4470-8073-3978be46d1c6}>
- m_nFlags 0
- m_dwStatus 0
Receive device #5 <Printers>, m_nType 7 <EF_GROUP>
- identifier <{b21199ff-face-4063-8bd3-8a5622b82b19}>
- m_nFlags 0
- m_dwStatus 0
Receive device #6 <Appliances>, m_nType 7 <EF_GROUP>
- identifier <{774824c6-20ff-4d46-a626-6f9cc943367c}>
- m_nFlags 0
- m_dwStatus 0
Receive device #7 <VNC>, m_nType 5 <EF_NID_SERVICE>
- identifier <{eb4b0a63-da86-4000-ad5b-278cd8e1df93}>
- m_nFlags 0
- m_dwStatus 0
Receive device #8 <VPN>, m_nType 5 <EF_NID_SERVICE>
- identifier <{d5beef2b-aedd-4adc-a778-9f5b84a1178a}>
- m_nFlags 0
- m_dwStatus 0
Receive device #9 <File Transfer>, m_nType 5 <EF_NID_SERVICE>
- identifier <{bc2f588c-58fe-4314-bf99-b3ba71d8bdd1}>
- m_nFlags 0
- m_dwStatus 0
CNetworkLocalView::RebuildNIDTopology - finish add device
<<<StartPing: BEGIN( 1 )>>>
StartPing: PING_ALL
StartPing: point 1
StartPing: point 2
StartPing: AfxIsValidAddress - OK
StartPing: point 3
CSearchNetworkManager::StartPing - iterate 2 interfaces
CSearchNetworkManager::StartPing - ping IP 192.168.1.(192.168.1.2), interface 0
CNetworkLocalView::RebuildNIDTopology( 0 ) device count 10 [entry 1]
Receive device #0 <WS19's Network>, m_nType 1 <EF_NID_NETWORK>
- identifier <{0cfe8bbe-d90c-48fd-a8fb-3219ac2575be}>
- m_nFlags 1 ( DEVICE_CONNECTED )
- m_dwStatus 0
Receive device #1 <WS19>, m_nType 2 <EF_NID_PC>
- identifier <{0189fb02-aba1-45e2-b307-de922ac62aa7}>
- m_nFlags c1 ( DEVICE_CONNECTED | PC_RUNNING | PC_RUNNINGKABOODLE )
- m_dwStatus 0
- MAC address <00-40-95-02-05-2c>
- IP address <169.254.132.217>
Receive device #2 <Services>, m_nType 7 <EF_GROUP>
- identifier <{b33d94af-7cb3-452a-bcf6-6088a06f78b5}>
- m_nFlags 0
- m_dwStatus 0
Receive device #3 <PCs>, m_nType 7 <EF_GROUP>
- identifier <{92041a75-aadc-4790-b208-25721b38a53b}>
- m_nFlags 0
- m_dwStatus 0
Receive device #4 <Macs>, m_nType 7 <EF_GROUP>
- identifier <{4b3dc6d8-a1cb-4470-8073-3978be46d1c6}>
- m_nFlags 0
- m_dwStatus 0
Receive device #5 <Printers>, m_nType 7 <EF_GROUP>
- identifier <{b21199ff-face-4063-8bd3-8a5622b82b19}>
- m_nFlags 0
- m_dwStatus 0
Receive device #6 <Appliances>, m_nType 7 <EF_GROUP>
- identifier <{774824c6-20ff-4d46-a626-6f9cc943367c}>
- m_nFlags 0
- m_dwStatus 0
Receive device #7 <VNC>, m_nType 5 <EF_NID_SERVICE>
- identifier <{eb4b0a63-da86-4000-ad5b-278cd8e1df93}>
- m_nFlags 0
- m_dwStatus 0
Receive device #8 <VPN>, m_nType 5 <EF_NID_SERVICE>
- identifier <{d5beef2b-aedd-4adc-a778-9f5b84a1178a}>
- m_nFlags 0
- m_dwStatus 0
Receive device #9 <File Transfer>, m_nType 5 <EF_NID_SERVICE>
- identifier <{bc2f588c-58fe-4314-bf99-b3ba71d8bdd1}>
- m_nFlags 0
- m_dwStatus 0
CNetworkLocalView::RebuildNIDTopology - finish add device
CSearchNetworkManager::StartPing - ping IP 192.168.1.(192.168.1.239), interface 1
CSearchNetworkManager::StartPing - receive 16 entries
CSearchNetworkManager::StartPing - entry 0, bValid 1, MAC address 00-e0-18-0b-23-f7,
IP address 192.168.1.225
CSearchNetworkManager::StartPing - entry 0(MAC address 00-e0-18-0b-23-f7, IP address
192.168.1.225) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 1, bValid 1, MAC address 00-e0-18-25-0f-2b,
IP address 192.168.1.1
CSearchNetworkManager::StartPing - entry 1(MAC address 00-e0-18-25-0f-2b, IP address
192.168.1.1) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 2, bValid 1, MAC address 00-c0-df-f6-ce-a0,
IP address 192.168.1.226
CSearchNetworkManager::StartPing - entry 2(MAC address 00-c0-df-f6-ce-a0, IP address
192.168.1.226) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 3, bValid 1, MAC address 00-c0-df-f6-66-ca,
IP address 192.168.1.2
CSearchNetworkManager::StartPing - entry 3(MAC address 00-c0-df-f6-66-ca, IP address
192.168.1.2) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 4, bValid 1, MAC address 00-c0-df-f5-ee-ba,
IP address 192.168.1.3
CSearchNetworkManager::StartPing - entry 4(MAC address 00-c0-df-f5-ee-ba, IP address
192.168.1.3) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 5, bValid 1, MAC address 00-c0-df-f5-50-cd,
IP address 192.168.1.228
CSearchNetworkManager::StartPing - entry 5(MAC address 00-c0-df-f5-50-cd, IP address
192.168.1.228) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 6, bValid 1, MAC address 00-e0-18-3a-d8-f7,
IP address 192.168.1.5
CSearchNetworkManager::StartPing - entry 6(MAC address 00-e0-18-3a-d8-f7, IP address
192.168.1.5) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 7, bValid 1, MAC address 00-c0-26-a4-8d-60,
IP address 192.168.1.231
CSearchNetworkManager::StartPing - entry 7(MAC address 00-c0-26-a4-8d-60, IP address
192.168.1.231) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 8, bValid 1, MAC address 00-c0-26-a2-6c-d6,
IP address 192.168.1.201
CSearchNetworkManager::StartPing - entry 8(MAC address 00-c0-26-a2-6c-d6, IP address
192.168.1.201) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 9, bValid 1, MAC address 00-c0-26-a4-bd-36,
IP address 192.168.1.10
CSearchNetworkManager::StartPing - entry 9(MAC address 00-c0-26-a4-bd-36, IP address
192.168.1.10) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 10, bValid 1, MAC address 00-c0-26-31-09-07,
IP address 192.168.1.138
CSearchNetworkManager::StartPing - entry 10(MAC address 00-c0-26-31-09-07, IP address
192.168.1.138) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 11, bValid 1, MAC address 00-a0-24-9a-23-2b,
IP address 192.168.1.11
CSearchNetworkManager::StartPing - entry 11(MAC address 00-a0-24-9a-23-2b, IP address
192.168.1.11) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 12, bValid 1, MAC address 00-e0-18-25-0f-66,
IP address 192.168.1.205
CSearchNetworkManager::StartPing - entry 12(MAC address 00-e0-18-25-0f-66, IP address
192.168.1.205) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 13, bValid 1, MAC address 00-c0-26-a2-5e-e9,
IP address 192.168.1.111
CSearchNetworkManager::StartPing - entry 13(MAC address 00-c0-26-a2-5e-e9, IP address
192.168.1.111) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 14, bValid 1, MAC address 00-e0-18-25-0f-66,
IP address 192.168.1.240
CSearchNetworkManager::StartPing - entry 14(MAC address 00-e0-18-25-0f-66, IP address
192.168.1.240) removed because of: dwIndex != interfaceIndex
CSearchNetworkManager::StartPing - entry 15, bValid 1, MAC address 00-04-76-8f-26-c6,
IP address 192.168.1.19
CSearchNetworkManager::StartPing - entry 15(MAC address 00-04-76-8f-26-c6, IP address
192.168.1.19) removed because of: dwIndex != interfaceIndex
<<<StartOSDetection: BEGIN( 2 )>>>
<<<StartOSDetection: END( 2 )>>>
<<<StartPing: END( 2 )>>>
