<?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: PADR.exe do not create firewall rules in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305672#M8131</link>
    <description>&lt;P&gt;you give the vault details like IP and port during installation of DR module, alternatively you can  make the changes in vault.ini as well, restart the cyberark vault disaster recovery service and monitor if replication is happening, if yes you are good with the setup&lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2019 15:33:11 GMT</pubDate>
    <dc:creator>A.agarwal592645</dc:creator>
    <dc:date>2019-03-14T15:33:11Z</dc:date>
    <item>
      <title>PADR.exe do not create firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305670#M8129</link>
      <description>&lt;P&gt;I have introduce new DR Vault.&amp;nbsp; installed Vault and the DR. &lt;/P&gt;&lt;P&gt;PADR.exe should create rules in server firewall. I cannot see any rule created by PADR.exe in server firewall. when I click PADR.exe it just appear and closes the cmd.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I missing some thing here.&amp;nbsp; I believe I have to give primary Vault IP and port 1858 to PADR so that rule can be created &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Syed &lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 13:00:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305670#M8129</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-03-14T13:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: PADR.exe do not create firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305671#M8130</link>
      <description>&lt;P&gt;you give the vault details like IP and port during installation of DR module, alternatively you can  make the changes in vault.ini as well, restart the cyberark vault disaster recovery service and monitor if replication is happening, if yes you are good with the setup&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 15:33:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305671#M8130</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-03-14T15:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: PADR.exe do not create firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305672#M8131</link>
      <description>&lt;P&gt;you give the vault details like IP and port during installation of DR module, alternatively you can  make the changes in vault.ini as well, restart the cyberark vault disaster recovery service and monitor if replication is happening, if yes you are good with the setup&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 15:33:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305672#M8131</guid>
      <dc:creator>A.agarwal592645</dc:creator>
      <dc:date>2019-03-14T15:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: PADR.exe do not create firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305673#M8132</link>
      <description>&lt;P&gt;You do know that PADR.exe is not a client right?&lt;/P&gt;&lt;P&gt;You turn it on by starting the CyberArk Disaster Recovery service.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 09:27:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305673#M8132</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-03-15T09:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: PADR.exe do not create firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305674#M8133</link>
      <description>&lt;P&gt;how many you have DR Site.  each DR Server reachable with  Primary Vault Server, &lt;/P&gt;&lt;P&gt;padr is txt file. in the background  using services  Cyber-Ark Disaster Recovery service. &lt;/P&gt;&lt;P&gt;and check the padr file any update received... by replication. &lt;/P&gt;</description>
      <pubDate>Sat, 16 Mar 2019 15:43:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/padr-exe-do-not-create-firewall-rules/m-p/1305674#M8133</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-03-16T15:43:21Z</dc:date>
    </item>
  </channel>
</rss>

