Error in Discovery.

[SatishChitti]

Hello Everyone,
Good day!

Can anyone tell me what is the process to troubleshoot if I my discovery was failing & getting error "Active, Couldn't Classify".

I was trying to discover "windows" & "Linux" device's. Below are the steps which I did to troubleshoot this error.

1.) Login into Mid host used "Telnet" command to check 135(WMI) and High Ranges i.e. 49152 to 65535 to check if this ports are opened.

2.) Checked Credentials for both Linux & Windows, used "Test Credential" functionality to test the credentials.

Note:- These devices are not discovered earlier, so there was no "Affinity" generated.

Can anyone tell me if my troubleshooting steps are correct? If not, Can anyone guide me what would be the next steps to troubleshoot Linux Device as well.

Thanks

[Harish Bainsla]

Hi @SatishChitti  

 Port Checks via Telnet
Checked port 135 (WMI) for Windows.
Checked high ephemeral ports 49152–65535 (used by WMI).
For Linux, you should also check port 22 (SSH).

Credential Testing

Used Test Credential to validate Windows and Linux credentials.

Affinity

Noted that these are new devices, so no prior affinity exists — that’s expected.

Now Steps to Troubleshoot "Couldn't Classify

1. Check MID Server Logs

Go to the MID Server used for the Discovery.
Review the agent.log and wrapper.log around the time of the Discovery.
Look for:
Authentication failures
Timeouts
Network errors

2. Run a Discovery and check logs

3. Validate MID Server Capabilities

Ensure the MID Server has the correct capabilities:

WMI for Windows
SSH for Linux

Also check that the MID Server is validated and up.

5.

Check IP Address Reachability

From the MID Server, try:

ping <target IP>
telnet <target IP> 22 (Linux)
telnet <target IP> 135 (Windows)

6. Check Firewall 

Some devices may have host-based firewalls or security agents that block WMI or SSH.
Coordinate with the network/security team to confirm.

if my answer helps you mark helpful and accept solution