Duplicate Locally Administered Address Can Cause Event 9006

 Last reviewed: July 24, 1996
Article ID: Q121070
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

If a locally administered address that you assign to a token ring adapter, is a duplicate of an address already in use by another station on the ring, you may find numerous errors in the Event Viewer System Log you restart Windows NT. The first error you see may be similar to this: 

   Event 9006:  Nbf could not find adapter \Device\IbmTok01
In this case, the token ring adapter driver does not produce an error; in fact, it appears to load properly. An error is not logged until NBF tries to bind to the adapter. You can alleviate all of this by eliminating the address conflict.

Additional reference words: prodnt 3.10
KBCategory: kbnetwork
KBSubcategory: ntdriver ntnetserv

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 24, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.