Assets Discovery fails during "WMI/PowerShell-Connection" with the message "IP Address is not reachable".
However, from the same Discovery server and using the same credentials, classic WMI queries succeed:
- Get-WmiObject Win32_OperatingSystem
- Get-WmiObject Win32_BIOS
- Get-WmiObject Win32_Service
DNS resolution works and the host name is resolved correctly by Discovery.
Discovery finds a matching credential but aborts immediately during the WMI/PowerShell connection phase.
We would like to understand what exact checks are performed during the "WMI/PowerShell-Connection" stage and what condition triggers the "IP Address is not reachable" message.
I have force scan on: ~
We have 1 possible credentials for the ip 192.xx.x.xx
Start WMI/PowerShell-Connection (...)
IP Address is not reachable.
Failed to connect during to: IP Address is not reachable.
Finish WMI/PowerShell-Connection (...) result: False
