Table 8-11 Solving Network Problems (continued)
Network controller stops working without apparent cause.
Cause Solution
The cable is not securely connected. Ensure that the cable is securely attached to the network
connector and that the other end of the cable is securely
attached to the correct device.
The network controller is defective. Contact an authorized service provider.
New network card will not boot.
Cause Solution
New network card may be defective or may not meet
industry-standard specifications.
Install a working, industry-standard NIC, or change the boot
sequence to boot from another source.
Cannot connect to network server when attempting Remote System Installation.
Cause Solution
The network controller is not configured properly. Verify Network Connectivity, that a DHCP Server is present,
and that the Remote System Installation Server contains the
NIC drivers for your NIC.
System setup utility reports unprogrammed EEPROM.
Cause Solution
Unprogrammed EEPROM. Contact an authorized service provider.
Solving Memory Problems
If you encounter memory problems, some common causes and solutions are listed in the following
table.
CAUTION: Power may still be supplied to the DIMMs when the computer is turned off (depending
on the Management Engine (ME) settings). To avoid damage to the DIMMs or the system board, you
must unplug the computer power cord before attempting to reseat, install, or remove a memory
module.
For those systems that support ECC memory, HP does not support mixing ECC and non-ECC
memory. Otherwise, the computer will not boot the operating system.
NOTE: The memory count will be affected by configurations with the Management Engine (ME)
enabled. The ME uses 8MB of system memory in single channel mode or 16MB of memory in dual-
channel mode to download, decompress, and execute the ME firmware for Out-of-Band (OOB), third-
party data storage, and other management functions.
166 Chapter 8 Troubleshooting Without Diagnostics
To Next Page
Loading...
Need help?
General