I recently updated several computers to FC21. Since then I have been having problems printing. I have a Brother laser printer connected via usb cable on pc1. I can print from here with no problem. From a different computer (pc2) on the same network I cannot print. I was able to create a link in the Print settings on pc2 but received an error during the defination process.

Transport endpoint is not connected

I have searched on the error but the problems are usually with SAMBA.
I ran dmesg and found the following error:
brcupsconfpt1[5776]: segfault at 44776f6c ip 00000000455f9d32 sp 00000000ffb9e51c error 6 in libc-2.20.so[45571000+1c5000]

As for accessing the other computer, I can ping pc1 from pc2 with no problem.
With nothing else to try, I disabled the firewall on both pcs and tried again. I got the same
error.
I can print from pc1.
I tried to print a test page from pc2 and when
I looked in the CUPS access log, I found this message

localhost - - [03/May/2015:16:40:50 -0400] "POST /printers/Brother-HL-L2360D-series HTTP/1.1" 200 426 Print-Job successful-ok

It looks like CUPS thinks the printer is working but I still get the 'Transport endpoint is not connected'. message

Where do I go from here?

I also have a printer on pc2 - an inkjet - and I can print a testpage on it from pc1.

I am guessing I have a setting wrong somewhere.

It should not be necessary to manually configure a networked CUPS printer at the client end, provided sharing has been enabled. Check /etc/cups/printers.conf to make sure that the desired printer is shared.

Review the CUPS printer sharing page

https://www.cups.org/documentation.p...VERSION=1.7&Q=

I figured out what the problem was - some firewall settings. Somehow 3 services in the fire wall got disabled on the pc with the printer attached. I enabled these settings and everything worked. The 3 services are ipp. ipp-client and mdns. I don't know how they got disabled. I hope this helps anyone else having the problem.

Glad that you got it working. In your first post you mentioned that you'd disabled the firewall during testing, so I discounted firewall issues.