SMS Network Monitor

This page details problems and issues relating to Network Monitor.

Are there any Tutorials on using Network Monitor? [9/8/02]
Capturing Packets from Remote Subnets [19/6/02]
CPU utilisation goes to 100% when using Server Response Time Expert [9/1/01]
Network Monitor doesn't Capture all Network traffic [2/7/01]
Why is Promiscuous Mode Not Working On My Windows 2000 Server? [28/4/03]

Are there any Tutorials on using Network Monitor?

Contributed By: Cliff Hobbs [MVP SMS]
Network Monitor (especially the "full" version that ships with SMS 2.0) is a very handy utility, but can be a difficult to get to grips with. So here's a couple of links to some tutorials help you out ... [Go to article]

Capturing Packets from Remote Subnets

Contributed By: Cliff Hobbs [MVP SMS]
There are a few "gotcha's" when using Network Monitor to capture packets from remote subnets as detailed in this article... [Go to article]

CPU utilisation goes to 100% when using Server Response Time Expert

Whenever I do a large network capture using the Network Monitor Server Response Time Expert, it takes a very long time to complete and my CPU utilisation goes to 100%.

Contributed By: Cliff Hobbs [MVP SMS]
There is a known problem when using either the Server Response Time expert or the TCP Retransmit expert in Network Monitor version 5.00.943 as detailed in Knowledge Base Article 254644 'SMS: Network Monitor Experts Increase CPU Utilization and Finish Slowly.'

Network Monitor doesn't Capture all Network traffic

I've got a Client-Server application that isn't functioning properly and I need to monitor the network traffic (TCP/IP) between the server (Proprietary) and the client (Windows 98). SMS's Network Monitor isn't capturing this traffic. I thought this version of Network Monitor was supposed capture all network traffic.

Contributed By: Ed Wilson (author of "Network Monitoring and Analysis: a protocol approach to troubleshooting"):

If you are in a switched environment, then Network monitor will not show all of the traffic. However, if you are only interested in the traffic between the server, and the client then if you are running netmon on the server, then it will show all of that particular conversation.

In addition, you can create a filter that will only collect that traffic. If this is not possible, then consider placing the client and the server into a hub (for testing purposes) and then run netmon on your laptop or whatever in the same hub. If however, you have a switch and you are not running netmon on the server, or the client talking to the server, then you will not be able to collect all of the traffic from a workstation.

Why is Promiscuous Mode Not Working On My Windows 2000 Server?

From the microsoft.public.sms.netmon newsgroup
If you're wondering why Network Monitor is only picking up local traffic even though the properties of the card show 'PMode' to be 'true' then here's why... [Go to article]