(In reply to comment #0)
> I configured my network with shared printing. I found out that I had not opened
> the right ports on my print server, but the real problem was that cups-manager
> hanged
This is really a problem of how TCP is designed. If you completely block packets
to the right port, your computer will not get any ICMP message that the port is
invalid, and thus will get the usual 30 second timeout. Does it recover after 30
seconds?
> and even crashed Firefox when I tried to print a page
That's more serious. That means you tried to print something in Firefox?
(In reply to comment #0)
> I configured my network with shared printing. I found out that I had not opened
> the right ports on my print server, but the real problem was that cups-manager
> hanged
This is really a problem of how TCP is designed. If you completely block packets
to the right port, your computer will not get any ICMP message that the port is
invalid, and thus will get the usual 30 second timeout. Does it recover after 30
seconds?
> and even crashed Firefox when I tried to print a page
That's more serious. That means you tried to print something in Firefox?