Cannot Join Domain Using Network Peripherals NP-EISA/S FDDI

 Last reviewed: November 17, 1995
Article ID: Q139732
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

When you install Windows NT Server as a backup domain controller (BDC) or set up a Windows NT Workstation to join a domain using a Network Peripherals NP-EISA/S FDDI network adapter, the following error message appears: 

   Could not find domain controller for this domain.

CAUSE

This problem occurs when a primary domain controller (PDC) and BDC are connected using a Cabletron hub using the TCP/IP protocol.

RESOLUTION

Network Peripherals has a newer driver (Npeisa.sys) for this adapter that fixes this problem. The latest driver file can be obtained from the Network Peripherals bulletin board system (BBS) at (408) 321-9322.

The third-party products discussed here are manufactured by Network Peripherals, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

KBCategory: kbhw kb3rdparty
KBSubcategory: nthw
Additional reference words: 3.51 prodnt

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: November 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.