[Steve Hill <ethereal@xxxxxxxxxxxx>]

Guy Harris wrote:

> > Does anyone have a troubleshooting scenario that I can use to
> > diagnose, and then fix, this problem?
>
>
> Diagnose?  Yes, the above shows how to diagnose it, but you have to be 
> unafraid to run WinPcap from the command line.
>
> Fix?  Maybe, maybe not - it's almost certainly a WinPcap problem 
> rather than an  Ethereal problem, and WinPcap problems might be 
> problems with the underlying network adapter driver and/or NDIS, and 
> neither we nor the Winpcap developers have source to those drivers or 
> to Windows 2000.
>
> The WinPcap developers are probably more likely to know why a WinPcap 
> problem such as that would occur, which is why, if it's a WinPcap 
> problem (i.e., if WinDump can't handle the interface, either), that 
> FAQ suggests contacting them. 

I have downloaded WinPcap3.01a (and 3.00 before that).  I double-clicked 
the file, and it appeared to load properly.  It DOES show up in my 
installed software. 

However, when I executed "windump -D", I received 
"PacketGetAdapterNames: The operation completed successfully."  But no 
adapter names were listed. 

I then executed msinfo32, drilled down to Software Environment then 
Drivers, and I see under "npf" that its state is stopped.

Can anyone see what I am doing wrong?  Or have suggestions for further 
inquiry?

Steve