HP t505 Administrator Guide 7 - Page 79

Troubleshooting, Troubleshooting network connectivity, Troubleshooting firmware corruption, corruption

Page 79 highlights

13 Troubleshooting This chapter discusses the following topics: ● Troubleshooting network connectivity ● Troubleshooting firmware corruption ● Troubleshooting Citrix password expiration ● Using system diagnostics to troubleshoot Troubleshooting network connectivity 1. Ping the desired server by doing the following: a. Click the System Information button on the taskbar, and then click on the Net Tools tab. b. Under Select Tool, select Ping. c. In the Target Host box, type the server address, and then click Start Process. If the ping is successful, the system will display the following output: PING 10.30.8.52 (10.30.8.52) 56(84) bytes of data. 64 bytes from 10.30.8.52: icmp_seq-1 ttl=64 time=0.81 5 ms 64 bytes from 10.30.8.52: icmp_seq=2 ttl=64 time=0.735 ms If the ping is unsuccessful, the thin client might be disconnected from the network and experience a long delay with no system output. 2. If the thin client does not respond to the ping, do the following: a. Check the network cable and check the network settings in the Control Panel. b. Try pinging other servers or thin clients. c. If you can reach other thin clients, verify that you typed the correct server address. d. Ping the server using the IP address instead of the domain name or vice-versa. 3. Check the system logs by doing the following: a. Click the System Information button on the taskbar, and then click on the System Logs tab. b. Check for any errors in the logs. c. If there is an error, then the Server is not set up notification appears. Verify that the server is set up properly and that HP Smart Client Services is running. Troubleshooting firmware corruption If the thin client beeps two times after it is powered on or does not appear to boot, then the device firmware may be corrupt. It is possible to resolve this by downloading the thin client image from http://www.hp.com, copying the image to a removable USB flash drive, and then booting the thin client from that flash drive. Troubleshooting network connectivity 67

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169

13
Troubleshooting
This chapter discusses the following topics:
Troubleshooting network connectivity
Troubleshooting
firmware
corruption
Troubleshooting Citrix password expiration
Using system diagnostics to troubleshoot
Troubleshooting network connectivity
1.
Ping the desired server by doing the following:
a.
Click the System Information button on the taskbar, and then click on the
Net Tools
tab.
b.
Under
Select Tool
, select
Ping
.
c.
In the
Target Host
box, type the server address, and then click
Start Process
.
If the ping is successful, the system will display the following output:
PING 10.30.8.52 (10.30.8.52) 56(84) bytes of data.
64 bytes from 10.30.8.52: icmp_seq-1 ttl=64 time=0.81 5 ms 64 bytes
from 10.30.8.52: icmp_seq=2 ttl=64 time=0.735 ms
If the ping is unsuccessful, the thin client might be disconnected from the network and experience a long
delay with no system output.
2.
If the thin client does not respond to the ping, do the following:
a.
Check the network cable and check the network settings in the Control Panel.
b.
Try pinging other servers or thin clients.
c.
If you can reach other thin clients, verify that you typed the correct server address.
d.
Ping the server using the IP address instead of the domain name or vice-versa.
3.
Check the system logs by doing the following:
a.
Click the System Information button on the taskbar, and then click on the
System Logs
tab.
b.
Check for any errors in the logs.
c.
If there is an error, then the
Server is not set up
notification
appears. Verify that the server is set
up properly and that HP Smart Client Services is running.
Troubleshooting
firmware
corruption
If the thin client beeps two times after it is powered on or does not appear to boot, then the device
firmware
may be corrupt. It is possible to resolve this by downloading the thin client image from
,
copying the image to a removable USB
flash
drive, and then booting the thin client from that
flash
drive.
Troubleshooting network connectivity
67