Hello,

Thanks for all the information

Le 11/04/2019 à 17:04, Hittner, David T [US] (MS) a écrit :
Due to subtle differences in Windows drivers, sometimes WinPcap can't see a NIC unless it 
has an IP address assigned to it (or some other protocol - that is, that the NIC should 
appear to be "active" to the host). Also, certain version of WinPcap had issues 
adding NICs, and the solution was to remove WinPcap and re-install it to allow the 
installation procedure to generate the correct registry entries for the new NIC during 
the installation.
I'll try that.
...
Gordon Lyon, Nmap project founder, has created Npcap, a packet capture library 
for Windows, that includes WinPcap compatibility and may be a suitable 
replacement for WinPcap and WinPcap Pro. Information can be found at 
https://nmap.org/npcap/.
Is Npcap compatible with simh?


-----Original Message-----
From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of gérard Calliet
Sent: Thursday, April 11, 2019 5:15 AM
To: simh@trailing-edge.com
Subject: EXT :Re: [Simh] winpcap problem

Hello,

I used the recommended tool windump -D and it doesn't see the new NICs.
So it is a pure problem of compatibility between Winpcap and the new NICs.

Did anyone see a similar problem? Are there somewhere WinPcap gurus?

Gérard Calliet


Le 11/04/2019 à 09:42, gérard Calliet a écrit :
Hello,

I tried a reboot of the host. Same problem. Is it possible there are
NICs not compatible with WinPcap? or some bizarre configuration to do
on the NIC?

Gérard Calliet

Le 05/04/2019 à 02:19, Mark Pizzolato a écrit :
On Tuesday, April 2, 2019 at 1:42 PM, gérard Calliet wrote:
I have some trouble using winpcap (on windows) with simh.

I added a NIC (intel ethernet server adapter i350-t2), I can see it
on the windows configuration panel, but I don't see it using simh
"sho eth"
command, which uses winpcap (version 4.1.3). The other NICs are seen
by the same command.

Any help?
Winpcap has a problem with detecting newly installed network devices
that weren't present when the system was booted.  Try rebooting the
system and see if you continue to see the same problem.

- Mark
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Reply via email to