I've received a number of helpful replies, most of which say to use 
"text", "raw", or "ps" for the rp value. I tried "raw" and the 
results were the same -- ie, no response. One thing I didn't mention 
in my original message was the firmware version of the JetDirect 
card: A.02.01. I think this is pretty old.
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 Thu Sep 26 1996 - 20:43:45 NZST