<?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 Bad Request Error in NAT Binding policy configuration in Prisma SD-WAN Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/bad-request-error-in-nat-binding-policy-configuration/m-p/538829#M79</link>
    <description>&lt;P&gt;Has anyone else run into an issue where they are unable to add new prefix bindings to sites in the NAT policy page? When I attempt to add a new one, it returns a 400 Bad Request error. I have a ticket open with PA support, but this is causing major issues, and I'm hoping someone else has run into it and has a fix or a workaround. Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 14 Apr 2023 18:49:52 GMT</pubDate>
    <dc:creator>GBowman</dc:creator>
    <dc:date>2023-04-14T18:49:52Z</dc:date>
    <item>
      <title>Bad Request Error in NAT Binding policy configuration</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/bad-request-error-in-nat-binding-policy-configuration/m-p/538829#M79</link>
      <description>&lt;P&gt;Has anyone else run into an issue where they are unable to add new prefix bindings to sites in the NAT policy page? When I attempt to add a new one, it returns a 400 Bad Request error. I have a ticket open with PA support, but this is causing major issues, and I'm hoping someone else has run into it and has a fix or a workaround. Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2023 18:49:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/bad-request-error-in-nat-binding-policy-configuration/m-p/538829#M79</guid>
      <dc:creator>GBowman</dc:creator>
      <dc:date>2023-04-14T18:49:52Z</dc:date>
    </item>
  </channel>
</rss>

