<?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 Are both the source and in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599299#M205816</link>
    <description>&lt;P&gt;Are both the source and destination address downstream from your inside interface? If so, you need to have "same-security-traffic" enabled in your configuration. &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/command/reference/cmd_ref/s1.html#wp1421315"&gt;Reference&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Oct 2014 22:53:30 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2014-10-20T22:53:30Z</dc:date>
    <item>
      <title>ASA5550 TCP connection denied</title>
      <link>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599297#M205814</link>
      <description>&lt;P&gt;cisco ASA5550 Inbound TCP connection denied from 172.XX.XXX.2/3314 to 172.16.XX.XX/XXX&amp;nbsp;flags SYN &amp;nbsp;on interface inside&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:57:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599297#M205814</guid>
      <dc:creator>mohdghafoor</dc:creator>
      <dc:date>2019-03-12T04:57:36Z</dc:date>
    </item>
    <item>
      <title>Can you post a config, or at</title>
      <link>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599298#M205815</link>
      <description>&lt;P&gt;Can you post a config, or at least the ACLs that you have for either of those networks?&lt;/P&gt;&lt;P&gt;You may need to enable logging on those particular ACLs in order for me/us to figure out why these are being denied. &amp;nbsp;&lt;/P&gt;&lt;P&gt;See this about turning logging on. &amp;nbsp;It will give your logs more information, including which ACL is denying these packets&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/acl_logging.pdf&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2014 20:45:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599298#M205815</guid>
      <dc:creator>davebornack</dc:creator>
      <dc:date>2014-10-20T20:45:29Z</dc:date>
    </item>
    <item>
      <title>Are both the source and</title>
      <link>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599299#M205816</link>
      <description>&lt;P&gt;Are both the source and destination address downstream from your inside interface? If so, you need to have "same-security-traffic" enabled in your configuration. &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/command/reference/cmd_ref/s1.html#wp1421315"&gt;Reference&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2014 22:53:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5550-tcp-connection-denied/m-p/2599299#M205816</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-20T22:53:30Z</dc:date>
    </item>
  </channel>
</rss>

