You should NOT be using TCP for sending syslogs. TCP syslogging is only used with the PFSS syslog server and is designed for those users who want their PIX to stop passing traffic if connectivity is lost to the syslog server.
Consequently, you will probably want to change your logging to udp.
Here's an excerpt of the relevant documentation on the pix logging command, as well as a link:
If you are using TCP as the logging transport protocol, the PIX Firewall stops passing traffic as a security measure if any of the following error conditions occur: the PIX Firewall is unable to reach the syslog server; the syslog server is misconfigured (such as with PFSS, for example); or the disk is full. (UDP-based logging does not prevent the PIX Firewall from passing traffic if the syslog server fails.)
To enable the PIX Firewall to pass traffic again, do the following:
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...