Solving Ethernet controller problems
The method that you use to test the Ethernet controller depends on which operating system you are using. For information about Ethernet controllers, see the Ethernet controller device-driver readme file and the operating-system documentation.
Try the following procedures:
- Make sure that the correct device drivers, which come with the server, are installed and that they are at the latest level.
- Make sure that the Ethernet cable is installed correctly.
- The cable must be securely attached at all connections. If the cable is attached but the problem remains, try a different cable.
- If you set the Ethernet controller to operate at 100 Mbps, you must use Category 5 cabling.
- If you directly connect two servers (without a hub), or if you are not using a hub with X ports, use a crossover cable. To determine whether a hub has an X port, check the port label. If the label contains an X, the hub has an X port.
- Determine whether the hub supports auto-negotiation. If it does not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub.
- Check the Ethernet controller LEDs on the rear panel of the server. These LEDs indicate whether there is a problem with the connector, cable, or hub.
- The Ethernet link status LED is lit when the Ethernet controller receives a link pulse from the hub. If the LED is off, there might be a defective connector or cable or a problem with the hub.
- The Ethernet transmit/receive activity LED is lit when the Ethernet controller sends or receives data over the Ethernet network. If the Ethernet transmit/receive activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed.
- Check the LAN activity LED on the rear of the server. The LAN activity LED is lit when data is active on the Ethernet network. If the LAN activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed.
- Check for operating-system-specific causes of the problem.
- Make sure that the device drivers on the client and server are using the same protocol.
If the Ethernet controller still cannot connect to the network but the hardware appears to be working, the network administrator must investigate other possible causes of the error.