I'm playing/experimenting with Cups, and set up a Slackware 8.1 Cups ipp print server. It prints okay both from the local command line and from other Slackware 8.1 machines on the LAN running Cups clients.
All well and good, but there are also some other machines on the LAN which are much older and running various older distributions with the old LPD system (LPD, not LPRng).
Per the Cups documentation, the print server has a line in /etc/inetd.conf file (the print server is not using xinetd) as follows:
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-
...and I have confirmed that this is indeed the proper path for cups-lpd. I also remembered to do "kill -HUP pid" after editing inetd.conf.
I cannot come up with a printcap entry for the LPD based hosts that permits them to access the print server. A command like "lpr myfile.txt" doesn't work, and "lpq" reports: "waiting for queue to be enabled on 192.168.1.4" (which is the address of my print server).
Any ideas, examples, thoughts...?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
bughead1:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
Business Accounts
Answer for Membership
by: LazyAdminPosted on 2002-11-06 at 17:00:21ID: 7417497
Hmm...
I'm not sure that I'm getting the full scope of your problem but...
I've got a RH7.2 machine (which I think has cups) and it's configured to print through an old BSD style SunOS 4.1.3 machine named "aero1" to a printer named "mishp".
I did the configuration entirely through printconf and it worked fine.
Both machines have an "lpc" command that allows you to start/stop individual print queues. Run "lpc" and then type "?" to get an idea what's available.
Here's an excerpt from my RH7.2 /etc/printcap file:
mishp:\
:sh:\
:ml=0:\
:mx=0:\
:sd=/var/spool/lpd/mishp:\
:af=/var/spool/lpd/mishp/m
:rm=aero1:\
:rp=mishp:\
:bk=:\
:control_filter=/usr/share
:lpd_bounce=true:\
:if=/usr/share/printconf/u
Aero1 uses an *OLD* lpd system.
Here's an excerpt from the aero1 printcap which is configured in a similar manner:
mishp| Network printer on Print server axis62:\
:lp=:\
:sd=/var/spool/lpd/mishp:\
:lf=/var/spool/lpd/mishp/l
:rm=axis62:\
:rp=LPT1:
I've got some some new sysV UNIX machines printing via lpd too, but that's an entirely different beast.
If you're still having problems, On any machine that's serving LPD, type "netstat -a|grep LISTEN". The LPD server should be listening on the "printer" socket (515). If not, you've got a problem.
Also check for basic connectivity by telnetting to the LPD server on port 515.
On the old SunOS machine that gives me a "/usr/lib/lpd: Malformed from address" error.
On a new UNIX machine, I have to press return first and then I get an "invalid protocol request".
Something along those lines is normal.