Use JetDirect on non-JetDirect Connected Printers

[Alzhy]

We have a variety of printers (probably a dozen or more) brands. Traditionally, we simply set them up as "remote printers" and that's it. Letely however, there is a requirement to do "Class Printing" - for which "remote printers" does not simply work because the requirement is such that the "class members" need to be local printers (really local or "networked" - i.e. JetDirect conected).

Since we also have a considerable amount of HP and JetDirect-EX connected non-HP Printers, I decided to finally test JetDirect Software. It works flawlesly with all HP printers as well as Non-HP printers hooked up to JetDirect-EX printservers. Then I decided to test non-JetDirect non-HP printers. Via the menu, it errors out when defining the spooler/printer -- something to do with no response on the SNMP MIB - but otherwise works fine. Via Command Line I use:

addqueue -chispeed -i9998 -qmaxlzr1 -hmaxlzr1.xyz.com -boff -Lauto

The printer identity I use is 9998 - which means generic network printer. We only print either postscript or text (with embedded PCL).

My Question, will there be "future issues" using JetDirect software with non-HP Jetdirect printers (which appear works flawlessly)? Anyone actually doing this?

[A. Clay Stephenson · Accepted solution]

It all depends upon how well the non-HP printer emulates the JetDirect protocol but, in general, the answer is yes; they work quite well; and no; there should be no hidden problems. The most difficult aspect is choosing which Laserjet model script to use; ie what does this "outlaw" printer most closely resemble in the HP world. I have had the most difficulty with big multi-function printers/copiers that will do things under Windows (because they have a driver) that become difficult to do under UNIX.

[Alzhy]

Thanks A. Clay,

Our prints as I've mentioned are either preformatted text (with embedded PCL/HPGL codes for font control, orientation, etc..) OR Postscript. So I do also think we should have no issues and should just use the printer identity 9998 (net_generic_printer).

We were fine with simply configuring these printer as "remote" printers but you probably already know that "Class" printing does not work with printers defined as "remote printers". It only works with local (parallel/serial attached) OR networked printers (HP Jetdirect or Xerox's xpadmin).

BTW, I just tested Xeroz/Tek's xpadmin software for HP-UX 11.11 and I must say the menu and workings are strikingly similar to JetDirect...

[Bill Hassell]

As Clay mentioned, non-HP LAN cards will only work with JetDirect software if they use the same port 9100 protocol. The vast majority of non-HP LAN cards use the standard lpr/lpd remote protocol. I haven't tested the latest version of hppi/addqueue with non-HP cards but it might be possible that hppi code has included support for the remote protocol on port 515. If so, I don't remember ever seeing this announced, so it may be an undocumented feature.