topic Re: Installing non-HP printer in Operating System - HP-UX

Installing non-HP printer

John McDen — Mon, 29 Apr 2002 11:54:38 GMT

I am trying to install a non-HP printer on ver 11.0.

I can ping the printer IP address but when I use Jetadmin to install the printer it says

!! No response from xxx.xxx.xxx.xxx !!
... (trying to ping xxx.xxx.xxx.xxx )

The HP JetAdmin utility can ping the device. The problem may be:
* incorrect GET community name!
* it is not a network printer!
* other.

Can somebody help me please..

Re: Installing non-HP printer

Steve Steel — Mon, 29 Apr 2002 12:14:40 GMT

Hi

Jetadmin is HP Card specific.

Look for a third party solution or install as a
remote printer.

LEXMARk has Markvision which runs on HP-UX and supports most printers

Steve Steel

Re: Installing non-HP printer

Victor_5 — Mon, 29 Apr 2002 13:27:26 GMT

I met the same problem on last Friday, but I was using HP printer, if you can ping this printer, that means the physical communication is ok, two points for you:

1. Generally, JetAdmin is only for HP printers with JetDirect card, in this case, you can try to power off-power on your printer and reset your jetDirect card no matter it is internal or external, sounds easy? But it worked on my case.

2. For some third party printers, you need set them up as remoter printer instead of network printer, check with your pritner vender to confirm.

Good luck!

Re: Installing non-HP printer

John Carr_2 — Mon, 29 Apr 2002 13:35:10 GMT

Hi

if the reset doesn't help please post details of printer trying to be used and which model external / internal jet direct card.

cheers
John.

Re: Installing non-HP printer

benoit Bruckert — Tue, 30 Apr 2002 06:41:48 GMT

hi,
If your printer is connected on the network, it means it has a network card.
And most networks printers has an lpr port !!
This means that to install this printer don't use jetdirect, but use printing on remote system !
(Add remote printer in sam).

regards
Benoit

Re: Installing non-HP printer

Chuck Zearfoss — Fri, 09 Aug 2002 11:30:27 GMT

The good solution is to use Lexmark's Enhanced Print Drivers for Unix, which will support other MOST NEWER vendor printers/NICs.

Using JetDirect/HPPI, you can create the queue by putting in the IP of a HP printer that is on the network, then go through the configuration and select the model script you wish, etc. After setup is complete, edit the file to change the IP to that of your non-HP printer.

One thing to keep in mind - if you are printing large jobs to a newer Lexmark with JetAdmin, and you run out of paper, get a jam, or a windows user sends a job to it, etc. you may see your JetAdmin job reprint from page 1 in the middle of the job.

It looks like the way to fix this is to change the community name string in the lexmark printer. 2 Ways -
1)Use telnet: Telnet 9000
2)Use Lexmark's MarkVision Professional software
a) under settings-network-tcp/ip, at the bottom
b) create a device policy for a print server (if you want to change alot of printers at one time)

JetAdmin and HPPI does SNMP GETs before the print data, one with community string of internal (which Jetdirect cards will answer, but no other vendor), and one with community string of public, which asks for the private mib location. If a printer responds to this one (as the lexmark does with the OID for it's private mib .641.), then the JetAdmin/HPPI will tend to do "status checks" by requesting SNMP OIDs when it detects a dataflow issue (don't know what kicks that off...). Anyway lexmark responds to the status OID request with "no such name" (cuz the OIDs are in HP's private MIB .11.) and then Jetadmin/HPPI restarts the print job from page one. If the community string name in the lexmark is changed from the default of public, JetAdmin/HPPI still performs the initial SNMP GETs, but gets no response in either case, and thus evidently thinks the printer is "dumb" and never does the status checks in the middle of the job, but instead just keeps sending data...
Hope this helps
Chuck

Re: Installing non-HP printer

Paul Benvenuti — Fri, 09 Aug 2002 11:54:04 GMT

John,

Like Victor and Benoit, I found the easiest solution is to set it up like a remote printer. I start by making an entry in /etc/hosts and then use the assigned name when configuring the remote host/printer in sam.

Our network is mostly Windows, and not all printers are configured on the HP box. Regardless, I always add them to the hosts file as it is a real simple way to keep track of them.