WinPcap does not show in the list of protocols of the NIC. Do the NICs get
listed in Wireshark?
Have a nice day
GV
--------------------------------------------------
From: <mike@xxxxxxxxxxxx>
Sent: Thursday, May 13, 2010 4:47 PM
To: "wireshark-users" <wireshark-users@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-users] One NIC on public side
The installer definitely said it was installing it but I don't see it
anywhere. Maybe I'll re-install and see what happens.
On Thu, 13 May 2010 16:32:50 -0700, Gianluca Varenni wrote:
Did you install WinPcap? WinPcap must be installed in order to capture.
Do
the NICs get listed in wireshark?
GV
--------------------------------------------------
From: <mike@xxxxxxxxxxxx>
Sent: Thursday, May 13, 2010 4:30 PM
To: "wireshark-users" <wireshark-users@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-users] One NIC on public side
Ok, just noticed that on new system, after installing wireshark, there
are
no capture protocols on either nic. Guess that's a lead.
On Thu, 13 May 2010 11:43:23 -0500, mike@xxxxxxxxxxxx wrote:
Just wanting to understand what I'm doing. Always good to learn rather
than
simply being told :).
MS client gets disabled if you disable TCP/IP. QoS can be disabled as
well.
The network monitors can be left on.
Because it is a netbios based service, which rides on tcp/ip?
You are disabling TCP/IP on the public NIC. The LAN NIC will have its
own
IP
address, the public one will not. As far as "safely connect" is
concerned,
it depends on what you mean by "safely".
Yes, the server has two NICs. I have one connected on the LAN side for
server admin, etc, the other is connected to a hub which has the WAN
connections coming into it, just before the firewall. I want to see
what
hits us before the firewall does anything with it. It helps a lot when
trying to figure out various problems.
What do I mean by safely? Meaning that public cannot gain access to the
server in some way. I mean, the setup bypasses the firewall so sure
don't
want someone being able to gain access into the lan somehow.
___________________________________________________________________________
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
___________________________________________________________________________
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
___________________________________________________________________________
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
