- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
04-06-2024 07:38 AM
Good morning everyone. I have a quick question. We are planning to replace all three Domain Controllers (DCs) in our self-hosted CyberArk environment.
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
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.
Your changes were not saved. The following error occurred:
Directory:
Status:
Successfully connected to directory, but with errors (0)
Host:
wrytgh-sfergDC-P02.heyeui.com
Status:
Failed to connect to host, Reason: Failed to perform customized function ProcessLevelPreConnect. Code(13, -1) (13)
Host:
wrytgh-sfergDC-P03.heyeui.com
Status:
Successfully connected (0)
Host:
wrytgh-sfergDC-P05.heyeui.com
Status:
Failed to connect to host, Reason: Failed to connect to LDAP host " wrytgh-sfergDC-P02.heyeui.com
" with user "CN=cyberark_ldap,OU=LDAP,OU=Accounts,DC=efffef,DC=com". Code(21, 81) (21)
Summary:
LDAP verify check ended with errors (-1)
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)
04-06-2024 09:57 AM
This kb article says it is a dns resolution issue, so double check the vault can look them up.
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
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.
I don't think certificates matter, as long as they are signed by the same root you've imported into the vault.
04-06-2024 05:33 PM
Hi @Law David?
Please check the LDP.exe to troubleshoot the connectivity issue for LDAP.
Hope it helps to find the cause.
04-06-2024 06:30 PM
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.
I am just wondering what the root cause could be.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

