topic Installing non-HP printer interfaces using JetAdmin in Operating System - HP-UX

Installing non-HP printer interfaces using JetAdmin

Clifton Smith — Tue, 09 Apr 2002 19:42:07 GMT

I am attempting to install a network printer using a Lantronix print server interface (much like an HP JetDirect box)to an HP9000. When using JetAdmin, it tells me that it can ping the printer, but cannot install because it is not an HP device. Can someone share with me a way to add this printer? I may have to use the lpadmin command, but am not sure what the printer device file would be, or which options I should use. Thanks

Re: Installing non-HP printer interfaces using JetAdmin

Victor_5 — Tue, 09 Apr 2002 19:47:52 GMT

JetAdmin is only for printers with JetDirect card (or box), in your case, try to set up your printer as remote printer instead of network printer, good luck.

Re: Installing non-HP printer interfaces using JetAdmin

Steve Steel — Wed, 10 Apr 2002 05:33:32 GMT

Hi

You should ask the supplier but

Otherwise

I would say there are 2 options.

1)Install as a remote printer via sam and
use the options available

2)try a 3rd party solution

Lexmark has a product called markvision which is free to download from the net.
Runs on HP-UX and supports a lot of stuff

Robust architecture

Broad printer and MFP support

MarkVision Professional fully supports all network-capable Lexmark printers and MFP's as well as over 70 printers and MFP's from other manufacturers (including HP, Xerox, Canon, Tektronix, Minolta, IBM, QMS, Ricoh and Kyocera). This feature allows IT administrators to use MarkVision Professional to manage their entire fleet of printers.

Client-server architecture
MarkVision's client server architecture uses the network efficiently to preserve valuable bandwidth while providing real-time remote management capabilities for IT administrators to speed up problem resolution and prevent downtime.
MarkVision Professional may be installed only once allowing user access via a web browser. This feature significantly reduces MarkVision software roll-out and update costs while extending access everywhere in the organization (where use is authorized).

Look at it

Steve Steel

Re: Installing non-HP printer interfaces using JetAdmin

Thierry Poels_1 — Wed, 10 Apr 2002 05:51:42 GMT

Hi,

JetDirect indeed tells you that it can ping the device, but that it's not an JetDirect card/box. You can try to ignore this message, and just continue setup which might work perfectly.
We use this way for Lexmark boxes and it works like a charm, and all printers (JetDirect & Lexmark) are configured through the same utility.

good luck,
Thierry.

Re: Installing non-HP printer interfaces using JetAdmin

Chuck Zearfoss — Fri, 09 Aug 2002 11:25:02 GMT

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 Lexmark printer.
One thing to keep in mind - if you are printing large jobs to the 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