For many years, now, I've run a CUPS server on my LAN, that any distro of Linux I've switched on has managed to find the printers it publishes, without me having to do any client configuration on the PC, other than making sure the firewall isn't in the way.
The CUPS server advertises itself, the clients find it, automatically, and when I want to print something, there's a list of available printers that I can print to. This is how it's supposed to work.
Fedora 20, however, finds nothing. I don't want to have to go around configuring all the clients, and all the user accounts on each of the clients. That's a really dumb way of doing things, something that CUPS and Linux used to manage to avoid.
Nor do I want to play silly buggers with Avahi. None of the printers are UPnP/zeroconf thingummies, nor the print server.
What is wrong with the Fedora 20 CUPS client?
On 05/21/14 15:56, Tim wrote:
For many years, now, I've run a CUPS server on my LAN, that any distro of Linux I've switched on has managed to find the printers it publishes, without me having to do any client configuration on the PC, other than making sure the firewall isn't in the way.
The CUPS server advertises itself, the clients find it, automatically, and when I want to print something, there's a list of available printers that I can print to. This is how it's supposed to work.
Fedora 20, however, finds nothing. I don't want to have to go around configuring all the clients, and all the user accounts on each of the clients. That's a really dumb way of doing things, something that CUPS and Linux used to manage to avoid.
Nor do I want to play silly buggers with Avahi. None of the printers are UPnP/zeroconf thingummies, nor the print server.
What is wrong with the Fedora 20 CUPS client?
I'm not 100% clear on what you're saying.
I think you are saying you have a CUPS print server set up on your LAN on a system running some version of Linux. And, the CUPS server is setup to share the printer to all systems on the LAN.
I think you are saying that F20 client systems are unable to detect the network printer when you run something like "system-config-printer" and try to add a printer. The F20 client systems' firewall has been modified to allow ipp-client packets.
I ask this since I've got a Synology NAS running a CUPS server and sharing an HP printer. My F20 systems are able to detect the printer just fine.
On Wed, 2014-05-21 at 16:30 +0800, Ed Greshko wrote:
I'm not 100% clear on what you're saying.
I think you are saying you have a CUPS print server set up on your LAN on a system running some version of Linux. And, the CUPS server is setup to share the printer to all systems on the LAN.
Correct. And that's been working brilliantly, for many years.
I think you are saying that F20 client systems are unable to detect the network printer when you run something like "system-config-printer" and try to add a printer. The F20 client systems' firewall has been modified to allow ipp-client packets.
Kind of... I'm not trying to manually add a printer, I don't want to do that. I want to open the, say "print" document item in the file menu and have the print-this-file-window, that pops up, show me the printers available on my server, so I can choose which one to print to. The same as it has done for many years, on prior versions of Fedora, and other distros (e.g. Ubuntu, CentOS).
Normally, CUPS doesn't require clients to add printers, clients automatically find all the printers that any local CUPS servers provide, and present them in your list of where to print to.
Yes, you can manually add printers, but that can get in the way of automatic discovery, or leave you with multiple instances of a printer being listed (those you've added, plus the ones it found).
Oddly, this MATE installation doesn't pre-install anything for configuring a printer, there is no system-config-printer, nor equivalent, there's only the http://localhost:631/ CUPS interface.
I ask this since I've got a Synology NAS running a CUPS server and sharing an HP printer. My F20 systems are able to detect the printer just fine.
I now have it working, thanks to Thomas Woerner's message. I'd already started the CUPS service (which wasn't set to run at boot, by default), but didn't know about another service that needed starting. Namely, the "cups-browsed.service". These four commands are my solution:
systemctl enable cups systemctl start cups systemctl enable cups-browsed systemctl start cups-browsed
I'm running the MATE spin of Fedora 20. I've done minimal customisation, and I haven't removed any software that I can recall, certainly no configurators.
On 05/21/2014 09:56 AM, Tim wrote:
For many years, now, I've run a CUPS server on my LAN, that any distro of Linux I've switched on has managed to find the printers it publishes, without me having to do any client configuration on the PC, other than making sure the firewall isn't in the way.
The CUPS server advertises itself, the clients find it, automatically, and when I want to print something, there's a list of available printers that I can print to. This is how it's supposed to work.
Fedora 20, however, finds nothing. I don't want to have to go around configuring all the clients, and all the user accounts on each of the clients. That's a really dumb way of doing things, something that CUPS and Linux used to manage to avoid.
Nor do I want to play silly buggers with Avahi. None of the printers are UPnP/zeroconf thingummies, nor the print server.
What is wrong with the Fedora 20 CUPS client?
Please make sure to enable and start the cups-browsed service. This is needed nowadays to have the CUPS protocol and part of the cups-filters package.
For the firewall, just enable the ipp-client service in the zone you are using - if not enabled already.
Thomas
Tim:
What is wrong with the Fedora 20 CUPS client?
Thomas Woerner:
Please make sure to enable and start the cups-browsed service. This is needed nowadays to have the CUPS protocol and part of the cups-filters package.
Aha! That was the culprit, a new service that I didn't know about, and it's working (well, now, at least, hopefully it stays that way).
For the firewall, just enable the ipp-client service in the zone you are using - if not enabled already.
Yes, I had already done that. And just as well that I know what IPP means, there's no hints in the firewall GUI. Actually, on that note, there's a scarcity of pop-up tool-tips in MATE, and not all aspects of GUIs are understandable without such help, or documentation.
Tim wrote:
For many years, now, I've run a CUPS server on my LAN, that any distro of Linux I've switched on has managed to find the printers it publishes, without me having to do any client configuration on the PC, other than making sure the firewall isn't in the way.
The CUPS server advertises itself, the clients find it, automatically, and when I want to print something, there's a list of available printers that I can print to. This is how it's supposed to work.
Fedora 20, however, finds nothing. I don't want to have to go around configuring all the clients, and all the user accounts on each of the clients. That's a really dumb way of doing things, something that CUPS and Linux used to manage to avoid.
Nor do I want to play silly buggers with Avahi. None of the printers are UPnP/zeroconf thingummies, nor the print server.
What is wrong with the Fedora 20 CUPS client?
See http://fedoraproject.org/wiki/Features/CUPS1.6
Sounds like you may want to install/configure cups-browsed
-- Rex
Tim:
What is wrong with the Fedora 20 CUPS client?
Rex Dieter:
See http://fedoraproject.org/wiki/Features/CUPS1.6
Sounds like you may want to install/configure cups-browsed
Thanks for the link, but the problem has been resolved. All I had to do was *start* that service going. Neither it, nor just the base CUPS service were enabled.
-
Ed Greshko -
Rex Dieter -
Thomas Woerner -
Tim