topic Re: fw_conn_post_inspect Reason: fwconn_key_init_links (OUTBOUND) failed; in Firewall and Security Management https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13816#M964 <HTML><HEAD></HEAD><BODY><P>yes and we found a resolution R80.10 Take_154 solved this issue for us. </P><P></P><P>Was a translation being dropped for some reason</P></BODY></HTML> Fri, 14 Dec 2018 17:20:48 GMT Tom_Stala 2018-12-14T17:20:48Z fw_conn_post_inspect Reason: fwconn_key_init_links (OUTBOUND) failed; https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13814#M962 <HTML><HEAD></HEAD><BODY><P>We have a VSX setup running R80.10</P><P>We have some translation issues that have show very ugly results that have led us to reboot the firewalls.</P><P></P><P>We have been trying to track down issues with the Firewalls seem to be dropping traffic when going outbound.</P><P></P><P>There is one program that runs a new lets say test credit card every 45 seconds and it is running 24 hours a day and we have been getting 4 failed communications.</P><P></P><P>it shows as accepted in the logs but there is no address translations so we run a zdebug forever to fid that it is the firewall dropping communications.</P><P></P><P>other seen issue</P><P>two servers sending an ICMP for monitoring up status.</P><P>Server A and Server B behind same IP Hide address</P><P></P><P>we turned B off</P><P>Traffic from A was going out fine and then coming back it was getting translated to B<BR />Rebooted the firewall due to a lot of communication errors and this fixed this issue.</P><P></P><P>But we are looking for a answer as to what can we do to fix this issue</P><P></P><P>&nbsp;<SPAN style="font-size: 11pt;">fw_conn_post_inspect Reason: fwconn_key_init_links (OUTBOUND) failed;</SPAN></P></BODY></HTML> Thu, 06 Dec 2018 15:14:41 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13814#M962 Tom_Stala 2018-12-06T15:14:41Z Re: fw_conn_post_inspect Reason: fwconn_key_init_links (OUTBOUND) failed; https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13815#M963 <HTML><HEAD></HEAD><BODY><P>Have you opened a TAC case?</P></BODY></HTML> Fri, 07 Dec 2018 00:39:56 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13815#M963 PhoneBoy 2018-12-07T00:39:56Z Re: fw_conn_post_inspect Reason: fwconn_key_init_links (OUTBOUND) failed; https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13816#M964 <HTML><HEAD></HEAD><BODY><P>yes and we found a resolution R80.10 Take_154 solved this issue for us. </P><P></P><P>Was a translation being dropped for some reason</P></BODY></HTML> Fri, 14 Dec 2018 17:20:48 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/fw-conn-post-inspect-Reason-fwconn-key-init-links-OUTBOUND/m-p/13816#M964 Tom_Stala 2018-12-14T17:20:48Z