I'm one to be sympathetic :)
First: no, it *does* work with a remote printer! I tested older
JetDirects as well as a newer model, with two different printer types.
Second: I'm unclear as to your printcaps - it looks like you have on
printcap referring to the same printer? Or are they variations for
testing? I would certainly be skittish about the same exact printer being
referenced in the printcap file at the same operational time.
Not being so advanced in some of this, my first tack would be to
simplify. My current printcap is this:
# Lab Printer - FIRST port on the JetDirect box.
lp:sd=/var/spool/lpd/%P
:force_localhost
:lp=saturnp1.uvm.edu%9100
:sh
(I add two more ports on the same JD box)
You might, for instance, want to try this one for your remote printer
testing:
qfs1750_1|lp4|sc563160-L1-qfs1750_1|sc563160 L1:\
:lp=192.192.192.101%9100:\
:sd=/var/spool/lpd/%P
Ditch the log and accounting file for the moment to get things working
more solidly.
I don't believe that you have to have a FQDN for the printer name, so that
should not, in theory, be a problem.
One additional step: change versions of LPRng - it worked a charm for me
(3.8.1).
One other caution: somewhere on the LPRng web pages is a cautionary note
about printers that must talkback to the system and how to deal with
that. Might be worth making sure that's not part of the mix.
Finally, at the risk of complicating things, it is not inconceivable that
the problem lies in the sending application. Based on your statement
about having W98 and W2K clients, I wonder if you have fully eliminated
particular applications. For my part, I have clear cut cases where, in
the past, Word was guilty of doing something very similar to what you
describe: sending a job and then stalling part way through. Only deleting
the job alleviated the problem. This was made even more fun by the fact
that it was not *always* a problem (can you say 'feature
enhancements'??). Another application that might bear scrutiny is Acrobat
- printing pdf files can produce, well, "unexpected" results!
Hope this (somewhat simplistic) reply helps a bit...
David Houston
CIT Client Services Coordinator
University of Vermont
On Jan 16, 2002, P.Remmertz wrote:
P.
P. I asked 10 days ago, but nobody answered?!
P.
P. We are printing with these Print-Server-Boxes and we have the problem that
P. sometimes the job is stalled . According to this the following jobs will not
P. be printed either. If this stalled job will be deleted the printing works
P. correctly and the other jobs in the Queue will be printed. Sometimes it
P. already works by restarting lpd.
P.
P. Does printing only work correctly with a printer connected to the local
P. device of a linux-computer? To our opinion it is not network-printing if
P. some computers have to run for printing at their locally connected printer.
P. In addition to this we don't have linux-clients but W98- and W2k-Clients.
P.
P. We use:
P. >RFC-1179
P. >lprng 3.6.25-5
P. >SuSE 7.1
P. >Kernel 2.4.14
P. >Apsfilter (must we use ifhp-filter?)
P. >Samba 2.2.2-3
P.
P. My printcaps
P.
P. # VERSION=3.6.26
P. # Queue nach RFC1179
P. qfs1750_1|lp4|sc563160-L1-qfs1750_1|sc563160 L1:\
P. :lp=:\
P. :rm=sc563160:\
P. :rp=L1:\
P. :sd=/var/spool/lpd/sc563160-L1-qfs1750_1:\
P. :lf=/var/spool/lpd/sc563160-L1-qfs1750_1/log:\
P. :af=/var/spool/lpd/sc563160-L1-qfs1750_1/acct:\
P. :ar:bk:mx#0:\
P. :tr=:cl:sh:send_job_rw_timeout#0:
P.
P. ### END apsfilter: ### remote sc563160 L1 qfs1750_1 ###
P. # For testing port 9100
P. qfs1750_1|lp4|sc563160-L1-qfs1750_1|sc563160 L1:\
P. :lp=192.192.192.101%9100:\
P. :sd=/var/spool/lpd/sc563160-L1-qfs1750_1:\
P. :lf=/var/spool/lpd/sc563160-L1-qfs1750_1/log:\
P. :af=/var/spool/lpd/sc563160-L1-qfs1750_1/acct:\
P. :ar:bk:mx#0:\send_job_rw_timeout#0:
P.
P.
P.
P.
P.
P. -----------------------------------------------------------------------------
P. YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
P. The address you post from MUST be your subscription address
P.
P. If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
P. or lprng-digest-requests) with the word 'help' in the body. For the impatient,
P. to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
P. with: | example:
P. subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
P. unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
P.
P. If you have major problems, send email to [EMAIL PROTECTED] with the word
P. LPRNGLIST in the SUBJECT line.
P. -----------------------------------------------------------------------------
P.
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
