Getting below error when trying to run a Discovery Scan on a Priv Cloud shared services deployment.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Getting below error when trying to run a Discovery Scan on a Priv Cloud shared services deployment.

L2 Linker

We have CyberArk ISPSS, and configured a Discovery Scan to automatically discover accounts within our Active Directory's specific OU/Group. But when executing the scan, we get bellow error. If anyone has come across this error, could you please share your experience or how it was resolved?

"errorMessage": "DSENG621E Failed to connect to the Active Directory. Ensure the full flow in the Connector Management is correct: domain identifier in the connector pool, connectors assigned to the pool, open ports, other connector configuration issues. AD error: The server is not operational.

 

9 REPLIES 9

L7 Applicator

Hi @Ajit Sutreja​ 

 

Please login to the Connector server and run the following commands

 

 

Test-NetConnection -ComputerName <AD-Domain-Controller> -Port 636

 

nltest /dsgetdc:<DCName>

 

If the above tests fails the connector cannot find a DC.

 

If the connection fails,

 

Please check that the Connector server can reach the DC.Open required firewall rules for LDAP, LDAPS, or Global Catalog and if your AD is behind a Load Balancer, check if the LB allows LDAP connections.

 

Please also check that the account used by the Connector must have Read permissions on the AD OU.

 

Then try to manually running an LDAP query from the Connector server using PowerShell command and troubleshoot accordingly.

 

Get-ADUser -Filter * -SearchBase "OU=Users,DC=domain,DC=com"

 

 

Hope it helps !

 

 

 

L2 Linker

Hello Malhar, thanks for these steps. Above two commands are successful and I am able to run below command via Powershell on the connector server and get list of users.

Get-ADUser -Filter * -SearchBase "OU=Users,DC=domain,DC=com"

But Discovery Scan is still failing with the same error code DSENG621E..

L4 Transporter

Hello @Ajit Sutreja​ 

 

Have you received an answer to your question? If so, we kindly encourage you to share it with us.

Your insights could be valuable to other community members in the future.

 

Thank you, Isar.

L4 Transporter

Hi @Ajit Sutreja​ 

 

If this is still an issue, please see below suggestions

 

- Does account's password you are using for the scan contain any back slashes (\) or forward slashes (/)?

- Review: https://community.cyberark.com/s/article/Discovery-Scan-Some-Domain-Scan-failed-with-DSENG014E-AND-DSENG276E

 

Hope this helps

 

Thanks

 

Michael

L2 Linker

Hi Michael, no we haven't resolved this. Our account's password doesn't have any back slashes (\) or forward slashes (/). And powershell script execution setting is set to 'unrestricted' on the connector server as per below screenshot. Field_Content_versions_oct20__068Vy00000VKlLwIAL.png

L0 Member

Hi @Ajit Sutreja​ you managed to fix the error?

L4 Transporter

Hi @Ajit Sutreja​  Please make sure your scan accounts is having following permissions.

 

  • Read permissions in the OU to scan and all sub-OUs
  • Read permissions on the Active Directory

 

If the domain admin account failed with same error, make sure the domain admin account is NOT in the protected users group.

 

You also need to make sure scan account is not expired / disabled/ set to change password at first login

L4 Transporter

Hi @Ajit Sutreja​  Please make sure your scan accounts is having following permissions.

 

  • Read permissions in the OU to scan and all sub-OUs
  • Read permissions on the Active Directory

 

If the domain admin account failed with same error, make sure the domain admin account is NOT in the protected users group.

 

You also need to make sure scan account is not expired / disabled/ set to change password at first login

L2 Linker

We were able to resolve the issue after enabling/configuring LDAPS as the Priv Cloud cannot use LDAP (non-secure) protocol for discovery scans. So you must have appropriate SSL cert in place either in all of your Domain Controllers or your LDAPS load balancer.

  • 504 Views
  • 9 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!