[cups.general] clients get stuck when server reboots

[henri]

An alternative solution would be to setup the queues (locally) on the  
machines with a tool like PrinterSetup. However, hopefully someone  
with more knowledge regarding CUPS browsing will be able to assist you  
with this issue and you will not need to deploy local queues to the  
machines.

Hope this helps.

> I forgot to mention one really important piece of information.  The  
> linux clients on net-193 (131.215.193.xx) don't get stuck.  Only the  
> linux clients on net-194 (131.215.194.xx).  So the problem has  
> something to do with the fact that our print server is physically  
> connected to more than one network.
>
> One thing I've noticed about the linux clients on the different  
> network, is that
> the linux computers on net-193 report this to error_log:
> I [29/Mar/2009:04:02:04 -0700] Added remote printer "4th_floor"...
>
> But a computer on net-194 will report this for the same printer:
> I [29/Mar/2009:04:02:13 -0700] Added remote printer "4th_floor"...
> I [29/Mar/2009:04:02:13 -0700] Added remote printer  
> "4th_floor at cahillprint"...
> I [29/Mar/2009:04:02:13 -0700] Added implicit class "4th_floor"...
>