<?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: PA sending TCP RST in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27764#M20240</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;not for this traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2015 11:53:34 GMT</pubDate>
    <dc:creator>Jakub_Kopka</dc:creator>
    <dc:date>2015-01-26T11:53:34Z</dc:date>
    <item>
      <title>PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27762#M20238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've run into a following issue. We have a Juniper MAG box communicating with a web server and a rule in place allowing this communication (source Juniper, destination any production IP, on any port). I can also see in the traffic log that the communication is accepted. However when I did a packet capture on the FW I saw the following:&lt;/P&gt;&lt;P&gt;Receiving capture:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="PA_recv.jpg" class="image-0 jive-image" height="78" src="https://live.paloaltonetworks.com/legacyfs/online/18002_PA_recv.jpg" style="height: 78px; width: 912.452830188679px;" width="912" /&gt;&lt;/P&gt;&lt;P&gt;Transmitting capture:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="PA_transm.jpg" class="image-1 jive-image" height="87" src="https://live.paloaltonetworks.com/legacyfs/online/18003_PA_transm.jpg" style="height: 87px; width: 914.237288135593px;" width="914" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea why is this happening or what I am missing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2015 11:18:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27762#M20238</guid>
      <dc:creator>Jakub_Kopka</dc:creator>
      <dc:date>2015-01-26T11:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27763#M20239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the monitor tab, filter the threat logs and the url logs for these ip addresses and see if there are any hits.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2015 11:50:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27763#M20239</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2015-01-26T11:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27764#M20240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;not for this traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2015 11:53:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27764#M20240</guid>
      <dc:creator>Jakub_Kopka</dc:creator>
      <dc:date>2015-01-26T11:53:34Z</dc:date>
    </item>
    <item>
      <title>Re: PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27765#M20241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then I would open a support case.&amp;nbsp; When the PA generates a reset we should have a log from the process that is creating the reset.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here your policy, threat and url logs are clean so it would appear that this is a bug that needs to be investigated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2015 11:56:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27765#M20241</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2015-01-26T11:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27766#M20242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jakub&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you running AppID version 482-2533? Try rolling back to a previous version, we had a similar issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 02:55:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27766#M20242</guid>
      <dc:creator>SteveMc</dc:creator>
      <dc:date>2015-01-27T02:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: PA sending TCP RST</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27767#M20243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks. This has helped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;edit:&lt;/P&gt;&lt;P&gt;It's a bug - should be fixed in PanOS 6.1.3 with the AppID 482.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 05:38:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-sending-tcp-rst/m-p/27767#M20243</guid>
      <dc:creator>Jakub_Kopka</dc:creator>
      <dc:date>2015-01-27T05:38:14Z</dc:date>
    </item>
  </channel>
</rss>

