Check the lpd.perms file... I don't know if you're using pre-packaged lprng or not...but the Debian packages put pretty strict rules in lpd.perms by default.
For instance, I had to change the following on my Debian print server: ## Reject anything that isn't generated locally REJECT NOT SERVER ... # Reject print requests from remote places REJECT SERVICE=R FORWARD I just commented them both out because the server sits on an isolated (and heavily firewalled) network and I have total control over all the clients and they physical network itself -- I'm not worried about locking down and fine-tuning lpd.perms on this box. --- Keith Rinaldo Systems Administrator College of Engineering University of Nevada, Las Vegas ----- Original Message ----- From: "Gruber Stefan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 24, 2003 10:35 PM Subject: LPRng: Remote printing/no printcap/connection refused > Hi list! > > Got a little problem with remote printing from linux to linux! > > First the environment: > Printserver named pt1, SuSE8.2, lprng3.8.12 > Printclient named pt5, SuSE8.0, lprng3.8.12, no printcap > no firewall in between, but different subnet > > I've added in client's lpd.conf the line default_remote_host=pt1 > Both machines have lpd running; if i trigger "lpc status hp2250sys" on > the client, it shows me (correctly) that the client looks on pt1 for > hp2250sys - printer but same time i receive following error: > Printer '[EMAIL PROTECTED]' - cannot open connection - Connection refused > Make sure the remote host supports the LPD protocol > > Doing a printjob: echo test | lp -dhp2250sys > --> lp: unable to print file: server-error-service-unavailable > > I think that I have to modify lpd.conf and lpd.perms on the server > (printing there goes well) and I tried a couple of things > unfortunately without success. > > What I'm expecting to do is to fully control printers via client > minimum to watch for status (lpc status xxx, lpc status all) and of > course to print. > > Couldn't find any hints in the existing list, perhaps you can help me. > > thx > stg > > > ##################################################################################### > This e-mail message has been scanned for Viruses and Content > by MailMarshal > For more information please visit www.marshalsoftware.com > ##################################################################################### > > ----------------------------------------------------------------------------- > 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. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
