Common Issues:

Protocols may not parse correctly in either of these two situations.

1. Conversations Not Enabled – Certain protocols depend on conversations properties to store state values that may be needed in a later frames. For instance TCP needs conversations to store information about retransmitted frames, so the filter for TCP Retransmits won’t work unless conversations are enabled. Similarly, SMB can’t translate the response to a Transact command, because the response doesn’t contain the original command. This information is also saved in conversation properties.

2. This parser and associated protocol(s) may be available under the MCPP and WSPP licensing programs; if you are interested in learning more about becoming a licensee please see:

http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx

These parsers are considered Confidential Microsoft Intellectual Property and are not distributed publicly; therefore they are not part of the publicly released version of Microsoft Network Monitor 3.1

If you get an error “None of the network adapters are bound to the Netmon driver" or “This network adapter is not configured to capture with Network Monitor", this may occur if you are running on Vista, and either NM3 is not run with elevated privileges, or you are not part of the Netmon Users group. See the release notes for more information.