<?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 Updating New DCs for LDAP authentication in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309316#M11163</link>
    <description>&lt;P&gt;Good morning everyone. I have a quick question. We are planning to replace all three Domain Controllers (DCs) in our self-hosted CyberArk environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've already updated the primary and disaster recovery (DR) vaults with the new DCs in the host file . Additionally, I've defined them in the vault server's firewall inbound and outbound rules. However, I keep encountering the following error whenever I attempt to save the new DCs in the LDAP host directory via Pvwa&lt;/P&gt;&lt;P&gt;I'm wondering if there are any other places where I need to update the new DCs, or if I need to import the certificates of all three DCs into the Vault servers. Any insights would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Your changes were not saved. The following error occurred:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Directory:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Successfully connected to directory, but with errors (0)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P02.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Failed to connect to host, Reason: Failed to perform customized function ProcessLevelPreConnect. Code(13, -1) (13)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P03.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Successfully connected (0)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P05.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Failed to connect to host, Reason: Failed to connect to LDAP host " wrytgh-sfergDC-P02.heyeui.com&lt;/P&gt;&lt;P&gt;" with user "CN=cyberark_ldap,OU=LDAP,OU=Accounts,DC=efffef,DC=com". Code(21, 81) (21)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Summary:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LDAP verify check ended with errors (-1)&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;Failed to connect to host, Reason: Failed to connect to LDAP host "wrytgh-sfergDC-P03.heyeui.com" with user "CN=cyberark_ldap,OU=LDAP,OU=Accounts,DC=auau,DC=COM". Code(21, 81) (21)&lt;/P&gt;</description>
    <pubDate>Sat, 06 Apr 2024 14:38:13 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-04-06T14:38:13Z</dc:date>
    <item>
      <title>Updating New DCs for LDAP authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309316#M11163</link>
      <description>&lt;P&gt;Good morning everyone. I have a quick question. We are planning to replace all three Domain Controllers (DCs) in our self-hosted CyberArk environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've already updated the primary and disaster recovery (DR) vaults with the new DCs in the host file . Additionally, I've defined them in the vault server's firewall inbound and outbound rules. However, I keep encountering the following error whenever I attempt to save the new DCs in the LDAP host directory via Pvwa&lt;/P&gt;&lt;P&gt;I'm wondering if there are any other places where I need to update the new DCs, or if I need to import the certificates of all three DCs into the Vault servers. Any insights would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Your changes were not saved. The following error occurred:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Directory:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Successfully connected to directory, but with errors (0)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P02.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Failed to connect to host, Reason: Failed to perform customized function ProcessLevelPreConnect. Code(13, -1) (13)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P03.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Successfully connected (0)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Host:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;wrytgh-sfergDC-P05.heyeui.com&lt;/P&gt;&lt;P&gt;&lt;B&gt;Status:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Failed to connect to host, Reason: Failed to connect to LDAP host " wrytgh-sfergDC-P02.heyeui.com&lt;/P&gt;&lt;P&gt;" with user "CN=cyberark_ldap,OU=LDAP,OU=Accounts,DC=efffef,DC=com". Code(21, 81) (21)&lt;/P&gt;&lt;P&gt;&lt;B&gt;Summary:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LDAP verify check ended with errors (-1)&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;Failed to connect to host, Reason: Failed to connect to LDAP host "wrytgh-sfergDC-P03.heyeui.com" with user "CN=cyberark_ldap,OU=LDAP,OU=Accounts,DC=auau,DC=COM". Code(21, 81) (21)&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2024 14:38:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309316#M11163</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-04-06T14:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: Updating New DCs for LDAP authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309317#M11164</link>
      <description>&lt;P&gt;This kb article says it is a dns resolution issue, so double check the vault can look them up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/Adding-New-Host-Failed-to-connect-to-host-Reason-Failed-to-perform-customized-function-ProcessLevelPreConnect-Code-13-1-13&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can the pvwas see the dns entries too? I'm not sure if they validate it as well but have seen some use cases where the pvwa does domain resolution etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't think certificates matter, as long as they are signed by the same root you've imported into the vault. &lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2024 16:57:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309317#M11164</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2024-04-06T16:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: Updating New DCs for LDAP authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309318#M11165</link>
      <description>&lt;P&gt;The last host looks like it has a cert problem though, see https://community.cyberark.com/s/article/troubleshoot-new-LDAP-directory-connection&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2024 17:03:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309318#M11165</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2024-04-06T17:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Updating New DCs for LDAP authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309319#M11166</link>
      <description>&lt;P&gt;Hi @Law David?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please check the LDP.exe to troubleshoot the connectivity issue for LDAP. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps to find the cause. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/00004795" href="https://community.cyberark.com/s/article/00004795" target="_blank"&gt;https://community.cyberark.com/s/article/00004795&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Apr 2024 00:33:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309319#M11166</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-04-07T00:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: Updating New DCs for LDAP authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309320#M11167</link>
      <description>&lt;P&gt;I think I have done all that is on this article, accept that the DCs are not define in PVWA host file, our current DCs are not defined in PVWA server host file as well and they are successfully connected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am just wondering what the root cause could be. &lt;/P&gt;</description>
      <pubDate>Sun, 07 Apr 2024 01:30:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/updating-new-dcs-for-ldap-authentication/m-p/1309320#M11167</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-04-07T01:30:50Z</dc:date>
    </item>
  </channel>
</rss>

