Credential Issue

[csatish]

Hello Community

Can anyone please guide me on below scenario based question:-

When performing the discovery of an Subnet (/24), In those around 20 Machines are getting failed & getting an  error " Active, Couldn't Classify"  do we have to perform "Test Credentials" in the credentials table, we have around 5 to 10 Windows Credentials.
Note:- High-end decom ports are already opened for these machines.

Thanks

[sanketpatil09]

"Active, Couldn’t Classify” means Discovery can reach the machine, but cannot identify what it is.
Yes, we should run Test Credentials to check if any Windows credential can log in successfully. If all credentials fail, Discovery cannot classify the device. Even if ports are open, issues like wrong credentials, no admin access, WinRM/WMI blocked, or the machine not being Windows can cause this. We should also check Discovery logs to find the exact reason.

[csatish]

Hi, Do we have to test the credentials off all 20 machines with the available credentials or only few IP are enough to test?

[SIVASANKARIS]

It’s better to test the credentials against all 20 machines instead of randomly testing a few IPs, since credentials may work on some machines and fail on others. If you have a larger number of machines, rerun the discovery schedules to verify whether the newly added credentials are successful.

Please mark my answer as helpful if it is useful

[HarshitaC]

Hello @csatish 

Please always follows these steps when you run into such scenarios.

1. Checking the discovery logs Apart from 'Active, Couldnt Classify' we will also be able to see other error messages which points to credentials if its a credential issue.

2. Checking the 'Test Credential' option from correct credentials which is configured for it.
3. You can also check if there is any existing credential affinity created for it.

If you are using any third party for credentials like cyberark there are few more things which we can check from midserver logs.