- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2020 07:27 PM
Hi,
I am getting below error message please help me resolve it and understand the root cause of the issue,
Active, couldn't classify: No WMI connection
Thanks in advance.
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2020 12:35 AM
HI,
We always try gwmi connection first when the discovery is initiated. SO couple of the things to check:
1) 135 port
2) then logon to mid server and go to powerShell executor and run
gwmi win32_operatingsystem -computer <IP address of server to gather info> -credential '<credentials>'
3) If this is successful then check firewall rules on that target machine.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-19-2021 09:20 AM
Hi,
We have a similar issue and have performed all the checks (including a wireshark trace) which revealed that there are no firewall or credential issues. The return port used by the target server is 5068 which reaches the mid server, however results in a failed logon attempt. This affects a large portion of the estate as it occurs across one sub-domain.
Any advice would be appreciated as to the best way to fix.