HP Jetdirect 380x HP Wireless Print Server 380x - (English) Setup Guide - Page 56

Firmware Upgrade Failure, If Server-Based Authentication is Not Used, Windows, HP Web Jetadmin

Page 56 highlights

z Elevate the access point's antenna. In most office environments, elevating the access point's antenna will improve the range and performance of all wireless devices. z Check to see what a wireless device such as a laptop computer receives for signal strength, as reported in its client utility. The print server should have a similar signal strength when positioned in the same location. Also, many client utilities have the ability to a test between two devices (client-to-client in ad hoc mode or client-to-access point in infrastructure mode). The method to do this varies from client to client. Firmware Upgrade Failure HP Jetdirect wireless print servers support network installation, or download, of firmware upgrades to provide new or enhanced features. As with other HP Jetdirect print servers, firmware upgrades may be downloaded using tools such as HP Download Manager (Windows), HP Web Jetadmin, or FTP (File Transfer Protocol). z If the firmware upgrade fails to complete, you should restart the upgrade without cycling the power to the print server. z If power is lost during the upgrade and the print server must be restarted, your next steps depend on whether the print server is configured for server-based authentication. If Server-Based Authentication is Not Used If either type of firmware upgrade failure occurs on an HP Jetdirect wireless print server that is not configured for server-based authentication, simply restart the download process and try again. If the print server must be power-cycled before you can restart the upgrade, the print server will regain its previous configuration prior to the download failure. 5-10 Troubleshooting Problems

  • 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

5-10 Troubleshooting Problems
Elevate the access point’s antenna. In most office environments, elevating the access
point’s antenna will improve the range and performance of all wireless devices.
Check to see what a wireless device such as a laptop computer receives for signal
strength, as reported in its client utility. The print server should have a similar signal
strength when positioned in the same location.
Also, many client utilities have the ability to a test between two devices (client-to-client
in
ad hoc
mode or client-to-access point in infrastructure mode). The method to do this
varies from client to client.
Firmware Upgrade Failure
HP Jetdirect wireless print servers support network installation, or download, of firmware
upgrades to provide new or enhanced features. As with other HP Jetdirect print servers,
firmware upgrades may be downloaded using tools such as HP Download Manager
(Windows), HP Web Jetadmin, or FTP (File Transfer Protocol).
If the firmware upgrade fails to complete, you should
restart the upgrade without
cycling the power
to the print server.
If power is lost during the upgrade and the print server must be restarted, your next
steps depend on whether the print server is configured for server-based authentication.
If Server-Based Authentication
is Not
Used
If either type of firmware upgrade failure occurs on an HP Jetdirect wireless print server
that is not configured for server-based authentication, simply restart the download process
and try again. If the print server must be power-cycled before you can restart the upgrade,
the print server will regain its previous configuration prior to the download failure.