Diskless (No-Flash) Unit Troubleshooting - HP f10 Troubleshooting Manual

Table of Contents

Advertisement

Table 4-4
Power-On Troubleshooting (continued)
A newly connected unknown USB
peripheral does not respond or USB
peripherals connected prior to the newly
connected USB peripheral will not
complete their device actions.
Video does not display.

Diskless (No-Flash) Unit Troubleshooting

This section is only for those units that do not have ATA Flash capability. Because there is no ATA
Flash in this model the boot priority sequence is:
USB device
PXE
To troubleshoot the unit:
1.
When the unit boots, the monitor should display the following information:
Table 4-5
Item
MAC Address
GUID
Client ID
MASK
DHCP IP
If you are running in an MS RIS PXE environment go to step 2.
28
Chapter 4 Diagnostics and Troubleshooting
An unknown USB peripheral may be connected and disconnected to a running
platform as long as you do not reboot the system. If problems occur, disconnect
the unknown USB peripheral and reboot the platform.
1.
2.
3.
4.
Diskless Unit Troubleshooting
Information
NIC portion of the system board is
OK
General system board information
Information from server
Information from server
Information from server
Verify that the monitor brightness is set to a readable level.
Verify the monitor is good by connecting it to a known working computer
and ensure its front LED turns green (assuming the monitor is Energy Star
compliant). If the monitor is defective, replace it with a working monitor
and repeat testing.
Re-image the thin client unit and power on the monitor again.
Test the thin client unit on a known working monitor. If the monitor does
not display video, replace the thin client unit.
Action
If no MAC Address, the system board is at fault.
Contact the Call Center for service.
If no GUID information, the system board is at fault and
should be replaced.
If no Client ID information there is no network
connection. This may be caused by a bad cable, down
server, or a bad system board. Contact the Call Center
for service for the bad system board.
If no MASK information there is no network connection.
This may be caused by a bad cable, down server, or a
bad system board. Contact the Call Center for service
for the bad system board.
If no DHCP IP information there is no network
connection. This may be caused by a bad cable, down
server, or a bad system board. Contact the Call Center
for service for the bad system board.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents