I swapped some servers around after the GNHLUG meeting last night, and
walked in (of course) to all sorts of strange interdependencies that
cropped up... and I've patched everything together, EXCEPT, of all things,
printing. Under both stock lpr and LPRng, I get:
lpr: connect: Connection refused
when I try to submit a job. Power-cycling both the server and the printer
don't seem to help (which I thought I'd try in case, as per the LPRng
HOWTO, I was filling up my TCP ports before they had a chance to expire).
I hate to admit it, but my face currently has mirror imprints of the
alphabet from slamming my head into the keyboard. If anyone has any
suggestions (Google, usually helpful, has come up dry), I'd be MOST
appreciative.
Setup:
Some Linux boxen, two running LPRng, one with stock lpr (though only one
enabled at a given time), attempting to talk to some half-dozen HP
printers (and one miscreant Sharp that I'm more than willing to pretend
doesn't exist). Snippet for printer closest to me:
lp|hp5000:\
:sd=/var/spool/lpd/lp:\
:mx#0:\
:sh:\
:rm=192.168.1.100:\
:rp=raw:\
:if=/var/spool/lpd/lp/filter:
And, just to give a hint of how my day's gone:
[root@sol /root]# lpc start all
HP5000:
printing enabled
lpc: connect: Connection refused
couldn't start daemon
sharp:
printing enabled
lpc: connect: Connection refused
couldn't start daemon
chp8850dn-b:
printing enabled
lpc: connect: Connection refused
couldn't start daemon
hp4050:
printing enabled
lpc: connect: Connection refused
couldn't start daemon
chp8850dn:
printing enabled
lpc: connect: Connection refused
couldn't start daemon
Do I need to upgrade my brain's kernel rev.? Is there something
pathetically obvious that I'm missing? (Oh, and, yes, all the hosts
resolve via DNS.)
Thanks...
-Ken
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************