Operating System - HP-UX
1825311 Members
4567 Online
109679 Solutions
New Discussion юеВ

P2015dn not recognized as network printer by hppi

 
Mauricej
Occasional Contributor

P2015dn not recognized as network printer by hppi

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
9 REPLIES 9
David Bellamy
Respected Contributor

Re: P2015dn not recognized as network printer by hppi

can you telnet into the printers.
Mauricej
Occasional Contributor

Re: P2015dn not recognized as network printer by hppi

Hi David,

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

Maurice
Luk Vandenbussche
Honored Contributor

Re: P2015dn not recognized as network printer by hppi

Mauricej
Occasional Contributor

Re: P2015dn not recognized as network printer by hppi

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.
OldSchool
Honored Contributor

Re: P2015dn not recognized as network printer by hppi

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?
Mauricej
Occasional Contributor

Re: P2015dn not recognized as network printer by hppi

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
OldSchool
Honored Contributor

Re: P2015dn not recognized as network printer by hppi

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
Tommy Brown
Respected Contributor

Re: P2015dn not recognized as network printer by hppi

MJ,
Here is an HP document that shows some of the KEY differences in some of the Jetdirect products..
Tommy
I may be slow, but I get there !
Mauricej
Occasional Contributor

Re: P2015dn not recognized as network printer by hppi

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