3Com Corporation
    EtherDisk Diskette for the EtherLink III LAN+Modem PC Card
                     Troubleshooting



 If the adapter diagnostic tests fail, the adapter might not be
 defective. Check the following:

 1. Make sure that the adapter is operating in a computer
    containing the Personal Computer Memory Card International
    Association (PCMCIA) Release 2.01, Type II or Type III slots.

 2. Make sure that the adapter is completely seated in its slot.
    Review the installation instructions in the appropriate
    adapter guide.

 3. Make sure that your computer is running DOS 3.1 or higher
    and that no device drivers or memory managers are loaded.

 4. Inspect all cables and connections.

 5. If you are running the Network Loopback test, make sure
    that the adapter (coax only) is securely connected to a 
    loopback plug or to a properly cabled network.

 6. If you are running the Echo Server test, make sure that the
    adapter is securely connected to a properly cabled network
    and an echo server is set up on the network.

 7. If you are configuring the I/O base address or interrupt
    request level make sure that the settings you choose for
    these parameters do not conflict with any other peripheral
    or software program installed in the computer.  

 8. Make sure that the configuration setting for the transceiver
    type is correct.

 9. Running the Network Loopback test (coax only) while
    connected to an active network can cause intermittent
    failures.  These failures can be avoided by using a
    loopback plug or by connecting to an inactive network on
    which only the computer being tested is operating.

10. The computer in which the adapter is installed might be
    defective.  Install the adapter in a known functioning
    computer and run the tests again.

11. The loopback plug you are using might be defective.  Try a
    different loopback plug.

12. Replace the failed adapter with a known working adapter,
    with the same configuration.  If the second adapter fails,
    something is probably wrong with the test environment, not
    with the adapter.


         (%VER  Troubleshooting v2.1e)