This is sort of related to the other thread, "Another administrative problem", but not quite.
One of our test machines, a single CPU Windows 2000 Server, which has WinPcap installed and was used succesfully about 2 weeks ago can no longer see any network devices in WinPcap even when logged in as _the_ local machine's Administrator user. We've tried rebooting and running our app as Administrator immediately ater reboot without any change. We're going to try uninstalling and reinstalling with reboots inbetween. I've used the debug version of packet.dll and WinDump and attached the generated debug files to this message (the reg files are in winpcap_debug_reg.zip). Thanks, Gordon Sitraka -- the Java advantage http://www.sitraka.com/
winpcap_debug_reg.zip
Description: Zip compressed data
************Packet32: DllMain************
PacketGetAdapterNames: BufferSize=8192
Need 558 bytes for the names
PacketGetAdapterNames: Cycling through the adapters:
1) UpperBind=NM Name = \Device\{1D754D47-FBB1-4474-B5A4-623FBB120EEB}
2) UpperBind=NdisWan Name = SKIPPED
3) UpperBind=NdisWan Name = SKIPPED
4) UpperBind=NdisWan Name = SKIPPED
5) UpperBind=NdisWan Name = SKIPPED
6) UpperBind=Tcpip Name = \Device\NdisWanIp
7) UpperBind=NM Name = \Device\NdisWanBh
Dumping BpStr:
\ D e v i c e \ { 1 D 7 5 4 D 4
7 - F B B 1 - 4 4 7 4 - B 5 A 4
- 6 2 3 F B B 1 2 0 E E B } \
D e v i c e \ N d i s W a n I p
\ D e v i c e \ N d i s W a n
B h
PacketOpenAdapter: trying to open the
adapter=\Device\Packet_{1D754D47-FBB1-4474-B5A4-623FBB120EEB}
The status of the driver is:4
PacketOpenAdapter: CreateFile failed, Error=2,2
PacketOpenAdapter: trying to open the adapter=\Device\Packet_NdisWanIp
The status of the driver is:4
PacketOpenAdapter: CreateFile failed, Error=2,2
PacketOpenAdapter: trying to open the adapter=\Device\Packet_NdisWanBh
The status of the driver is:4
PacketOpenAdapter: CreateFile failed, Error=2,2
PacketGetAdapterNames: ended correctly
