<?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: Why No-NAT rule is required to communicate between On-Prem to VPC (in GCP) in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213268#M35267</link>
    <description>&lt;P&gt;The obvious guess would be that your NAT policy isn't specific enough in other areas but is a little difficult to say without knowing the exact composition of the policy.&lt;/P&gt;
&lt;P&gt;The other could be the implied inclusion of the Gateway address in the encryption domain could be causing a challenge.&lt;/P&gt;</description>
    <pubDate>Mon, 06 May 2024 11:33:51 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2024-05-06T11:33:51Z</dc:date>
    <item>
      <title>Why No-NAT rule is required to communicate between On-Prem to VPC (in GCP)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213238#M35259</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In GCP we have our own VPC where we have Checkpoint in cluster state. There is a connectivity with our On-Prem environment via VPN on Direct connect.&lt;/P&gt;&lt;P&gt;While Communicating the resources behind the Checkpoint gateway from On-Prem we need to configure a No-NAT rule for it work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why do we require a No-NAT rule in this scenario?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Baljinder Singh Bimbh&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 06:44:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213238#M35259</guid>
      <dc:creator>ballu</dc:creator>
      <dc:date>2024-05-06T06:44:38Z</dc:date>
    </item>
    <item>
      <title>Re: Why No-NAT rule is required to communicate between On-Prem to VPC (in GCP)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213268#M35267</link>
      <description>&lt;P&gt;The obvious guess would be that your NAT policy isn't specific enough in other areas but is a little difficult to say without knowing the exact composition of the policy.&lt;/P&gt;
&lt;P&gt;The other could be the implied inclusion of the Gateway address in the encryption domain could be causing a challenge.&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 11:33:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213268#M35267</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2024-05-06T11:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why No-NAT rule is required to communicate between On-Prem to VPC (in GCP)</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213270#M35268</link>
      <description>&lt;P&gt;I think if you sent us basic diagram with explanation of traffic flowing, it would certainly help.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 11:46:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Why-No-NAT-rule-is-required-to-communicate-between-On-Prem-to/m-p/213270#M35268</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-05-06T11:46:53Z</dc:date>
    </item>
  </channel>
</rss>

