Active, couldn't classify: No WMI connection

[anandtk]

Getting this popular error in discovery.

Usually the issues would be around any of the following, not this time.

Already verified the following.

MID server and target (Windows7) are reachable.

Target TCP 135 , 139, 445, DCOM Ports: â—¦High port range 49152 - 65535
â—¦Low port range 1025 - 5000 All are kept open.

Account has :

Local admin right,

Domain wide account,

with password as never expire,

access to execute 'WMI queries' on the target servers.

I have personally used the discovery account to login to the server and ran a simple command on the command prompt and it works well.

Wondering what could be the next step.

WBEM test???

Please share your ideas.

[VivekSattanatha]

Hi Anand,

You could try running the command from your MID Server. I always used to check the below powershell command to test WMI from MID Server. you can also try and let us know what error you are getting.

gwmi win32_operatingsystem -Computer <hostname> -Credential <Domain\username>

Regards,

Vivek

Based on the impact hit like, helpful, or Correct

[anandtk]

Vivek thanks for taking a look.

This idea did not work for me.

I got the error: 'gmi is not recognized as an internal or external command'.

[VivekSattanatha]

Hi Anand,

I believe you ran this command in powershell. Instead of gmi you can use get-wmiobject in powershell.

Regards,
Vivek

[anandtk]

Vivek,

I got many updates on the issue.

1. This time, I ran it correctly.Here is the snapshot.

2. verified that the 'snowdiscovery' is added to the SysAdmin agoup with full rights to execute WMI commands on all hosts in the domain.

3. I ran the WBEMTEST, was able to successfully connect to the target Windows server.

I think, it is 100% perfect in terms of WMI permission having been granted on the target system for 'snowdiscover' user.

Anything else strikes your thought please let me know.

Regards | Anand TK