In order for windows based auto-discovery tool to collect information from windows servers it needs to connect to remote machines using WMI/WinRM.
We have an older article that helps with some of the error messages: https://device42.zendesk.com/entries/27009367-D42AutoDisc-Client-Windows-or-Hyper-V-auto-discovery-error-messages
If that doesn't help and you still have problems connecting, please use the following steps to troubleshoot:
The WMI Diagnosis Utility
This is a utility to help system administrators diagnose and repair problems with the WMI service. Please run this to see if you can connect to the remote computer.
Link: https://www.microsoft.com/en-us/download/details.aspx?id=7684
How to article for this: http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx
Quick step to enable winrm
Run following on the remote machine:
```winrm quickconfig```
Some steps for firewalls
```netsh advfirewall set service RemoteAdmin enable```
or
```
netsh firewall set service RemoteAdmin enable
```
Advanced firewall commands
```netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
netsh advfirewall firewall add rule dir=in name ="WMI" program=%systemroot%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=any
netsh advfirewall firewall add rule dir=in name ="UnsecApp" program=%systemroot%\system32\wbem\unsecapp.exe action=allow
netsh advfirewall firewall add rule dir=out name ="WMI_OUT" program=%systemroot%\system32\svchost.exe service=winmgmt action=allow protocol=TCP localport=any```
Windows auto-discovery
For .net auto-discovery tool to work, the WMI diagnostic utility must be able to connect to the remote machine. If you are able to connect via that utility and still having issues with auto-discovery tool, please contact us at support at device42.com