Using Active Directory Discovery - A customer is unable to sync with AD for User or Device Discovery.

Snow Inventory Server 6.x

Firstly - check the snowserver.logs within C:\ProgramData\SnowSoftware\Inventory for any guidance as to where the issue may lie.

Please note: From Snow Inventory Server 6.6.3 there is now the facility for more advanced logging with regards to Active Directory Discovery.

If on a lower version (than 6.6.3 )or you are unable to identify an issue with the logs:

• Please investigate the table inv.DiscoveryUserActiveDirectoryEmail.  This is the table where the raw data is stored.
• If there is data present in inv.DiscoveryUserActiveDirectoryEmail then look at the tblUserInfo table. This may give some more insight into the issue for example some users may be appearing whereas some are not. If this is the case perhaps a firewall rule or restriction was put in place after a period of time. Checking the UpdateBy & UpdatedDate columns may help you identify some trends or when the issue occurred. For example you may see that users have been updated ok by using the License Manager Import Tool.

• Start by installing the Portqry utility - (https://www.microsoft.com/en-us/download/details.aspx?id=17148) on the Snow Inventory Server
• Please take note of your install location. (i.e. C:\PortQryV2)
• Next - open a command prompt (as administrator)
• Type cd <location of install? (ie. cd C:\PortQryV2)
• Hit Enter
• Run the following command - portqry.exe -n snowsoftware.com -p udp -e 161 -cn !public! (Where you see snowsofware.com enter the Active Directory Domain you are trying to access). Similar to the below:

• Running the port query utility on Port 161 it has returned FILTERED.
  • Usually "Filtered" means the packet is dropped (no reply whatsoever) to the Active Directory Domain or that traffic is blocked.

Please note: It may still be possible to still have successful communication using a utility like Powershell (i.e. GET-ADUser).  However this uses UDP port 389 or 636.  Again using the port query utility we are able to verify that port 389 is open. It should return the Schema settings, similar to below:

Snow currently only supports SNMPV1 for Network Discovery which uses port 161.

Please note: Each environment varies - in some cases there may be a dynamic IP address assigned to their Active Directory Domain Controller. Please check they are not using an IP address but instead are using a hostname when defining their LDAP path in Snow Management and Configuration Center (SMACC):

Using a utility like telnet will only tell us if the TCP port is open.  It will not confirm whether UDP is open.  For this reason we need to use something like the Port Utility to verify the communication.

Ensure that UDP port 161 is open for communication on your AD server.
Once opened please repeat the process of running the query above.
If successful it should look similar to the query result of port 389 above.
Please then configure your network discovery module in SMACC using the hostname as opposed to using the IP Address.

UDP Port 161 was closed between Inventory Server & Active Directory.