Cannot Capture Outbound Frames with Network Monitor 2 on a Token Ring Network (264715)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q264715 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
You may not be able to use Network Monitor version 2 to capture outbound frames from the local computer on your Token Ring network. This problem exists because of the following conditions:
- Network Monitor 2 cannot force a network adapter into Promiscuous mode.
- Some Token Ring network adapters must be forced into Promiscuous mode to allow the capturing of local outbound traffic.
CAUSE
The ForcePmode (Force Promiscuous Mode) registry setting was removed from Network Monitor 2.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix for Service Pack 2 should have the following file attributes or later:
Date Time Version Size File name
-----------------------------------------------------
11-Oct-2000 05:01 5.0.2195.2228 161,680 Ndis.sys
The English version of this fix for Service Pack 3 should have the following file attributes or later:
Date Time Version Size File Name
-----------------------------------------------------
13-Feb-2001 19:33 5.0.2195.3253 161,680 Ndis.sys
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbnetwork kbWin2000PreSP2Fix kbWin2000PreSP3Fix kbWin2000sp3fix KB264715 |
---|
|