HP (Hewlett-Packard) ML100 Server User Manual


 
Printe
1. Be sure the printer is powered up and online.
exist.
led.
Printer tp
Action
Mouse and keyboard problems
1. itching device is in use, be sure the
d be sure the switch is correctly
2.
p
3.
5. er restarts.
equivalent device (another similar mouse or keyboard).
o If the problem still occurs with the new mouse or keyboard, the connector port on the system I/O
tive. Replace the board.
o If the problem no longer occurs, the original input device is defective. Replace the device.
eyboard or mouse is connected to the correct port. Determine whether the keyboard
lights flash at POST or the NumLock LED illuminates. If not, change port connections.
ure the keyboard or mouse is clean.
Mode
al tone exists
odem documentation.
e company and
r problems
Printer does not print
Action:
2. Be sure no loose connections (on page 50)
3. Be sure the correct printer drivers are instal
ou ut is garbled
: Be sure the correct printer drivers are installed.
Action:
Be sure no loose connections (on page 50) exist. If a KVM sw
server is properly connected to the switch.
o For rack-mounted servers, check the cables to the switch box an
set for the server.
o For tower model servers, check the cable connection from the input device to the server.
If a KVM switching device is in use, be sure all cables and connectors are the proper length and are
su ported by the switch. Refer to the switch documentation.
Be sure the current drivers for the operating system are installed.
4. Be sure the device driver is not corrupted by replacing the driver.
Restart the system and check whether the input device functions correctly after the serv
6. Replace the device with a known working
board is defec
7. Be sure the k
Be s8.
m problems
No di
Action:
1. Be sure the cables are plugged in as specified in the m
2. Connect a working telephone directly to the wall jack, and then test the line for a dial tone.
3. If no dial tone is detected, the phone line is not working. Contact the local telephon
arrange to correct the problem.
Troubleshooting 75