Issues with Windows server discovery "Active, couldn't classify: No WMI connec"

[ahmadadnan]

Hi,

I am facing issue while discovering windows server.

I am running discovery on a subnet in which few windows servers has been discovered but for few I am getting below errors.

When I checked in devices tab of Discovery status, I am getting error in completed activity "Active, couldn't classify: No WMI connec" and in the discovery log it is giving me message as "The result file \\10.12.70.20\admin$\temp\psscript_output_4778de1d-ec89-44cf-9745-ebcd9fa31706.txt can't be fetched because it doesn't exist". But in the server this file has been created, I have checked this.

Can anyone please suggest me how to troubleshoot this because few Servers has been discovered of the same subnet.

I have validated the credentials, and it is working fine.

Please find the ECC queue input message:

Regards,

Adnan

[Fares1 · Accepted solution]

Hey there,

Have you considered this article?

Consider opening the 445 port because it's the port used for Windows's Network File Sharing Protocol. (SMB)

[ahmadadnan]

Hi Fares,

I have checked that this file has been created in the target host. Please suggest what else I need to check.

Regards,

Adnan

[Fares1]

Is your 445 port open? It's necessary for the network file sharing protocol described above. 

[ahmadadnan]

I can do telnet on port 445 on both the servers that were discovered and also to those servers for which I am facing issue.

Please suggest what next I need to check.