Ethernet Adapter  (260-5505/A/B)   Troubleshooting      Faxback Doc. # 5617

CHECK FOR THE OBVIOUS

1. Make sure that the adapter is completely seated in the computer expansion
   slot, and no cables inside the computer were pulled loose when you
   installed the adapter.

2. Verify that the network cable is securely attached to either the BNC or
   AUI port.

3. Verify that 50 Ohm cable terminators are installed as required. Terminators
   must be 50 Ohm impedance (within 2%) or errors may occur. Terminators are
   installed at both ends of every cable segment.

4. Make sure the interconnecting cables meet IEEE standard requirements.

5. Check the cable connection to other computers. In an Ethernet network
   using thin cable, check the computers that are daisy-chained to the
   computer you are troubleshooting. If you are using thick cable, check the
   drop cable connection at the transceiver.

6. Check jumper W3 on the adapter and verify that the correct network port
   (BNC or AUI) is selected.

7. If a ROM device is installed on the adapter, verify the ROM device is
   correct for the computer system and network software you are using. Make
   sure that every pin on the ROM device is seated firmly in the socket.

8. Make sure that you copied any required software drivers from the driver
   diskette as instructed in the documentation included with your networking
   software.

TROUBLESHOOTING PROCEDURE

1. Determine whether or not your workstation is the only one in the network
   that is not functioning.
   A. If other workstations are also affected, the source of the problem is
      the cabling or file server. Skip steps 2 - 5, and go to step 6.
   B. If your workstation is the only one affected, the problem is probably
      in the hardware or in the software of the adapter you just installed.

2. Run the diagnostic program to further isolate the problem. This program
   is located in the subdirectory <DIAGNOSE> on the driver diskette. The
   USER.DOC file, also in this subdirectory, tells you how to operate the
   diagnostic program.
   A. If the diagnostic basic adapter test passes, the hardware is probably
      operating properly.
   B. If the test fails, the most common hardware problem is that another
      device conflicts with the Ethernet adapter.

3. Before attempting to resolve a configuration conflict, review the section in the
   manual on avoiding configuration conflicts. Also review the SYSMAP.DOC
   file on the software driver diskette for up-to-date information on the
   normal configuration settings of all boards.
     A. Once you have done this, choose another configuration for your
        Ethernet adapter.
     B. If after reviewing the configuration information and trying alternate
        configurations, the basic adapter test still fails, call for
        technical assistance.

4. If the problem is not the hardware, you know it's the software.
   A. If you are using a driver other than Novell NetWare, call for technical
      assistance.
   B. If you are using Novell NetWare, type the following at the DOS prompt:

              IPX I

         This enables you to verify that --

    * The driver you are using is appropriate for the type of adapter you
      have.
    * The driver is the latest version.

 5. If running IPX I does not uncover a problem, call for technical
     assistance.

 6. To determine whether the problem is the cabling or the file server, run
    the diagnostic program using remote loopback between the two nodes.
     A. If the remote loopback test passes without errors, the problem is
        probably the file server, not the cabling.
     B. If the test fails, the problem is probably the cabling.

 7. If you think you have a cabling problem, try splitting segments to
    isolate the cable defect, or replace the cable with one known to be good.

 8. If the problem appears to be the file server, check the installation of
    the network software, and make sure that the server is properly attached
    to the network and that it is operational.

(DTC/jlc-03/28/94)