Network Sonar Discovery using Active Directory - Unable to discover nodes

Good day! I'm using Network Sonar discovery - Active Directory, the account i'm using is a domain admin and can view the AD OU's but i'm having issue discovering nodes. Anyone who has the same experience? Thanks in advance.

Find more posts tagged with

orion

discovery_scans

npm

Accepted answers

All comments

christopher.t.jones123

@sidry, do you have a WMI credential defined to use for the discovery? when doing AD discoveries there would be two locations to put credentials. !. to scan the OU and 2. the one that is actually tested against the node for discovery

shuth

A couple of other things to check:

Can the SolarWinds server reach those servers in the OU? SolarWinds may be able to communicate with the Active Directory server but if the servers in those OUs are in a different part of the network behind firewalls, etc. then the discovery won't see them
Has someone accidentally added the servers to the Network Discovery Ignore List? I've seen that before where a user added their whole network to the ignore list - during discovery it would show as finding X nodes but when discovery ended it would show no nodes found (as they were ignored).
What @christopher.t.jones123 said - ensure you have provided suitable WMI credentials. If you have ticked the option to only include nodes that respond to SNMP/WMI (i.e. ignore ICMP only nodes), if the credentials don't work on those servers they won't show in the list. I usually enable the "show ICMP only nodes" option so I can see if they at least respond to ping.