<?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 Re: TCP Reset-I in PIX Log in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054803#M895232</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I attached the commands I entered (modified per my naming conventions) plus the output from sh run.  I faked some of the IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Oct 2008 00:25:22 GMT</pubDate>
    <dc:creator>doug.dockter</dc:creator>
    <dc:date>2008-10-15T00:25:22Z</dc:date>
    <item>
      <title>TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054794#M895216</link>
      <description>&lt;P&gt;Since switching ISPs and having to upgrade my PIX 515 from 7.0.2 to 7.2.4 for PPPOE support, I'm having issues receiving e-mails with attachments from a particular domain.  All I see in the PIX log is the following message:  Teardown TCP connection 1479120 for outside:193.246.239.75/34098 to inside:10.1.255.48/25 duration 0:16:14 bytes 87079 TCP Reset-I.  I'm not sure what is causing the reset.  &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:56:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054794#M895216</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2019-03-11T13:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054795#M895218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;tcp reser-i suggest a reset came from your email server.You would need to look into email server to see why it is generating the reset.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also,you can try disabling the inspect esmtp on asa,if that's enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do rate if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sushil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2008 20:50:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054795#M895218</guid>
      <dc:creator>suschoud</dc:creator>
      <dc:date>2008-10-10T20:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054796#M895220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm going to disable esmtp to see if that will help.  We use an IronPort device as our SMTP server.  There have been no configuration changes on it that I'm aware of.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2008 21:00:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054796#M895220</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-10T21:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054797#M895222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Disabling esmtp resolved the issue.  Was this a new feature of 7.0.4?  Should I leave this turned off globally or is there a way to tweak the setting to not check for certain IP addresses or email domains?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2008 21:12:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054797#M895222</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-10T21:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054798#M895224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here you go :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;considering 4.2.2.2 is the ip address of email domain to which you are facing issues sending email :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# policy-map global_policy&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap)# class inspection_default&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap-c)# no inspect esmtp&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# access-l 101 deny ip any host 4.2.2.2&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# access-l 101 permit ip any any&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# clas&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# class-map myesmtp&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-cmap)# mat&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-cmap)# match ac&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-cmap)# match access-list 101&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-cmap)# exit&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# poli&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# policy-map glo&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# policy-map globa&lt;/P&gt;&lt;P&gt;ASA5510-Single(config)# policy-map global_policy&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap)# clas&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap)# class myesmtp&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap-c)# ins&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap-c)# inspect esmtp&lt;/P&gt;&lt;P&gt;ASA5510-Single(config-pmap-c)#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pretty much you specify an access rule which define what traffic should be inspected by esmtp inspect.If there is a " deny " in access list,that traffic would be bypasses from inspection engine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do rate if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sushil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2008 21:53:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054798#M895224</guid>
      <dc:creator>suschoud</dc:creator>
      <dc:date>2008-10-10T21:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054799#M895226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the example Sushil.  I am having problems receiving e-mails FROM a domain.  In your example above you said it was for an issue with sending e-mails TO a domain.  Would the commands be the same?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 13:56:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054799#M895226</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-13T13:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054800#M895228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just replace :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l 101 deny ip any host 4.2.2.2 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l 101 deny ip  host 4.2.2.2 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.2.2.2 -&amp;gt; ip of the domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do rate helpful posts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Sushil&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 14:07:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054800#M895228</guid>
      <dc:creator>suschoud</dc:creator>
      <dc:date>2008-10-13T14:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054801#M895230</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if there is something wrong with the configuration commands you sent or I'm doing something wrong.  As soon as I enter the inspect esmtp command toward the bottom, all access to the internet seems to be blocked. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 18:48:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054801#M895230</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-13T18:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054802#M895231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the suggested commands in no way can block internet traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is access-l 101 already defined somewhere in your configuration ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure what is wrong.Can u post " sh run " command output ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sushil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 20:03:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054802#M895231</guid>
      <dc:creator>suschoud</dc:creator>
      <dc:date>2008-10-13T20:03:38Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054803#M895232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I attached the commands I entered (modified per my naming conventions) plus the output from sh run.  I faked some of the IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Oct 2008 00:25:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054803#M895232</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-15T00:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset-I in PIX Log</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054804#M895233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cisco tech support suggested the below changes and that resolved the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list esmtp_acl extended deny tcp host 193.246.239.72 any eq 25 &lt;/P&gt;&lt;P&gt;access-list esmtp_acl extended deny tcp host 193.246.239.73 any eq 25 &lt;/P&gt;&lt;P&gt;access-list esmtp_acl extended deny tcp host 193.246.239.74 any eq 25 &lt;/P&gt;&lt;P&gt;access-list esmtp_acl extended deny tcp host 193.246.239.75 any eq 25 &lt;/P&gt;&lt;P&gt;access-list esmtp_acl extended permit tcp any any eq 25&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Oct 2008 15:22:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-i-in-pix-log/m-p/1054804#M895233</guid>
      <dc:creator>doug.dockter</dc:creator>
      <dc:date>2008-10-27T15:22:37Z</dc:date>
    </item>
  </channel>
</rss>

