installing hp8150dn with hppi or addqueue

[Bill Hassell]

Is this printer on another subnet? Ping is only one communication test. Perhaps a router is blocking port 9100? Use hpnpadmin to query the printer:

hpnpadmin -v 12.34.56.78

Check the working printer and the problem printer.

[Bill Walter]

we have run hpnpadmin -v which yielded the following results:

[k3@]/home/root # hpnpadmin -v
*** Receive NO snmp response!
*** (printer down, cable off, or wrong Get community name?)

We asked our network guru to watch as we made another attempt. He could see our telnet connection but saw nothing when we executed the hpnpadmin command. He stated all the ports going out of the server are open.

The community name in snmpd.conf match the entry in snmpd.conf on the server which can access the printer.

[Bill Hassell]

> We asked our network guru to watch as we made another attempt. He could see our telnet connection but saw nothing when we executed the hpnpadmin command. He stated all the ports going out of the server are open.

Apparently not. The snmp message is not helpful -- it just means that hpnpadmin did not connect to the JetDirect card. Try telnet 9100 to see if you can connect to the printer on port 9100. If port 9100 is open, your screen will probably clear and you'll some underscore characters when you press return. Characters are not echoed and you'll have to press CTRL ] to get to a telnet prompt and then quit. If port 9100 is not open, you'll get:

Connecting to 192.168.0.10...

which means the path to that IP address is blocked somewhere. In router terms, the port name may be jetdirect, hpnp, hp-printer or similar. To see normal results, use the working printer's IP address. Another confirmation point is that the working printer is on a different subnet than the failing one -- thus a different router path.

[Bill Walter]

Great suggestion; however, here is what happened:

# telnet 999.999.999.999 9100
Trying...
Connected to 999.999.999.999.
Escape character is '^]'.

telnet> quit
Connection closed.

I performed this test on the other box, where the printer works, with exactly the same results. Looks like port 9100 is open.

[Bill Hassell]

Try standard telnet or a web page pointed to the printer's address. Then check to see that TCP/IP protocol is enabled. There are usually 4 protocols available but each one can be disabled. Telnet will give you a menu, the web page will be a full browser with multiple pages. You can compare both printers with their network settings.

[Bill Walter]

I have examined the printer config, again. It is correctly configured with TCP/IP and port 9100 enabled. Note that both the successful and the unsuccessful servers are pointing at the same printer, so no comparison can be made.

[Bill Hassell]

One last check on the JetDirect card: make sure there are no entries in the access list. This is either empty (any IP address can talk to the card) or has 1 to 10 entries (no IP except those can connect).

When all else fails, use the cold reset in the printer to clear all the JetDirect settings and then reassign the addresses manually with telnet or arp/ping harvesting.