Active, couldn't classify: No WMI connec

[RajK01619170647]

wmi test connection are giving the positive result from Mid server to target server.  though while doing the quick discovery getting "Active, couldn't classify: No WMI connec" error.

[pavani_paluri]

Hi @RajK01619170647 ,

If the WMI Test Connection from the MID Server to the target server is successful but Quick Discovery still fails with "Active, couldn't classify: No WMI connec", it usually indicates that basic WMI connectivity is working, but Discovery is unable to retrieve the information required for classification.

This can happen when:

• The Discovery account can authenticate successfully, but does not have sufficient permissions to query the required WMI classes.
• DCOM/RPC communication is partially blocked, allowing the connection test to pass while actual WMI queries used by Discovery fail.
• The target server has WMI repository or namespace issues.
• Discovery is using a different credential or MID Server than the one used for the WMI test.
• Required WMI classes such as Win32_OperatingSystem or Win32_ComputerSystem are not accessible.

The most useful next step is to review the Discovery Status logs and ECC Queue records. Although the error message says "No WMI connection," the detailed logs often reveal the actual cause, such as Access Denied, RPC Server Unavailable, Invalid Namespace, or a failed WMI query.

Since the connectivity test is already successful, the focus should be less on network reachability and more on validating:

1. The credential being used during Discovery.
2. WMI permissions on the target server.
3. RPC/DCOM configuration.
4. Discovery logs and ECC Queue output for the specific failure during classification.

A successful WMI Test Connection confirms that the MID Server can reach and authenticate to the target server, but a classification failure generally points to an issue with WMI query execution rather than connectivity itself.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[Tanushree Maiti]

Hi @RajK01619170647 

Refer: Port Scanning Issue - Active, couldn't classify: No WMI connection 

KB2687718 Validating Windows Credentials from the MID Server Using WMI 

[Ehab Pilloor]

Hi @RajK01619170647,

Log in to the server where the MID Server is installed.

Open a PowerShell command prompt.

Run the following command:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential LOCALDOMAIN\mid

Replace LOCALDOMAIN\mid with the Windows credential being tested.

Replace 192.168.200.14 with the target IP address that is failing Discovery.

Expected Result

If the command is successful, output similar to the following will be returned:

SystemDirectory C:\Windows\system32

Organization

BuildNumber 6001

RegisteredUser Windows User

SerialNumber 12345 OEM 1234567 12345

Version 6.0.6001

This confirms that the credential has sufficient permissions and that basic WMI connectivity from the MID Server to the target is working.

Failure Result

If the command fails, the credential is either incorrect or lacks the required permissions on the target system. In this case, the Windows administration team should investigate credential validity, permissions, firewall rules, and WMI configuration. Discovery and orchestration will not function until this basic connectivity issue is resolved.

Please Accept this response as Solution if it assisted you with your question & Mark this response as Helpful.

Kind Regards,

Ehab Pilloor