HP Web Jetadmin Software Manual do Utilizador descarregar pdf (Página 13)

TROUBLESHOOTING DISCOVERY

HP SNMP Proxy Agent

If HP Web Jetadmin does not discover PC-connected devices running HP SNMP Proxy Agent or

HP WS Pro Proxy Agent, try the following troubleshooting steps to understand why the discovery fails.

The key to these issues is proving that the communication channel between HP Web Jetadmin and the

proxy is working, and then focusing on the printer driver as the culprit.

1. HP SNMP Proxy Agent or HP WS Pro Proxy Agent must be installed on the client computers.

Check the version to make sure it is the latest version available on the Web. HP SNMP Proxy

Agent appears as a program under Add/Remove Programs. HP WS Pro Proxy Agent appears as

a service that must be running.

2. The Microsoft SNMP service, which is a Windows Component and a service, must be installed

and started on the client computers for HP SNMP Proxy Agent to discover devices. The SNMP

Proxy Agent installer will not complete without the SNMP service running. However, the SNMP

service might have been removed or stopped after the proxy was installed.

3. The Microsoft SNMP service must be configured to provide HP Web Jetadmin with read access

through a mutually agreed-upon community name, such as public.

4. The Microsoft SNMP service must be configured to grant access to either the management

application’s host IP address or all IP addresses.

5. The client computers must be equipped with a supported HP device. For a list of supported

devices, see “Appendix A—Supported printing devices” on page 26.

6. The printer driver must be installed with a supported bi-directional I/O stack. An easy way to

ensure this is to install HP UPD or a printing system driver that provides a DOT4 port. There are

no guarantees that the latest or largest driver obtained on the Web contains the DOT4 bi-

directional stack, but the chances are better. HP UPD also provides the necessary language

monitor for composite devices, such as the HP LaserJet P2055.

7. Firewalls on client computers must be configured to pass traffic on UDP port 161 (SNMP).

8. Verify basic network connectivity by pinging the client machine from the HP Web Jetadmin server.

9. Use a third-party SNMP tool, such as SNMP Get or GetIF, to verify basic SNMP service on the

Windows client. Any tool capable of gathering SNMP information should suffice. A typically

supported object to query in order to prove SNMP communication is 1.3.6.1.2.1.1.1 (sysDescr).

For example:

snmpget –v 2c –c public clienthostname 1.3.6.1.2.1.1.1

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 30 31

Sem comentários

HP Web Jetadmin Software Manual do Utilizador Página 13