<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ASA denying tcp traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-denying-tcp-traffic/m-p/2135351#M395229</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Remco,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing here is that the ASA is torning a connection down as he is receiving a Reset packet from an inside host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nov 21 18:31:12 vpn : Nov 21 18:31:12 CEST: %ASA-session-6-302014: Teardown TCP connection 10627309 for outside:199.38.223.43/443 to inside:10.0.4.51/50978 duration 0:00:09 bytes 722969 &lt;EM&gt;&lt;STRONG style="text-decoration: underline; "&gt;TCP Reset-I&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG style="text-decoration: underline; "&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Now I would recommend you to do captures in order to determine if is the ASA the one sending the TCP reset packet as this is expected when you have the "service reset command".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the TCP statebypass, yes that could solve it but my recommendation would be to track this down by creating captures but you could try the TCP statebypass is this is need it ASAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Nov 2012 00:43:41 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-11-23T00:43:41Z</dc:date>
    <item>
      <title>ASA denying tcp traffic</title>
      <link>https://community.cisco.com/t5/network-security/asa-denying-tcp-traffic/m-p/2135350#M395225</link>
      <description>&lt;P&gt;Some of my users were complaining their software was not working correct. It retrieves file from a remote host and then constructs a model from these files. Retrieving and constructing behind our ASA5510 resulted in a corrupt model while the same actions at home (where they don't have a ASA) always works.&lt;/P&gt;&lt;P&gt;I tracked down (at least i think i did) the problem to these messages from the syslog:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:02 vpn : Nov 21 18:31:02 CEST: %ASA-session-6-302013: Built outbound TCP connection 10627309 for outside:199.38.223.43/443 (199.38.223.43/443) to inside:10.0.4.51/50978 (10.0.4.51/50978) &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:12 vpn : Nov 21 18:31:12 CEST: %ASA-session-6-302014: Teardown TCP connection 10627309 for outside:199.38.223.43/443 to inside:10.0.4.51/50978 duration 0:00:09 bytes 722969 TCP Reset-I &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:12 vpn : Nov 21 18:31:12 CEST: %ASA-session-6-106015: Deny TCP (no connection) from 199.38.223.43/443 to 10.0.4.51/50978 flags FIN ACK&amp;nbsp; on interface outside &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:12 vpn : Nov 21 18:31:12 CEST: %ASA-session-6-106015: Deny TCP (no connection) from 199.38.223.43/443 to 10.0.4.51/50978 flags ACK&amp;nbsp; on interface outside &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:38 vpn : Nov 21 18:31:38 CEST: %ASA-session-6-302013: Built outbound TCP connection 10627324 for outside:199.38.223.43/443 (199.38.223.43/443) to inside:10.0.4.51/50979 (10.0.4.51/50979) &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Nov 21 18:31:43 vpn : Nov 21 18:31:43 CEST: %ASA-session-6-302014: Teardown TCP connection 10627324 for outside:199.38.223.43/443 to inside:10.0.4.51/50979 duration 0:00:05 bytes 418328 TCP FINs&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the connection is not nicely closed and the remote host is not sending all files or the cliënt is not retrieving all the files correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After searching a lot i added &lt;SPAN style="font-family: courier new,courier;"&gt;sysopt connection timedwait&lt;/SPAN&gt;, but this does not seem to change anything, i suspected 106028 Deny TCP (Connection marked for deletion) messages, but can't find them in the syslog.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My configuration is pretty straightforward with a wireless AP &amp;gt; ASA5510 &amp;gt; Cisco871 &amp;gt; internet so there is no asynchronous routing on our side.&lt;/P&gt;&lt;P&gt;Cisco Adaptive Security Appliance Software Version 8.4(2)&lt;/P&gt;&lt;P&gt;Device Manager Version 6.4(5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone help me resolving these Deny TCP messages? Or is the only solution to disable statefull inspection for certain hosts, which is not my preferred solution?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:26:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-denying-tcp-traffic/m-p/2135350#M395225</guid>
      <dc:creator>mazzzterrr</dc:creator>
      <dc:date>2019-03-12T00:26:54Z</dc:date>
    </item>
    <item>
      <title>ASA denying tcp traffic</title>
      <link>https://community.cisco.com/t5/network-security/asa-denying-tcp-traffic/m-p/2135351#M395229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Remco,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing here is that the ASA is torning a connection down as he is receiving a Reset packet from an inside host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nov 21 18:31:12 vpn : Nov 21 18:31:12 CEST: %ASA-session-6-302014: Teardown TCP connection 10627309 for outside:199.38.223.43/443 to inside:10.0.4.51/50978 duration 0:00:09 bytes 722969 &lt;EM&gt;&lt;STRONG style="text-decoration: underline; "&gt;TCP Reset-I&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG style="text-decoration: underline; "&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Now I would recommend you to do captures in order to determine if is the ASA the one sending the TCP reset packet as this is expected when you have the "service reset command".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the TCP statebypass, yes that could solve it but my recommendation would be to track this down by creating captures but you could try the TCP statebypass is this is need it ASAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 00:43:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-denying-tcp-traffic/m-p/2135351#M395229</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-23T00:43:41Z</dc:date>
    </item>
  </channel>
</rss>

