[Winpcap-users] Problem with PacketGetAdapterNames

[madhumitha b]

 Hi 

I am facing the same problem with Winpcap version 4.1.2
We have an in house application called Kiwi which in turn uses Winpcap to do the 
packet capture and analysis.
When using WinDump -D we are not getting the interface names.

C:\>WinDump.exe -D
1.\Device\NPF_GenericDialupAdapter (Adapter for generic dialup and VPN capture)

Only on restarting the PC we are getting the interface names.


C:\>WinDump.exe -D
1.\Device\NPF_GenericDialupAdapter (Adapter for generic dialup and VPN capture)
2.\Device\NPF_{A0D77CD6-8AD0-47AF-9023-71DD593B76F7} (Broadcom NetXtreme Gigabit 
Ethernet Driver)
3.\Device\NPF_{2D8A942E-B2F4-4A19-B1E1-ED56DEF9B266} (Intel(R) PRO/1000 MF Dual 
Port Server Adapter)

4.\Device\NPF_{B3A59ED5-4661-4229-A13F-B1FCD00BAB0A} (Intel(R) PRO/1000 MF Dual 
Port Server Adapter)

5.\Device\NPF_{FF7C098A-EC52-4075-9B9A-B1EE1185EB34} (Intel(R) PRO/1000 MF Dual 
Port Server Adapter)

6.\Device\NPF_{F226B76F-5A9A-4DAB-9329-EE25F3A44B9E} (Intel(R) PRO/1000 MF Dual 
Port Server Adapter)

7.\Device\NPF_{C063208D-21BC-4E86-BB83-5F5728640862} (Broadcom NetXtreme Gigabit 
Ethernet Driver)


Can any one help me in resolving this issue?
Because of this the in house tool kiwi which has to get memory allocated from 
the kernel of winpcap is not getting enough memory and throwing the 
error."Failed to open adapter : driver error: not enough memory to allocate the 
kernelbuffer "



Thanks and Regards
Madhumitha



> -----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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20100908/436c48ed/attachment.htm