Where can you check that the LDAP binding is using TCP/636?
Where can you check that the LDAP binding is using TCP/636?
To check if the LDAP binding is using TCP/636, you would look in the PVWA (Privileged Vault Web Access), under 'LDAP Integration', then 'LDAP', then 'Directories', and then 'Hosts.' This process aligns with how configurations and bindings are typically verified in systems using LDAP integrations. The other options either reference incorrect steps or tools that do not pertain to checking the LDAP binding specifically on TCP/636.
B is Correct. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Configuring-the-Vault-to-Recognize-Multiple-External-Directories.htm?tocpath=Administrator%7CUser%20Management%7CTransparent%20user%20management%20using%20LDAP%7C_____9
The answer is D. https://cyberark-customers.force.com/s/article/Privilege-Cloud-How-to-Troubleshoot-Connection-Issues-Between-Connector-Server-Domain-Controller-and-PVWA-LDAP
Answer is B
From the Connector server, Run the Test-NetConnection command using PowerShell as Admin. You’ll do this on your Connector server and try to reach an active domain controller via port 636. This tests to make sure the Connector server is communicating with the DC. If not, there is a communication issue the customer needs to solve on their end. Type “tnc <DomainController IP> - port 636” If you get a failure: Check to see if the LDAP SSL is enabled on the domain that you are attempting to reach. Make sure the DC can communicate over port 636 and that no Firewall or Security software is blocking communication Check for routing issues https://cyberark.my.site.com/s/article/Privilege-Cloud-How-to-Troubleshoot-Connection-Issues-Between-Connector-Server-Domain-Controller-and-PVWA-LDAP
Answer is B Reference: https://docs.cyberark.com/pam-self-hosted/Latest/en/Content/PASREF/LDAP%20Integration%20-%20Introduction.htm#Hosts
Answer should be B.
B is correct