<?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 I have resolved this issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537092#M927501</link>
    <description>&lt;P&gt;I have resolved this issue now. I'd had a bad/busy day and wasn't thinking clearly. I'd put the source port as the original rather than using 1-65535.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for getting in touch.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Sep 2014 15:39:53 GMT</pubDate>
    <dc:creator>efusesolutions</dc:creator>
    <dc:date>2014-09-19T15:39:53Z</dc:date>
    <item>
      <title>asa blocking inbound</title>
      <link>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537090#M927495</link>
      <description>&lt;P&gt;I have inbound traffic unable to make a connection from anywhere despite a rule allowing so.&lt;/P&gt;&lt;P&gt;The ACL is set-up is&amp;nbsp;being hit but the ASA is still discarding the connection with the following information within the log:&lt;/P&gt;&lt;P&gt;The ASA discared a TCP packet that has no associated connection in the ASA connection table.&lt;/P&gt;&lt;P&gt;The result is that I cannot get a connection to our CCTV equipment on a specific port.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone assist with this.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:16:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537090#M927495</guid>
      <dc:creator>efusesolutions</dc:creator>
      <dc:date>2020-02-21T13:16:49Z</dc:date>
    </item>
    <item>
      <title>just so i can better wrap my</title>
      <link>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537091#M927499</link>
      <description>&lt;P&gt;just so i can better wrap my head around your problem,&amp;nbsp;&lt;/P&gt;&lt;P&gt;is the rule on the outside interface or the inside interface?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Sep 2014 17:48:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537091#M927499</guid>
      <dc:creator>christopher jardine</dc:creator>
      <dc:date>2014-09-16T17:48:17Z</dc:date>
    </item>
    <item>
      <title>I have resolved this issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537092#M927501</link>
      <description>&lt;P&gt;I have resolved this issue now. I'd had a bad/busy day and wasn't thinking clearly. I'd put the source port as the original rather than using 1-65535.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for getting in touch.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Sep 2014 15:39:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-blocking-inbound/m-p/2537092#M927501</guid>
      <dc:creator>efusesolutions</dc:creator>
      <dc:date>2014-09-19T15:39:53Z</dc:date>
    </item>
  </channel>
</rss>

