Thanks! Great idea.
Another obvious thing I should have already tried and posted about is trying it under a Linux boot CD tshark / tcpdump.. just not had a chance to burn & try yet.
That would rule out any 'diabled in the chip' type of suspicions.
And then there's trying in on Win32 instead of x64 as well *sigh* :-)
Steve Gladden
Michigan Broadband Systems
Connecting Your Business!
+1 734.527.7150 Direct
+1 248.327.4389 Fax
steve@xxxxxxxxxxxxxxxxxxxxx
www.michiganbroadband.com
-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Wednesday, January 25, 2012 2:32 PM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] Wireshark-users] Nvidia MCP onboard wired 10/100/1000 NIC
On Jan 25, 2012, at 10:18 AM, Steve Gladden wrote:
> I have an open ticket with Gigabyte (no useful reply yet).
>
> And also have an email out to nicfae@xxxxxxxxxxx with my questions regarding promiscuous mode in Win7 64bit with WinPcap and Wireshark.
Just out of curiosity, try downloading Microsoft Network Monitor:
http://www.microsoft.com/download/en/details.aspx?id=4865
and see if *it* can capture in promiscuous mode. If not (as I suspect will be the case), then if they blame it on WinPcap (it's not an issue with Wireshark - Wireshark 100% relies on libpcap/WinPcap to handle packet capture, so any other program using WinPcap, such as WinDump, will have the same issue), tell them that it also doesn't work with Microsoft Network Monitor (which means it's probably a problem either with their hardware or with their driver).
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
