Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Chris Markle" <cmarkle@xxxxxxxxxxxxxx>
Date: Fri, 9 Nov 2007 10:55:45 -0800

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

  • Follow-Ups:
    • Re: [Wireshark-dev] How to diagnose "failure to capture" situation?
      • From: Sake Blok
  • Prev by Date: Re: [Wireshark-dev] Create a new tvb from a bit offset in the currenttvb
  • Next by Date: Re: [Wireshark-dev] 0.99.7 release?
  • Previous by thread: [Wireshark-dev] [ANNOUNCE] WinPcap 4.0.2 has been released
  • Next by thread: Re: [Wireshark-dev] How to diagnose "failure to capture" situation?
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation