3Com EtherLink II Card Not Detected During Setup of WFWG

 Last reviewed: November 21, 1994
Article ID: Q92771
The information in this article applies to:
  • Microsoft Windows for Workgroups versions 3.1, 3.11

SUMMARY

When you run the Windows for Workgroups (WFWG) Setup program, the 3Com EtherLink II network card may not be detected if the card is not initialized or if it is using an input/output (I/O) address of 0300h.

NOTE: The network card will be initialized if you load a network software driver, such as IPX.COM, to your system.

If the card is not detected, you must set it up up manually when you run the Setup program or you must use the Network option in the Windows Control Panel after the setup is complete.

MORE INFORMATION

The Windows for Workgroups Setup program sets the transceiver type to external, regardless of the actual transceiver setting. The transceiver location is determined by the type of network cabling you are using:

  • Thin Ethernet networks and twisted-pair networks (in the case of the EtherLink II TP card) use the transceiver located on the EtherLink II card.
  • Thick Ethernet networks use an external transceiver with the 3Com Etherlink II cards.

To change the transceiver location for a 3Com card:

  1. In the Windows Control Panel, choose the Network icon.

  2. Select the Adapters option and select Advanced.

The default setting for the 3Com Etherlink II cards is External. If you are using thin Ethernet or twisted pair, change this setting to Onboard.

NOTE: If you run Windows for Workgroups with Novell NetWare connectivity on a network that has thick EtherNet cabling, you may receive the following error message: 

   A File Server Could Not Be Found
This type of cable, also known as thicknet or 10Base5, uses external transceivers. Many network adapter cards need to be properly configured to use this cable. To configure your network properly:

  1. Run Control Panel.

  2. Select the Networks option.

  3. Choose Adapters, and select External transceiver.

For example, a 3COM Etherlink II netcard must have the transceiver set to External to attach to a Netware server, otherwise the error message appears.

KBCategory: kbnetwork kb3rdparty kbhw
KBSubcategory: win31 wfw wfwg
Additional reference words: 1.0 1.00 3.1 3.10 LAN Manager LANman elink
3.11 elinkii elinkii.DOS

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 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.