HP EliteDesk 705 G3 Micro Maintenance and Service Guide - Page 94

that the Remote System Installation Server contains the NIC

Get HP EliteDesk 705 G3 Micro PDF manuals and user guides View all HP EliteDesk 705 G3 Micro manuals
Add to My Manuals
Save this manual to your list of manuals

Page 94 highlights

Network controller stopped working when an expansion board was added to the computer. Cause Solution The network controller requires drivers. Verify that the drivers were not accidentally deleted when the drivers for a new expansion board were installed. Network controller stops working without apparent cause. Cause The files containing the network drivers are corrupted. The cable is not securely connected. The network controller is defective. Solution Reinstall the network drivers using the Recovery Disc Set in Windows 7. If necessary, download the softpaq from the web (from a different computer). 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. Contact an authorized service provider. New network card will not boot. Cause New network card may be defective or may not meet industrystandard specifications. Solution 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 Unprogrammed EEPROM. Solution Contact an authorized service provider. 86 Chapter 6 Troubleshooting without diagnostics

  • 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
Network controller stopped working when an expansion board was added to the computer.
Cause
Solution
The network controller requires drivers.
Verify that the drivers were not accidentally deleted when the
drivers for a new expansion board were installed.
Network controller stops working without apparent cause.
Cause
Solution
The
files
containing the network drivers are corrupted.
Reinstall the network drivers using the Recovery Disc Set in
Windows 7.
If necessary, download the softpaq from the web (from a
different
computer).
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.
86
Chapter 6
Troubleshooting without diagnostics