Windows Server Discovery ending with Active couldn't classify:No WMI connection

Suvetha S
Tera Contributor

‎05-17-2024 05:53 AM

Hi,

We are facing Active couldn't classify: No WMI connection for few of the Windows server during Discovery. Credential test is getting failed from ServiceNow end even though we are able to RDP the server using the same user name and password added. Adding a local admin to the servers/re-configuring Domain credentials didn't work either. Ports are opened and there is no firewall rule blocking the MID servers. Please share your inputs. 

0 Helpfuls
  • 213 Views
1 REPLY 1

Marshall Parker
Tera Guru

‎05-17-2024 10:20 AM

I would suggest looking at the discovery logs in ecc_queue table. The XML on the Shazzam classification input should give you a map of what ports were communicated with for each IP address. That may help with determining where to troubleshoot.

 

Example - ecc_queue for the Shazzam topic on the input side .. for the IP address in question, was WMI (Port 135) open, refused or another result?

<scanner name="GenericTCP" port="135" portprobe="wmi" protocol="tcp" result="refused" service="epmap"/>

vs

<scanner name="GenericTCP" port="135" portprobe="wmi" protocol="tcp" result="open" service="epmap"/>

 

0 Helpfuls