[13.1] no cups network printig after update

after updating some packages via yast (including kernel) and and a reboot I am no longer able to print via network.

local printing on the server is possible.
network printing is still allowed on the server.

other computer on the network are however not able to print.
when trying to set up the print queue again on the remote computer via yast,
on on client yast tells me it can reach the server via port 631, but /var/log/cups/error_log says “Unable to connect to <server ip> on port 631”.
on a different client /var/log/cups/error_log says “CUPS-Get-Printers failed : Forbidden”

port 631 is allowed on the server as well as on the client.
(no changes had been made to firewall settings)

I’d be glad if anyone could help me to enable remote printing again.

sorry, I provided the wrong OS version:
server runs 12.3, the clients run 13.1

Well the obvious question is, what were the updates?

rpm -qa --last | head -n 30

Will list the last 30 updates.

after executing systemctl restart cups.service on the server I can print.

why didn’t that work after assessing the cups configuration via yast?

/var/log/cups/error_log on the client still says " Unable to connect to …"

Let us know if you get the same issue again after a client reboot.

…and check the status again as well at that time.

systemctl status cups

no, it didn’t occur after client reboot.

> systemctl status cups
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: active (running) since Fri, 2014-08-15 19:54:41 CEST; 17h ago
Main PID: 5546 (cupsd)
CGroup: name=systemd:/system/cups.service
└ 5546 /usr/sbin/cupsd -f

“normal” printing from the clients works, but on one of the clients, firefox freezes when trying to print.
looks like it can not connect connect to cups.
since the clients should be configured the same way, it might be an issue of firefox or one of the addons.

Good to know.

but on one of the clients, firefox freezes when trying to print.
looks like it can not connect connect to cups.
since the clients should be configured the same way, it might be an issue of firefox or one of the addons.

Okay, that sounds like a different issue.