> From [EMAIL PROTECTED] Wed Oct 18 18:02:43 2000
> From: [EMAIL PROTECTED]
> Date: Wed, 18 Oct 2000 17:10:34 -0700
> Subject: LPRng: Laserwriter 8500 High Weirdness
> To: [EMAIL PROTECTED]
>
> Any suggestions from anyone (including dropping the printer off a roof)
> would be most welcome. I just can't get this thing to work with LPRng,
> although it worked six months ago, and I can't find anything changed.
> The printer still works fine if I send print jobs to it from a Macintosh
> via the LPD protocol - I have tried queue names lp, raw, pz04, even left
> it blank, and it works every time. The printer name is defined as pz04
> in the printer, although Apple documentation suggests I use the "raw"
> queue name to spool to it via LPD, which I know worked with this printer
> in the past. When I try to spool a job from an Apple to the LPRng queue
> for this printer, nothing happens. lpq -P pz04 gives me the following
> output:
>
> Printer: pz04@pcfprod (dest [EMAIL PROTECTED]) 'snm'
>  Queue: 1 printable job
>  Server: pid 21666 active
>  Unspooler: pid 21668 active
>  Status: connecting to '199.249.215.99', attempt 1 at 15:56:24.883
>  Filter_status: no response from printer at 14:08:18.745
>  Rank   Owner/ID                  Class Job Files                 Size
> Time
> active Dean Lambourn@deanl+695      A   695 untitled            127388
> 15:54:40
> Queue does not exist
>
> However, when I take the same Mac, and redirect its LPD queue to spool
> directly to the printer, it works fine. I'm using the exact same queue
> name to spool directly to the printer as LPRng is configured to use, so
> I don't understand why I get the "Queue does not exist" message. 
>
> Here's the printcap entry:
> pz04|snm:\
>         :rw:\
>         :[EMAIL PROTECTED]:\
>         :sd=/var/spool/lpd/pz04:\
>         :af=acct:\
>       :lf=log:\
>       :ps=status:\
>         :if=/usr/libexec/filters/ifhp:\
>         :ifhp=model=apple:\
>         :sh:
>
> I tried using the "bk", "nline_after_file", and "status@" options, and
> combinations of these - they didn't seem to change the behavior any. I'm
> using LPRng 3.6.10-3 and ifhp 3.3.9-1. Here are a few lines from the
> status file which seem relevant:
>
> connecting to '199.249.215.99', attempt 1 at 2000-10-18-15:38:14.514 ##
> identifier=root@pcfprod+171 number=171 process=21173
> connected to '199.249.215.99' at 2000-10-18-15:38:14.527 ##
> identifier=root@pcfprod+171 number=171 process=21173
> requesting printer [EMAIL PROTECTED] at 2000-10-18-15:38:14.527 ##
> identifier=root@pcfprod+171 number=171 process=21173
> error 'LINK_ACK_FAIL' with ack 'ACK_STOP_Q' sending str '^Braw' to
> [EMAIL PROTECTED] at 2000-10-18-15:38:14.533 ##

Well,  I hate to say it,  but it looks like it simply does not
like the print queue name 'raw'

I have not the faintest idea why...  Have you tried a 'reset to factory'
and then setting up the printer again?

> identifier=root@pcfprod+171 number=171 process=21173
> job 'root@pcfprod+171' transfer to [EMAIL PROTECTED] failed at
> 2000-10-18-15:38:14.534 ## identifier=root@pcfprod+171 number=171
> process=21173
>
> I'd say the printer was screwed, but the damn thing works fine when
> receiving LPD jobs from Macs. I don't get it. Any ideas?
>
> -- 
> Jules Agee
> System Administrator        O>
> Pacific Coast Feather Co.  / )
> [EMAIL PROTECTED]  x284        X

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to