Discovery: No WMI Connection

[A Westervelt]

I know this is a popular topic, but hopefully I've got a new wrench to throw in the mix.

We just acquired a new company and starting to inventory their devices on the network. I've setup a new MID server on their network and using a domain admin account to pull in their machines. However, I seem to only be pulling in the servers and very few workstations.

The usual troubleshooting of WMI commands from the MID server have shown that the IP address node keeps getting discarded for a known workstation on the network. However, if I try the hostname instead, I can authenticate and pull configuration details. Is there any settings in Discovery that can try to resolve WMI via both IP address and fallback onto hostname?

[Patrick DeCarl1]

Hi, 

Discovery is IP based and I am not aware of any back up / fall back to use host name. For the workstations, is there a local firewall rule blocking WMI queries? 

[robertgeen]

I have seen this issue before where WINS didn't exist and it couldn't reverse DNS lookup the hostname. Every time WMI tries to discover with an IP the first step is to figure out the hostname of the server. If it doesn't find it, it ends up failing. 

I saw this once in a clients public cloud where their was no reverse lookup enabled and WINS didn't exist. Unfortunately this is a WMI thing not a discovery thing I believe.

Take a look at WINRM and enabling it. It might actually get around this.

[Ann B_]

Correcting reverse lookup record in DNS solved this problem for me. 

[adilrathore]

I think your IP is pointing to a different host in the DNS. Can you find the IP as well for the given hostname using the below wmic command:

wmic /node:<hostname> nicconfig where "IPEnabled = True" get ipaddress

I guess it wont return the IP as 192.168.2.229