Cups with local and remote printers

[David Jansen]

Thanks, I'll give it a try. The BrowsePoll option was one that I didn't
have in my configuration. And if that doesn't work, I may have to set up
an additional cups server on each subnet as others have suggested

I'm still a bit curious why it worked without additional settings on
Fedora 8 (and earlier)

David

PS: also thanks to others who resonded, but I already ruled out firewall
(and selinux) issues.

On Thu, Dec 04, 2008 at 07:41:05AM -0600, Aaron Konstam wrote:
> On Wed, 2008-12-03 at 17:55 +0100, David Jansen wrote:
> > I came across another weird problem: here at our university department,
> > we have a few hundred Linux machines, most of them Fedora, and in the
> > process of being upgraded to fedora 10.
> > Now my problem is printing. There is a central printserver (running RHEL5)
> > and making a fedora pc a client (by placing a printserver entry in
> > /etc/cups/client.conf) makes it possible to access all the printers on
> > the printserver.
> > However, a couple of machines have a local printer as well. That used to
> > work in Fedora 8: set up the local printer (probably autodetected on
> > install anyway), make sure it is shared, and then make the machine a
> > cups client so everything goes to the printserver. A solution I found in
> > some howto on the net, but I can't remember where.
> > However, in fedora 10, this no longer works. A computer seems to be a
> > client of the central printserver, or it is not a client, and it can see
> > its own printer, and any browsed cups printers on the local net.
> > (and, since our network consists of a couple of subnets in multiple
> > buildings, just relying on cups to find all printers by browsing on the
> > local subnet is not a complete solution).
> > 
> > Does anyone know how to do this? The thing is ofcourse, that cups has
> > not had a major upgrade between fedora 8 and fedora 10, and I see
> > nothing in the changelogs that indicates a change of behaviour.
> > 
> > David Jansen
> > 
> This can be done. I have one machine doing it. It requires a careful
> reading of the documentation for cupsd.conf on the client machine which
> is also its own server. Unfortunately I can't remember exactly what I
> did to make this work so the best I can do is to attach a copy of
> cupsd.conf on a machine that supports this configuration. Its central
> print server is 192.168.100 but can print to its local printer in
> addition.
> --
> =======================================================================
> Distress, n.: A disease incurred by exposure to the prosperity of a
> friend. -- Ambrose Bierce, "The Devil's Dictionary"
> =======================================================================
> Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam at sbcglobal.net