Mixing LPRng and CUPS?

Kevin O'Gorman kevin
Mon May 17 11:37:13 PDT 2004


I tried the web thingy, and got basically the same problems as 
described for the Control Center, presumably because the Control
Center is only fronting for the true culprit.

Thanks for the hint about directing the listener.  I'll do that.
The odd thing is, as near as I can tell, nobody's listening on 631
as things stand.  That may be the real problem.  I'll start with the
obvious things: looking at the daemon.  I had thought port 515
was the real deal because of the line from a file in /etc/inet.d:
   printer stream  tcp     nowait lp       /usr/lib/cups/daemon/cups-lpd 
     cups-lpd -o document-format=application/octet-stream
but that turns out to be cups-lpd, which is presumably what I will
be using for my LPRng clients.

Someone sent me a link to full CUPS documentation.  I'm going to
devote as much of today as it takes to making this work.  I'll give
the web admin thingy another try too.

This sort of thing sure makes me respect the effort that goes into
an easy-to-use interface, whenever I actually see one.

Thanks,

++ kevin


-- 
Kevin O'Gorman, PhD  (805) 650-6274  mailto:kevin at kosmanor.com
Permanent e-mail forwarder: mailto:Kevin.O'Gorman.64 at Alum.Dartmouth.org
Permanent e-mail forwarder  mailto:kogorman at umail.ucsb.edu
Web: http://kosmanor.com/~kevin/index.html

On 4 Sep 2002, Aaron Grewell wrote:

> I'm assuming your new COL install is running CUPS.  If so, the easy way
> to configure it is to use the CUPS web interface.  Point the browser on
> that machine to http://127.0.0.1:631 and click Administration.  Put in
> root and password and add the printer from there.  Note that CUPS can do
> autoconfiguration, which may be why you're seeing a printer you didn't
> add.  cupsd may well be confused by your many-dual-nic setup, so I
> recommend editing cupsd.conf and changing the line:
> Port 631
> To read:
> Listen 1.2.3.4:631
> Where 1.2.3.4 is replaced by the IP of the NIC that resides on your
> internal network.  That should prevent CUPS from trying to talk to the
> outside.  Do this for all machines running CUPS.
> 
> The web administration tool has worked far better for me than any of the
> native GUI tools I've tried, either in KDE or Gnome.  I went round and
> round with the KDE stuff once, and after that I don't even bother.  The
> web tools just work.
> 
> On Tue, 2002-09-03 at 22:02, Kevin O'Gorman wrote:
> > Okay, I'm finally at the point of trying the first step.  It's a bit
> > easier because it's CUPS on both sides (my wife's WinME system stopped
> > recognizing its NIC and is having problems with the CDROM for some
> > reason, and rather than put me through installing Win98 so I can upgrade
> > to WinMe and probably still not have all her customization, she's
> > willing to let me teach her Linux.  Hooray!)
> > 
> > Anyway, I thought this would be easy.  I've got a HPLJ4M on a
> > COL 3.1.1 Server running CUPS.  That seems to be working.
> > 
> > I've just installed COL 3.1.1.WS on my wife's machine, and I'm having
> > no luck configuring it to use the printer remotely.
> > 
> > What I've tried:
> >   K -> Control Center -> System -> Printing Manager
> >   This seems to come up with a HPLJ4M printer, at least it has a printer
> >   icon with this caption.  Question 1: is this coincidence?  How could
> >   it know what printer I have on a machine it's not configured to
> >   contact?  When I scan all of /usr and /etc for files containing this
> >   string, all I find is a very broken /etc/printcap that has only the
> >   string HPLJ4M: and no actual configuration -- I have no clue where
> >   that came from since this is a fresh install. 
> > 
> >   When I click on that icon, however, the icon disappears and the entire
> >   Control Center freezes.  I have to kill the task.
> > 
> >   Just about anything else I do to try to configure a printer gets the
> >   same result eventually.  When I try the wizard to create a new printer
> >   I get as far as naming the remote host (it's on the same 192.168.1.0/24
> >   network, and I give the IP number) and the port (I tried 515 because
> >   it's open on the server).
> > 
> >   BTW, I'm assuming CUPS will open its listener on eth0.  This is
> >   important, because there are 2 NICs on almost all my machines.  The
> >   "inner" network is 100MB, and eth0 talks to that.  The "outer"
> >   network is 10MB and connects to a 10MB hub and my DSL router.
> >   Naturally, I prefer local traffic to be on the inner net.
> > 
> >   While testing, all machines are running a firewall that prohibits
> >   any traffic originating from the internet.  Only local addresses
> >   are allowed in NEW connections.
> > 
> > Anyway, the freezeups are annoying and I'm not impressing my wife at
> > all.  The way she sees it, I just earned my PhD in Computer Science
> > last month and I ought to be able to do this in my sleep.
> > 
> > Help?
> > 
> > ++ kevin
> > 
> > -- 
> > Kevin O'Gorman, PhD  (805) 650-6274  mailto:kevin at kosmanor.com
> > Permanent e-mail forwarder: mailto:Kevin.O'Gorman.64 at Alum.Dartmouth.org
> > Permanent e-mail forwarder  mailto:kogorman at umail.ucsb.edu
> > Web: http://kosmanor.com/~kevin/index.html
> > 
> > On 3 Sep 2002, Aaron Grewell wrote:
> > 
> > > CUPS has an LPR emulator, so if that is running and you point your LPR
> > > machines to the queue on the CUPS server it should work fine. 
> > > Personally, I like the CUPS interface so much better than the LPR
> > > frontends I've used that I converted all my machines over.  You
> > > certainly don't have to, though.
> > > 
> > > On Sat, 2002-08-31 at 10:34, Kevin O'Gorman wrote:
> > > > I'm getting a COL 3.1.1. Server system ready to serve.
> > > > It installed CUPS, but the rest of my LAN is using LPRng.
> > > > I want this machine to have the actual printer.  Am I
> > > > going to have to choose between CUPS and LPRng, or will
> > > > they play nicely together?
> > > > 
> > > > ++ kevin
> > > > 
> > > > _______________________________________________
> > > > Linux-users mailing list
> > > > Linux-users at linux-sxs.org
> > > > Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
> > > 
> > > 
> > > _______________________________________________
> > > Linux-users mailing list
> > > Linux-users at linux-sxs.org
> > > Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
> > > 
> > 
> > _______________________________________________
> > Linux-users mailing list
> > Linux-users at linux-sxs.org
> > Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
> 
> 
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
> 



More information about the Linux-users mailing list