<?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: Odd NAT issue... in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243847#M69664</link>
    <description>&lt;P&gt;have you checked your upstream device that there's no static arp entry or 2 sources fighting for the same ip?&lt;/P&gt;</description>
    <pubDate>Wed, 19 Dec 2018 14:15:02 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2018-12-19T14:15:02Z</dc:date>
    <item>
      <title>Odd NAT issue...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243832#M69658</link>
      <description>&lt;P&gt;Had a very odd issue yesterday,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I created two new Bi-Directional nat rules [seperate NAT IP's] to the outside world, one worked fine the other did not...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One server could not get to the outside world..&lt;/P&gt;&lt;P&gt;The NAT matched [OK],&lt;BR /&gt;The Security Rule Matched [OK],&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Searched the configs [and old ones]&amp;nbsp;for any possible clash with the NAT IP "X.X.X.115", Nothing.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I could see some traffic had started&amp;nbsp;hitting that external address, but stopped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nothing in session browser.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On a hunch I changed the NAT IP "X.X.X.117" And eveything now works..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can't fathom what possibly could have been wrong as routing must be fine, and the previous address was not blocked by security or used elsewhere...&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I may swap it back and have a play.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nat1.jpg" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/17977i561719792F6B3ACB/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="nat1.jpg" alt="nat1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nat2.jpg" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/17979iC595EFF093641659/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="nat2.jpg" alt="nat2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 10:35:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243832#M69658</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2018-12-19T10:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: Odd NAT issue...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243847#M69664</link>
      <description>&lt;P&gt;have you checked your upstream device that there's no static arp entry or 2 sources fighting for the same ip?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 14:15:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243847#M69664</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2018-12-19T14:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Odd NAT issue...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243863#M69667</link>
      <description>&lt;P&gt;You know that moment when something dawns on you that should be bleeding obvious!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pinging the external IP got a solid response.&lt;/P&gt;&lt;P&gt;Traceroute got same results to 115 and 117.&lt;/P&gt;&lt;P&gt;Packet capture shows nothing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What on earth could be resp......Oh wait.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The clue should have been in the Source of the traffic shown briefly yesterday. It was from our SIP telco provider that used to be on the firewall [although on a different IP]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Someone [ME] Moved this SIP service back in August to a different device as the Palo kept locking up the SIP/RTP session after a few weeks...... That other device has the IP address..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking in the system log of the PA, I found "Received Conflicting ARP on interface...... Duplicating IP...."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So mystery solved, no interruption to the Phone service fortunatly..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 16:03:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/odd-nat-issue/m-p/243863#M69667</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2018-12-19T16:03:49Z</dc:date>
    </item>
  </channel>
</rss>

