[Winpcap-users] windows7, wireshark2.2.3, winpcap 4.1.3, int2 not visible on wireshark windows7
Daniel Miller
bonsaiviking+winpcap at gmail.com
Thu Jan 19 18:48:39 UTC 2017
Manolis,
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 ?
Dan
On Fri, Jan 13, 2017 at 3:04 PM, Manolis Katsidoniotis <manoska at gmail.com>
wrote:
> Hello
>
> Update
> 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.
>
> Thanks
> Manolis
>
> On Fri, Jan 13, 2017 at 2:33 PM Manolis Katsidoniotis <manoska at gmail.com>
> wrote:
>
>> Hello
>>
>> 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?)
>>
>> thanks
>> Manolis
>>
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20170119/bf8215fb/attachment.html>
More information about the Winpcap-users
mailing list