[Winpcap-users] Problem with PacketGetAdapterNames
Gonze Didier
Didier.Gonze at thomson.net
Fri Jun 23 07:29:17 GMT 2006
Loris,
I have just installed WinPcap 3.0: It works perfectly as with Ethereal
as with the WinDump version 3.8 alpha (it seems the latest WinDump
version is not compatible with WinPcap 3.0)
For the moment, it solve my problem
I just hope that there is no feature on latest WinPcap that I need for
the capture.
Thanks
> -----Original Message-----
> From: winpcap-users-bounces at winpcap.org [mailto:winpcap-users-
> bounces at winpcap.org] On Behalf Of Loris Degioanni
> Sent: woensdag 21 juni 2006 17:40
> To: winpcap-users at winpcap.org
> Subject: Re: [Winpcap-users] Problem with PacketGetAdapterNames
>
> Gonze Didier wrote:
>
> > Using Ethereal I was receiving the following message:
> >
> >
> >
> > Can't get list of interfaces: PacketGetAdapterNames: There are no
more
> > files. (18)
> >
> >
> >
> > From the Ethereal site I've read the advice to try with WinDump in
> > order to see if the problem was linked with Ethereal or WinPCap:
> >
> >
> >
> > Running WinDump.exe -D I receive the first time as expected the name
of
> > the interface:
> >
> >
> >
> > /1.\Device\NPF_GenericDialupAdapter (Generic dialup adapter)/
> >
> > /2.\Device\NPF_{2ADF974F-F3C9-48FF-97E2-3C261938FA9A} (Dell
draadloze
> > 1350 WLAN Mini-PCI kaart (Microsoft's Packet Sche/
> >
> > /duler) )/
> >
> > /3.\Device\NPF_{889EBB8E-FD12-4D35-AB19-BF61DF1BCA73} (NOC Extranet
> > Access Adapter (Microsoft's Packet Scheduler) )/
> >
> > /4.\Device\NPF_{EA1435B5-323F-40A0-A2EA-DEB99F70041F} (Broadcom
> > NetXtreme Gigabit Ethernet Driver (Microsoft's Packet S/
> >
> > /cheduler) )/
> >
> >
> >
> > The second time all the interfaces are gone but I receive a message
that
> > the command is correctly applied:
> >
> >
> >
> > WinDump.exe: PacketGetAdapterNames: The operation completed
> > successfully. (0)
> >
> >
> >
> > This test is done with WinPCap 3.1
> >
> > Only after a reboot of the PC I receive back the correct interface.
> >
> >
> >
> > My conclusion is thus that the problem is located in WinPCap
> >
> >
> >
> > The Ethereal test were done with 3.1, 3.1 beta4 and 4.0 alpha1.
> >
> > My guess: is that the problem has been introduced when I've go from
> > WinPCap 3.0 to WinPCap 3.1 beta4 but now when I install WinPCap 3.1
> > there is still some part of the the beta version which are not
> uninstalled
> >
>
> So was it working with WinPcap 3.0?
>
> Loris
>
> >
> >
> >
> > Can you help me?
> >
> >
> >
> >
> >
> >
> >
> > Didier Gonze
> >
> > Project Management
> >
> > AP&G DSL R&D
> >
> >
> >
> > Mobile: +32 495586640
> >
> > Fixed: +32 3 4436609
> >
> >
> >
> > Prins Boudewijnlaan 47
> >
> > 2650 Edegem
> >
> > Belgium
> >
> >
> >
> >
> >
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Winpcap-users mailing list
> > Winpcap-users at winpcap.org
> > https://www.winpcap.org/mailman/listinfo/winpcap-users
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
More information about the Winpcap-users
mailing list