From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040808 Firefox/0.9.3 Description of problem: When sharing is enabled for a locally connected printer, ipp:udp is opened in iptables, but ipp:tcp is not. The effect is that the printer is viewable from client machines, but jobs queue on the client without printing. Opening ipp:tcp on the server in system-config-securitylevel causes the client's queue to flush and all jobs to print. Also allows client's eggcups to view job status, which it won't do without the TCP port open. Version-Release number of selected component (if applicable): system-config-printer-0.6.116-1 How reproducible: Always Steps to Reproduce: 1. Use system-config-printer to enable sharing. 2. Check firewall status with "service iptables status". 3. Print a job to the shared printer from another machine via IPP. Actual Results: In step 2, ipp:udp is open, but ipp:tcp is not. In step 3, job hangs in queue. Client's eggcups shows unknown name and size. Expected Results: In step 2, probably ipp:tcp should be open as well. In step 3, job should print and eggcups should show proper name and size. Additional info:
system-config-printer doesn't open any ports at all, because there is no infrastructure to do so. (I've been saying this for *ages*.)
Yeah we should sort for FC4.
*** This bug has been marked as a duplicate of 90946 ***