It turns out that the version of firmware on our JetDirect cards is
too old to support lpd. Alan Sherlock <ajs_at_talon.csc.cxo.dec.com> hit
the nail on the head with his answer:
It sounds like the jetdirect you've got doesn't support lpd. The
older versions didn't. Try a telnet to port 515 on the jetdirect.
If you get connection refused, that's the problem. The other
systems that are printing to the card are most likely printing to
port 9100.
If this is the case, call your local CSC for options on how to get
this to work.
Additional thanks to:
Brian Leverson <brian_at_aa.washington.edu>
joe_at_resptk.bhp.com.au
Catherine Xiaolan Zhang <cxzhang_at_eecs.harvard.edu>
Matt White <whitem_at_bofh.usask.ca>
"Craig I. Hagan" <hagan_at_cih.com>
"Dave Golden" <golden_at_falcon.invincible.com>
Mike Ferris <mike_at_pps.ca>
"Zaldivar, Ned" <ZaldivarN_at_zeus.dt.uh.edu>
John Fischer <jfischer_at_worldbank.org>
Kent R Arnott <karnott_at_falcon.tamucc.edu>
Isaac <I.O.Oribioye_at_herts.ac.uk>
Mak Andrew <Andrew.Mak_at_MIS.SYDNEY.nestleau.nestle.com>
Jerry Winegarden <jbw_at_oit.duke.edu>
Original message:
> I'm sure this is a FAQ, and I've looked for answers, but remain
> stumped. Our problem: We have a couple of HP Laserjet 4si printers
> with JetDirect cards in them. We also have a mixed network of
> Alpha's, PC's and HPUX workstations. The 4si's were setup from one
> of the HPUX hosts and I had our Alphas (running DU 3.2d) set up to
> do remote printing to one of the HP hosts (not the Laserjets). Well
> all our HP hosts are going away, and I tried to set up remote
> printing direct to the LJ. No go.
>
> Basically the printcap had:
> :lf=/usr/adm/lperr:\
> :lp=:\
> :rm=hplark:\
> :rp=lark:\
> :sd=/usr/spool/lpd:
>
> where "hplark" is the hostname of the JetDirect card. I tried many
> combinations of "hplark", "lark", "lp0", for the "rp" entry. None
> worked. In the configuration of the JetDirect card, I don't recall
> anything that set a printer name distinct from the IP hostname of
> the card. Something's missing, but I can't figure out what.
>
> sending something via lpr results in a file in the printer queue.
> lpq shows the file in the queue, but always prints "connection to
> hplark is down". The child lpd process basically justs sits there.
> The lpr.log has nothing of note. Note that printing from the HP
> hosts works flawlessly.
>
> any advice appreciated,
--
Peter Gross
Probita, Inc.
pag_at_probita.com
+1.303.546.6307 x3329
Received on Fri Sep 27 1996 - 21:15:34 NZST