topic Re: P2015dn not recognized as network printer by hppi in Operating System - HP-UX

P2015dn not recognized as network printer by hppi

Mauricej — Thu, 21 Jun 2007 15:33:04 GMT

We have two P2015dn printers that are connected to our network, that we access from a Solaris 10 server. The first of the two, we were able to configure using the old Web JetAdmin software. But the newer printer is not listed as a print server. So we tried using hppi, however, hppi also reports that neither one of the printers (including the one we were able to setup with wja) is a networked printer. We can ping the printers from the same host, and are able to print to them from Windows clients over the network. Any ideas anyone?

Thanks
MJ

Re: P2015dn not recognized as network printer by hppi

David Bellamy — Thu, 21 Jun 2007 16:48:08 GMT

can you telnet into the printers.

Re: P2015dn not recognized as network printer by hppi

Mauricej — Fri, 22 Jun 2007 07:08:04 GMT

Hi David,

No I cannot telnet in to either one. Wja indicates they are using JetDirect CB364A.

Maurice

Re: P2015dn not recognized as network printer by hppi

Luk Vandenbussche — Fri, 22 Jun 2007 07:37:54 GMT

Check this link

http://www.hp.com/pond/modelscripts/index2.html

Re: P2015dn not recognized as network printer by hppi

Mauricej — Fri, 22 Jun 2007 08:04:13 GMT

Thanks Luk

We did download the model script for the 2015 and ran it; It went through a short process then indicated the software was installed. But hppi still does not recognize it as a network printer. I've been looking for documentation on how these model scripts are supposed to work but can't find a thing.

Re: P2015dn not recognized as network printer by hppi

OldSchool — Fri, 22 Jun 2007 10:35:53 GMT

the first things to look into:

can you ping it (the printer) by ip address, dns name?

does it have a jet-direct card installed, attached to jet server, or is it perhaps attached directly to a windows print server?

Re: P2015dn not recognized as network printer by hppi

Mauricej — Fri, 22 Jun 2007 10:40:54 GMT

Yes we can ping it by both IP address and DNS name, from the Solaris box.

The printer has a built-in JetDirect interface.

Just to make sure the model script for the 2015 was installed, I went through the process in hppi to install it again; here is a capture:

Enter the Model Script name or URL(q-quit, ?-help, default=http://www.hp.com/go/
solaris_modelscripts): /usr/lib/lp/model/hpnpl/net_lj2015

ModelScript with same name exists already. Do you want to replace it (y/n, defau
lt=n) : y

The following steps will update the utility to use this new model
script, IT DOES NOT INSTALL AND CONFIGURE A PRINTER.

Enter the Printer Name or IP Address (q-quit) : 198.81.213.122
ERROR: The printer is not in the network.
No response from 198.81.213.122 !

...and that is the printer's correct IP; I can ping that IP from this same box and get replies, and can access the web-based admin page.

Thanks

Re: P2015dn not recognized as network printer by hppi

OldSchool — Fri, 22 Jun 2007 11:56:42 GMT

A little digging shows that this printer is *not* a JetDirect Device, but rather a Window's Printer:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1102369

http://www.shopping.hp.com/webapp/shopping/product_detail.do?storeName=storefronts&landing=printers&category=laserjets&subcat1=bw&catLevel=3&product_code=CB368A%23ABA&tab=detailed_specs#defaultAnchor

It appears that it may need to be installed as a "remote" printer. I'm not sure, maybe a JD card can be added, or attach it to a JetServer?
sS

Re: P2015dn not recognized as network printer by hppi

Tommy Brown — Fri, 22 Jun 2007 13:41:44 GMT

MJ,
Here is an HP document that shows some of the KEY differences in some of the Jetdirect products..
Tommy

Re: P2015dn not recognized as network printer by hppi

Mauricej — Fri, 22 Jun 2007 13:49:09 GMT

I believe I have it working now, setup as a remote printer as OldSchool suggested, with just a few lp commands

lpadmin -p myprt -i /usr/lib/lp/model/hpnpl/net_lj2015
lpadmin -p myprt -v /dev/null
lpadmin -p myprt -s 'printerhostname!auto'

...at least it sent out a postscript file okay, so thats an improvement.

Thanks for all the great help guys
M