Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] How to diagnose "failure to capture" situation?

From: "Sake Blok" <sake@xxxxxxxxxx>
Date: Sat, 10 Nov 2007 20:53:21 +0100
Hi Chris,

Many Windows drivers for Wireless cards do not support the "promiscuous" mode well. Do you see any packets when you start a capture with promiscuous mode off? Of course this means you will only see broadcasts, multicasts and unicasts to/from the pc running Wireshark.

Cheers,


Sake

----- Original Message ----- From: "Chris Markle" <cmarkle@xxxxxxxxxxxxxx>
To: <wireshark-dev@xxxxxxxxxxxxx>
Sent: Friday, November 09, 2007 7:55 PM
Subject: [Wireshark-dev] How to diagnose "failure to capture" situation?


Hi folks,

I had a customer of ours install Wireshark 0.99.6a and WinPcap to help
us disgnose a networking issue involving their Windows XP system. No
matter what form of installing, uninstalling, rebooting, etc. we did,
we could not get Wireshark to capture on his wireless interface. What
I am used to seeing is when I open the Capture -> Interfaces window, I
see packet counts on active interfaces, even if capture is not
started. I see no packet counts on any of his interfaces even though
his computer is clearly connected to the internet. Then if I try to
capture on the wireless interface anyway, I see no packets captured.

What kinds of things can I do to diagnose what's going on here?

Thanks in advance.

Chris
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev