A remote client tried legitmately to 3 way handshake a TCP connection through our firwall and instead of going into UP state, the TCP connection failed, with the Pix "Show conn" flags showing "SaA" on the client side and "SaAB" flags on the server side. We think we can decode these flags - but we cant figure out the causation. No devices went down or failed-over to my knowledge, and there appears to have been no other reported events occuring that could have caused or impacted this situation. Any ideas anyone as to what may have caused the TCP connection attempt to have failed? It seemed to right itself also after a while - we did nothing...but I need some answers for the suits when it happens again - thanks firstname.lastname@example.org
SaAB-->initiat sym from outside, and firewall waiting for synack, there was no returns reply sent to firewall,the default gateway got missing, check for routing issues...is the client/server having dual NICs
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...