- 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
‎11-24-2020 07:19 PM
Hi Hitoshi,
We are receiving the below error,
Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service.
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2020 07:24 PM
Error 403 implies credential error. It's not able to login with the provided user/password.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2020 07:40 PM
Check if MID server is running with domain credentials so it'll be able to access computers in the domain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2022 10:33 PM
Hi,
the mid server is not having the Powershell folder. What to do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-25-2020 09:19 AM
Did you also check that the high ports 49152 - 65535 are open to this server as well? When discovering using WMI, port 135 from the MID Server to the Remote Windows host must be open for initial communication AND high ports 49152 - 65535 must be open for the remainder of the communication. It is possible the high ports are being blocked.
And as Ashutosh Munot mentioned - check the firewall rules on the remote Windows host. If the Windows host has the Windows Firewall with Advanced Security turned on, you can check the firewall logs (C:\Windows\System32\LogFiles\Firewall) to determine if any of the WMI ports are being blocked. When the Inbound rule Windows Management Instrumentation (WMI-In) for WMI is enabled, you can see in the logs that the high ports (src-port and dst-port) are allowed (action=ALLOW).