Configure Lexmark T616 printer

[Anthony khan]

Hi Forum,

I am trying to configure Lexmark T616 in HP-UX 10.20 as a network printer, do anyone have documentation how to configure it.

Thanks

[Chuck Zearfoss]

The supported way is to use Lexmark's Enhanced Drivers for Unix package and follow the instructions...
However if you are using JetAdmin or HPPI... Create the queue by putting in the IP of a HP printer at the JetDirect/HPPI create queue prompts, 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