You can use "windump -D" command to know what problems happened when opening the
adaptors.
flying72
----- Original Message -----
From:<[EMAIL PROTECTED]>
To:<[EMAIL PROTECTED]>
Subject:Re: [WinPcap-users] PacketGetAdapterNames fills first 4 bytes to zero
Date:Thu, 7 Nov 2002 15:13:51 +0800
> Hi,
>
> What is a reason why all adapters can not be opened ? Is it a bug or a
> feature? How to crack this problem ?
>
> Yours sincerely,
> Alex Bash
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, November 07, 2002 4:03 AM
> Subject: RE: [WinPcap-users] PacketGetAdapterNames fills first 4 bytes to
> zero
>
>
> > When all adpters can not be opened, this scenario (the first 4 bytes
> filled with 0 then all adapters'descriptions) happens.
> >
> > Cheers
> >
> > ----- Original Message -----
> > From:<[EMAIL PROTECTED]>
> > To:<[EMAIL PROTECTED]>
> > Subject:[WinPcap-users] PacketGetAdapterNames fills first 4 bytes to zero
> > Date:Thu, 7 Nov 2002 01:48:06 +0800
> > > Hi WinPcap-users!
> > >
> > > I wrote to this maillist about problem with detecting adapters under
> Windows
> > > 2000 Terminal Server. I did not solve my problem and have yet one. I
> have
> > > Windows 2000 Advanced Terminal Server Domain Controller Service Pack 3
> > > build=2195 (Number of CPU: 1). Two similar nics INTEL pro Adapter.
> WinPcap
> > > 3.0 alpha 4, admin rights, reboot...
> > >
> > > PacketGetAdapterNames returns nothing... :( I see a buffer after a call
> of
> > > PacketAdapterNames. It seems that it contains true data about adapters
> > > installed but the first 4 bytes are zero. As result, WinPcap can't
> detect
> > > adapters. Here is the dump of buffer filled by PacketGetAdapterNames
> (first
> > > 20 bytes):
> > >
> > > 00 00 00 00 65 00 76 00 69 00 63 00 65 00 5c 00 4e 00 50 00
> > >
> > > I performed a trace of PacketGetAdapterNames and got the follows:
> > >
> > > PacketGetAdapterNames: BufferSize=4096
> > > Need 654 bytes for the names
> > > PacketGetAdapterNames: Cycling through the adapters:
> > > 1) UpperBind=CV2K1 Name = Device{5073D02F-890A-4D3E-BD1B-CB8B40A490B6}
> > > 2) UpperBind=CV2K1 Name = Device{F0B8A138-01F9-48D1-BE79-C2E8627DA559}
> > > 3) UpperBind=NdisWan Name =
> Device{2F96A8B0-BDFE-4FEB-A368-57B108C45DED}
> > > 4) UpperBind=NdisWan Name =
> Device{03F6799B-A623-4E14-8A28-1B7D0E6A5969}
> > > 5) UpperBind=NdisWan Name =
> Device{E33166A0-20DE-44AA-9EEF-5AE6CEE4E2DD}
> > > 6) UpperBind=NdisWan Name =
> Device{06A1EC07-4425-49C9-AE33-7C736478C2C8}
> > > 7) UpperBind=Tcpip Name = DeviceNdisWanIp
> > > 8) UpperBind=NM Name = DeviceNdisWanBh
> > > PacketGetAdapterNames: ended correctly
>
>
>
>
>
> ==================================================================
> This is the WinPcap users list. It is archived at
> http://www.mail-archive.com/winpcap-users@;winpcap.polito.it/
>
> To unsubscribe use
> mailto: [EMAIL PROTECTED]?body=unsubscribe
> ==================================================================
>
>
______________________________________
===================================================================
==================================================================
This is the WinPcap users list. It is archived at
http://www.mail-archive.com/winpcap-users@;winpcap.polito.it/
To unsubscribe use
mailto: [EMAIL PROTECTED]?body=unsubscribe
==================================================================
