Robert Heller wrote:
I manage a bunch of workstations at the Wendell Free Library. They are all diskless, boot via PXE and mount all of their file systems via NFS from a server. All of the machines are 32-bit and run CentOS (fully up-to-date running 5.10). There are two printers with queues managed on the server. The server 'shares' these printers on the local LAN (eg with all of the workstations). After the upgrade to 5.10, *one* of the machine no longer sees the printers. *Nothing* is different about its configuration files, since these files are mounted via NFS from the server, *like all of the other workstations*. The other workstations all see the printers shared by the server. I don't understand what is going on here. And cannot find the problem.
lpstat -t on the server yields:
scheduler is running system default destination: BlackandWhiteLaserjet device for BlackandWhiteLaserjet: socket://192.168.1.246:9100 device for Officejet_Color: socket://192.168.1.253 BlackandWhiteLaserjet accepting requests since Tue 19 Jun 2012 03:27:17 PM EDT Officejet_Color accepting requests since Tue 24 Jul 2012 04:43:33 PM EDT printer BlackandWhiteLaserjet is idle. enabled since Tue 19 Jun 2012 03:27:17 PM EDT printer Officejet_Color is idle. enabled since Tue 24 Jul 2012 04:43:33 PM EDT
lpstat -t on the bum workstation yields:
lpstat: No destinations added. lpstat: No destinations added. lpstat: No destinations added. lpstat: No destinations added. scheduler is running no system default destination
and lpstat -t on a working workstation yields:
scheduler is running system default destination: BlackandWhiteLaserjet device for BlackandWhiteLaserjet: ipp://192.168.1.254:631/printers/BlackandWhiteLaserjet device for Officejet_Color: ipp://192.168.1.254:631/printers/Officejet_Color BlackandWhiteLaserjet accepting requests since Sun 10 Nov 2013 10:26:03 AM EST Officejet_Color accepting requests since Sun 10 Nov 2013 10:26:04 AM EST printer BlackandWhiteLaserjet is idle. enabled since Sun 10 Nov 2013 10:26:03 AM EST printer Officejet_Color is idle. enabled since Sun 10 Nov 2013 10:26:04 AM EST
The server's /etc/cups/cupsd.conf looks like this:
{snip part of cupsd.conf}
<Location /admin> Allow from localhost Allow from 192.168.1.27 Allow from 192.168.1.28 Allow from 192.168.1.29 Allow from 192.168.1.5 # Allow remote administration... Order allow,deny Allow all
</Location>
{snip another bit of cupsd.conf}
and the cupsd.conf (shared by ALL of the workstations) looks like this:
{snip workstation cupsd.conf}
A shot in the dark here. "Somehow" the errant workstation is different. Is its IP address outside this list
Allow from 192.168.1.27 Allow from 192.168.1.28 Allow from 192.168.1.29 Allow from 192.168.1.5
Ken Allow from 192.168.1.254