vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I can't get this to work, although I know it does as I've had it working on the same machine in the past. I'm trying to set up lprng to act as a print server for a group of machines. I have the printer set up as a raw printer and the client set up with the correct drivers. The client can see the printer but CUPS reports the error "Remote printer refused control file (104)", or something very similar. Is this some sort of remote permissions issue? I've looked but can't for the life of me work out what's wrong. Anyone any ideas? -- James: jwt102@york.ac.uk http://www-users.york.ac.uk/~jwt102 |
| |||
| James Telfer wrote: [...] > > The client can see the printer but CUPS reports the error "Remote printer > refused control file (104)", or something very similar. Is this some sort > of remote permissions issue? I've looked but can't for the life of me work > out what's wrong. > > Anyone any ideas? By default, it's probably configured to only allow jobs to be submitted by localhost. Check the lpd.perms file, which IIRC, is in /etc/lpd see http://www.lprng.org/LPRng-Reference...t/permsref.htm for more info, or man lpd.perms -- - Matt - |
| |||
| James Telfer wrote: >I can't get this to work, although I know it does as I've had it working on >the same machine in the past. I'm trying to set up lprng to act as a print >server for a group of machines. I have the printer set up as a raw printer >and the client set up with the correct drivers. > >The client can see the printer but CUPS reports the error "Remote printer >refused control file (104)", or something very similar. Is this some sort >of remote permissions issue? I've looked but can't for the life of me work >out what's wrong. > >Anyone any ideas? > > You don't use lprng with CUPS, not the same thing at all, which is most likely your problem. Save this as, say, docups: #!/bin/ksh cd /usr/bin rm lp lp-lprng lpq lpr lprm lpstat ln -s lpstat-cups lpstat ln -s lprm-cups lprm ln -s lpr-cups lpr ln -s lpq-cups lpq ln -s lp-cups lp then chmod 755 docups then (as root) docups cd /etc/rc.d ../rc.lprng stop (this stops lprng) chmod 644 rc.lprng chmod 755 rc.cups (this starts CUPS) ../rc.cups start You could also just reboot. If you want to go back to lprng, save this as, say, dolprng: #!/bin/ksh rm lp lp-lprng lpq lpr lprm lpstat ln -s lpstat-lprng lpstat ln -s lprm-lprng lprm ln -s lpr-lprng lpr ln -s lpq-lprng lpq ln -s lpr lp-lprng ln -s lp-lprng lp Reverse what you did in /etc/rc.d above. cd /etc/rc.d chmod 644 rc.lprng chmod 755 rc.cups etc. |
| |||
| Matt Payton wrote: > James Telfer wrote: > > [...] > >> >> The client can see the printer but CUPS reports the error "Remote printer >> refused control file (104)", or something very similar. Is this some >> sort >> of remote permissions issue? I've looked but can't for the life of me >> work out what's wrong. >> >> Anyone any ideas? > > By default, it's probably configured to only allow jobs to be submitted > by localhost. Check the lpd.perms file, which IIRC, is in /etc/lpd > > see http://www.lprng.org/LPRng-Reference...t/permsref.htm for more > info, or man lpd.perms > > Ok, I've looked at this but can't see anyting that should be stopping this happen. My /etc/lpd.perms file follows: # allow root on server to control jobs ACCEPT SERVICE=C SERVER REMOTEUSER=root # allow anybody to get server, status, and printcap ACCEPT SERVICE=C LPC=lpd,status,printcap # reject all others REJECT SERVICE=C # # allow same user on originating host to remove a job ACCEPT SERVICE=M SAMEHOST SAMEUSER # allow root on server to remove a job ACCEPT SERVICE=M SERVER REMOTEUSER=root REJECT SERVICE=M # all other operations allowed DEFAULT ACCEPT The problem seems to be the availability of the printer, webmin reports the printer as not accepting requests or having printing enabled. Changing these settings in webmin does not 'stick', they immediately revert back to the original settings. -- James: jwt102@york.ac.uk http://www-users.york.ac.uk/~jwt102 |
| |||
| On Thu, 19 Feb 2004 16:23:53 +0000, James Telfer wrote: [...] > The problem seems to be the availability of the printer, webmin reports the > printer as not accepting requests or having printing enabled. Changing > these settings in webmin does not 'stick', they immediately revert back to > the original settings. Strange. What's the output of lpc status ? If it shows as being disabled, try enable "queue-name". Also, what's the output of checkpc -V ? If it reports problems, you can usually fix alot of them with checkpc -f Also, did you confirm that CUPS is not installed as suggested in another reply ? There will be issues if both CUPS and LPRng are installed. -- - Matt - |
| |||
| Matt Payton wrote: > Strange. What's the output of lpc status ? If it shows as being > disabled, try enable "queue-name". > Also, what's the output of checkpc -V ? If it reports problems, you can > usually fix alot of them with checkpc -f > > Also, did you confirm that CUPS is not installed as suggested in another > reply ? There will be issues if both CUPS and LPRng are installed. > I've only got LPRng on the slackware machine, CUPS is running on the client machine that I'm trying to access the printer from. I'll check the rest soon, thanks for the pointers so far! -- James: jwt102@york.ac.uk http://www-users.york.ac.uk/~jwt102 |
| ||||
| Matt Payton wrote: > On Thu, 19 Feb 2004 16:23:53 +0000, James Telfer wrote: > > [...] > >> The problem seems to be the availability of the printer, webmin reports >> the >> printer as not accepting requests or having printing enabled. Changing >> these settings in webmin does not 'stick', they immediately revert back >> to the original settings. > > Strange. What's the output of lpc status ? If it shows as being > disabled, try enable "queue-name". > Also, what's the output of checkpc -V ? If it reports problems, you can > usually fix alot of them with checkpc -f Running checkpc -V showed several problems, notably some ownership/permission errors. Happily checkpc -f has fixed everything and it is all working happily now, thanks very much! -- James: jwt102@york.ac.uk http://www-users.york.ac.uk/~jwt102 |