[Leaplist] CUPS printer status

[Dan Cherry]

Dan Cherry wrote:
> Hi,
> I've had a CUPS printer status that reads...
> 
> Ready: Network host '192.168.1.110' is busy; will retry in 30 seconds...
> 
> since yesterday afternoon.
> I've restarted CUPS, turned the printer off/on, Added the client IP 
> address to cupsd.conf, and assorted other desperate attempts found while 
> googling.
> 
> This is an Ubuntu system (I've run the Cups-cleanup), and the printer 
> works from the linux system it's attached to, and is 'visible' by all 
> other Linux systems.
> 
> If I 'Stop' the printer, all other systems immediately see it as 
> 'paused'.  When I restart the printer the other systems immediately see 
> it as ready: but with the busy status described above. The 'other' 
> systems just put the job in a local queue when they attempt to print. 
> The cupsd.conf file is below.
> 
> If anyone has run into this, and found a solution, could you share it, 
> please?
> 
> Thanks,
I think Ray is right.  I'm finding out that the Ubuntu team modifies
software and tends to lock things down, even though that software would
work on other distros without the changes.  (Ubuntu is not the only one
who does this, so this isn't meant as a flame).  I did find out how to 
unlock
the web admin Cups software, but that wasn't the problem.  Remote admin
still does _not_ work on my systems, making me think I have port issues.
  nmap shows port 631 open, but any attempt to access the server through 
port 631 results in a Forbidden 403.  Gasp!

Before I chase any further, I'd like to find out if anybody on the list
has two ubuntu systems (dapper or edgy) with a printer that works from
both machines over ipp.  Maybe I'm trying to fix something that doesn't 
work anywhere ;-)

If anybody has that scenario, would you be willing to post your
cupsd.conf file (and its includes)?  TIA

-- 
Dan Cherry
dscherry (@) bellsouth.net

Finding a solution to a problem doesn't solve the problem...
Implementing the solution solves the problem.