[Winpcap-users] windows7, wireshark2.2.3, winpcap 4.1.3, int2 not visible on wireshark windows7
Mark Pizzolato - Winpcap-Users
winpcap-users-20040408 at subscriptions.pizzolato.net
Thu Jan 19 18:57:05 UTC 2017
Manolis’ problem was due to the addition of a new network interface AFTER the
WinPap facilities had gathered the list of known interfaces. This list is gathered
when the NPF service starts, so a reboot would have solved the problem, or the
uninstall/reinstall does it since that stops on uninstall and starts it again on the
subsequent install. Alternatively he could have explicitly stop and start the NPF
service to also have the list of interfaces reacquired. The commands to do this
(from an elevated command prompt) are:
net stop npf
net start npf
I would also suggest trying Npcap.
From: winpcap-users-bounces at winpcap.org [mailto:winpcap-users-bounces at winpcap.org] On Behalf Of Daniel Miller
Sent: Thursday, January 19, 2017 10:49 AM
To: winpcap-users at winpcap.org
Subject: Re: [Winpcap-users] windows7, wireshark2.2.3, winpcap 4.1.3, int2 not visible on wireshark windows7
Npcap is a currently-maintained update/fork of the unmaintained WinPcap source. Does the problem still happen if you install the latest Npcap from https://github.com/nmap/npcap/releases/latest ?
On Fri, Jan 13, 2017 at 3:04 PM, Manolis Katsidoniotis <manoska at gmail.com<mailto:manoska at gmail.com>> wrote:
remove-reinstall winpcap 4.1.3 resolved my problem.
2nd interface became visible in wireshark.
If there is a way to trigger winpcap to see the interface without re-install let me know.
On Fri, Jan 13, 2017 at 2:33 PM Manolis Katsidoniotis <manoska at gmail.com<mailto:manoska at gmail.com>> wrote:
My apologies if something similar to this has been posted in the past.
I have a widnows7 installation logging in as user belonging in group Administrators
Wireshark2.2.3/ winpcap 4.1.3 were installed when only 1 card was present.
Added a 2nd one afterwards, configured IPs, it is visible to the system ad I can ping the IP but it is not visible in wireshak.
Went through wireshark help I read somewhere that it is a winpcap issue.
Any ideas on how I can cause winpcap to see the 2nd interface? (something like rescan the network?)
Winpcap-users mailing list
Winpcap-users at winpcap.org<mailto:Winpcap-users at winpcap.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Winpcap-users