


Of course, if there is no network virtualization, then you can skip this part.

Identify various network devices and network connectionsīecause network virtualization will add many virtual network devices (including virtual network cards) to the physical machine, the situation will become complicated, so first we need to distinguish them. So you will need to filter the network capture to see only the related traffic. However, your interest is only to look into the traffic/packets that are related to the specific connectivity problem you are facing. The saved file has captured all the traffic that is flowing to and from the selected network adapters on the local computer. By default, the file will be saved as a ".cap" file. Select Stop, and go to File > Save as to save the results. Reproduce the issue, and you will see that Network Monitor grabs the packets on the wire. Select the network adapters where you want to capture traffic, click New Capture, and then click Start. Network Monitor opens with all network adapters displayed. Run netmon in an elevated status by choosing Run as Administrator. When the driver gets hooked to the network interface card (NIC) during installation, the NIC is reinitialized, which might cause a brief network glitch. You can see the same on the adapter properties, as shown in the following image: When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. To get started, download Network Monitor tool. For more details, see Microsoft Message Analyzer Operating Guide. Microsoft Message Analyzer is the replacement for Network Monitor. Network Monitor is the archived protocol analyzer and is no longer under development.
