Igor:
I'm sorry, I'm unfamiliar with MSDN terminology. What
counts as a "network resource"? If I'm connected to a LAN via
an ethernet card, what would WNetEnumResource return? If I'm
connected with a modem to AOL, what would WNetEnumResource
return?
Thanks.
-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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
