This document contains late-breaking information about Microsoft Network Monitor version 2.0 Service Pack 2 functionality that is not available in the product documentation. Please read these release notes thoroughly before you install Network Monitor.
Use Support Online to search the Microsoft Knowledge Base and other technical resources for fast, accurate answers. To begin your search, go to http://www.microsoft.com/support/.
If you have comments or suggestions about Network Monitor, please send them to smswish@microsoft.com.
The Network Monitor 2.0 SP2 external setup program (located in the \NMext directory) will uninstall any previous external Network Monitor 2.0 installation it detects.
WORKAROUND: None. You cannot upgrade beta releases of Network Monitor 2.0. WORKAROUND: To install Network Monitor 2.0, use the Add/Remove Programs icon in Control Panel to first remove any previous beta versions of Network Monitor 2.0. Then, run Network Monitor Setup (as part of the SMS Setup or from the SMSsetup\Netmon\<Platform> directory on the SMS 2.0 compact disc). You must use "install mode" when installing Network Monitor on Windows 2000 computers that have Terminal Server software installed so that Network Monitor files can be written to the System32 directory. WORKAROUND: Before installing Network Monitor, type change user /install at a command prompt. You can then continue to install Network Monitor. Network Monitor setup does not automatically install Network Monitor over previous versions. WORKAROUND: To upgrade a previous version, specify that the new version be installed in the same directory as the previous version. During Network Monitor Setup, if you have the Local Area Connection properties window open, the Network Monitor drivers will not be installed and you will see an error saying that no network card was found. WORKAROUND: Use the following steps to install the required drivers:
Remove Beta Versions Before You Run Setup
Installing Network Monitor on Computers That Have Windows 2000 Server-Side Terminal Server Software Installed
Network Monitor is Not Installed Over Previous Versions
Close Local Area Connection Properties Window Before Installing Network Monitor
The Help button does not open online Help in the Select a Network dialog box on Windows 2000 computers.
WORKAROUND: To display the Help topic for the Select a Network dialog box, do the following:
There are some problems with some token-ring adapter cards.
WORKAROUND: Fully test any token-ring network adapter cards in your environment before relying on them to capture network data.
If you are using a Madge Smart 16/14 PCI Ringnode [BM] token-ring network adapter card, you must enable Traffic Statistics Gathering for that card.
WORKAROUND: To enable Traffic Statistics Gathering for a Madge Smart network adapter card that is already installed on the Windows NT 4.0 computer, do the following:
If the Madge Smart network adapter card is already installed on the Windows 2000 computer, do the following:
Do not use the driver supplied by the manufacturer for the Madge token-ring network adapter cards.
WORKAROUND: Use the driver that is made available through Windows NT 4.0 and Windows 2000 for your Madge token-ring network adapter card.
The maximum size for a capture buffer is 1024 MB. If you are creating large capture files (such as a 1024 MB capture), Windows is likely to run out of virtual memory. You can resolve part of the out of virtual memory problem by increasing the Windows paging-file swap size; however, this will not resolve the problem completely. When Windows runs low on memory, Network Monitor will continue to capture (although frames might be dropped because of slow system performance). After the capture is complete, Windows might not have enough free memory to display the large capture file.
WORKAROUND: If you want to display a large capture file, do the following:
Remote captures between SMS Network Monitor 2.0 and SMS Network Monitor 2.0 SP2 are not supported. The context in which the remote client and the Network Monitor Driver communicate was changed to fix a memory access problem.
WORKAROUND: Upgrade all installations of SMS Network Monitor 2.0 to SMS Network Monitor 2.0 SP2.
On Windows NT 4.0, the print capture function will always print the Summary pane in the default column order.
WORKAROUND: None.
The NetWare Core Protocol (NCP) burst frames are left as fragments and are not coalesced into single frame transactions as they should be.
WORKAROUND: None.
Under some conditions the Average Server Response Time expert returns incorrect averages for server time. (Instead of sorting the list of requests and discarding duplicates, all requests are saved. This situation can result in averages that are significantly inflated from the actual averages.) This problem occurs if your capture contains a lot of Server Message Block (SMB) traffic; if most of the traffic is non-SMB, the server averages are accurate. Also, the larger the capture file, the greater the inaccuracy of averages for server response time.
WORKAROUND: None.
If you capture network data sent between two computers that use a different code page than the one on your local computer, some frame data fields might not be readable in Network Monitor.
WORKAROUND: Use Network Monitor on a computer that has the same code page as the remote computers that you are targeting in your capture.
The Microsoft IntelliMouse(R) wheel does not work when you attempt to scroll in the y-axis in the Graph pane of the Capture window.
WORKAROUND: To scroll, use IntelliMouse to move the scroll box in the scroll bar.
On Windows 2000 Professional, the Administrative Tools are not displayed by default, so the Network Monitor shortcuts will not be available.
WORKAROUND: To display the shortcuts, do the following:
Some token-ring network adapter cards report that they support local-only mode, but they will not pass along functionals (a token ring named multicast).
WORKAROUND: If you notice that Security Monitor is not stopping unauthorized users from capturing, edit the registry to force the card into promiscuous mode, as follows:
The next time Network Monitor or the Monitor Control service runs, the network adapter card will run in promiscuous mode.
If you need to stop forcing promiscuous mode, do the following:
If you alter the Log On As behavior of the Monitor Control service, it will not function correctly.
WORKAROUND: Do not change the Monitor Control service settings.
If you start the computer that runs the Monitor Control Tool and it cannot reach a domain controller, when you start the Monitor Control service after logging in, your computer will not receive any monitor events. The following message appears:
"Windows Management denied us access to the database - unable to register for events."
WORKAROUND: Wait until you can reach a domain controller before you run the Monitor Control Tool.
The log file generated by Security Monitor (%netmon%\Secmon.log), which is created only if Security Monitor has been run on the local computer, is difficult to read using Microsoft Notepad.
WORKAROUND: To best view the Secmon.log file, do the following:
If the "No Network Drivers..." error message appears after you start Network Monitor, you will not be able to capture network traffic, although you can still open capture files that were created during earlier sessions of Network Monitor. The usual cause of this error message is that the Network Monitor driver (Nmnt.sys) could not be located in the %windir%\System32\Drivers directory.
WORKAROUND: To ensure that the Network Monitor Agent v2 driver is installed correctly, do the following:
Note If you change the Temporary Capture directory, you must exit and restart Network Monitor for the changes to take effect.
If you receive the "An unknown error 102 has occurred" error message in Network Monitor when you start a capture on a disconnected remote computer, the remote computer is no longer available on the network.
WORKAROUND: None.
If you attempt to connect to a remote computer that exists but that is disconnected from the network, Network Monitor might take a long time to time out.
WORKAROUND: None.
When connecting to remote computers, users should enter only the computer name. Preceeding the computer name with two backslashes (\\) is unnecessary and can cause remote connection problems.
WORKAROUND: Type computer names without preceding them with backslashes (\\).