weird F12 printing problem

[Aaron Konstam]

On Mon, 2010-02-15 at 20:32 -0500, fred smith wrote: 
> On Mon, Feb 15, 2010 at 05:46:25PM -0600, Aaron Konstam wrote:
> > On Mon, 2010-02-15 at 11:20 -0500, fred smith wrote: 
> > > On Mon, Feb 15, 2010 at 04:12:54PM +0000, Tim Waugh wrote:
> > > > On Mon, 2010-02-15 at 04:07 -0800, Mike Cloaked wrote:
> > > > > > I don't know if this will help but sometimes I have found that a printer
> > > > > > seems to be shared  according to the Fedora printer admin interface but
> > > > > > does not work - in this situation going to localhost:631 in a browser and
> > > > > > selecting that the printer concerned is "published" as a shared printer
> > > > > > usually sorts this out for me.
> > > > 
> > > > For a CUPS printer to be usable by another machine, you need:
> > > > 
> > > > 1. the printer to be marked as 'Shared' (the Printer-> Shared checkbox)
> > > > 2. the CUPS server to 'Publish shared printers' (Server-> Settings...->
> > > > Public shared printers connected to this system)
> > > > 3. the firewall settings on the server to allow 'Network Printing
> > > > Server'
> > > > 4. the firewall settings on the client to allow 'Network Printing
> > > > Client'
> > > > 
> > > > Tim.
> > > > */
> > > > 
> > > 
> > > It's NOT a shared printer. it is attached to the LAN with its own IP address.
> > Even so it needs to shared on the server that is distributing its
> > services to the rest of the machines. Or are you connecting it to each
> > computer independently. In my opinion that is a bad idea and can cause
> > the problem you report. 
> 
> It only needs to be shared if all the other computers are printing
> via that share.
> 
> Since they AREN'T, it doesn't need to be shared.
> 
> the printer supports lpd, ipp/http, jetdirect, and probably a handful
> of other printing protocols, so it contains its own spool manager
> and works just peachy when all computers print directly to it.
But as you report it does not run  peachy from one machine. I agree the
printer can be printed to directly. I am just saying it sometimes causes
problems as you have reported. In my opinion even on a home LAN having
one of you machines as a print server is a good idea. I have done it
your way and caused a big mess.

The biggest problem with your approach is that when the printer
environment is done your way configurations on all the machines have to
be changed rather than only on one server machine. 
> 
> it spends about 99.999% of its time sitting idle. we don't print much
> here, and I doubt we've ever had two different systems printing to it
> at the same time. but even if we did, it would be expected to work fine,
> given its internal print spooling implementations.
> 



--
=======================================================================
If we see the light at the end of the tunnel, it's the light of an
oncoming train. -- Robert Lowell
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam at sbcglobal.net