Diagnosing errorsTo find solutions to problems that have definite symptoms,see “Error symptoms” on page 107.If you cannot find the problem there, go to “Starting thediagnostic programs” on page 15 to test the server.If you have just added new software or a new option andthe server is not working, do the following before using theerror symptoms table:v Remove the software or device that you just added.v Run the diagnostic tests to determine if the server isrunning correctly.v Reinstall the new software or new device.Troubleshooting the Ethernet controllerThis section provides troubleshooting information forproblems that might occur with the 10/100 Mbps Ethernetcontroller.Network connection problemsIf the Ethernet controller cannot connect to the network,check the following:v Make sure that the cable is installed correctly.The network cable must be securely attached at allconnections. If the cable is attached but the problempersists, try a different cable.If you set the Ethernet controller to operate at 100Mbps, you must use Category 5 cabling.If you directly connect two workstations (without a hub),or if you are not using a hub with X ports, use acrossover cable.Note: To determine whether a hub has an X port, checkthe port label. If the label contains an X, the hubhas an X port.v Determine if the hub supports auto-negotiation. If not, tryconfiguring the integrated Ethernet controller manually tomatch the speed and duplex mode of the hub.v Check the LAN activity light (if available) on the front ofthe server. The LAN activity light illuminates when theEthernet controller sends or receives data over theEthernet network. If the LAN activity light is off, makesure that the hub and network are operating and thatthe correct device drivers are loaded.v Make sure that you are using the correct device drivers,supplied with your server.Chapter 3. Diagnostics 23
