Discovery authentication issues

[Fabio Borges]

Hi, I need some help, I don't know if I'm posting in the right category.

We have a few Discovery Schedules to scan some networks and feed the data into CMDB, but we noticed that during the Schedule several machines have authentication problems, but if we run Quick Discovery on the same IPs that presented problems, Discovery works fine, during the schedule around 60 to 70% of the machines present this scenario, the rest are discovered normally

I searched the forum and knowledge bases and found similar cases, but the solutions in these cases did not apply to my problem, we are using only SSH and Windows credentials (not using SNMP), we obtain the credentials through Cyberark, and in the Cyberark logs it is shown that the password was obtained successfully

We saw a KB informing about instance cloning problems that could generate this failure, but we followed the KB's instructions and had no solution, we changed the schedule hour of execution, created a new schedule, we divided the number of vlans between the two schedules (the number was not large, now there are 5 vlans /24 in each schedule), we are not using clusters for the discoverys, it is just one MID per schedule, but the problem persists.

Could you help us?

[Selva Arun]

Hi,

Could you please check whether the Windows credentials used for scanning Windows machines are locked out? The same goes for the Linux credentials. If an account is locked out, the discovery scan will fail because the MID Server will not be able to connect to the target device.

Regards,
Selva

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

[Fabio Borges]

Hi Selva thanks for the reply

Yes, we have already checked that the credentials are not blocked.

[pratik0306]

1. Try to run a separate schedule for the IP/range that you are facing issues with.

2. Try to use behavior discovery and see if that helps

[Fabio Borges]

Hi, thanks for the reply

We already tried create a separate schedule for the ranges that are facing the issue, but without success, I go study if behavior can helps us in this situation, 90% of the machines are the same OS, and we only have Windows (less common) and Linux (more common) on those ranges, none other technology