How to test the WMI connection with wmic? |
Open a command prompt on the proxy server or the outpost and execute the command below:
wmic /node:<ipaddress> /user:<domain\username> PATH Win32_PhysicalMemory
Alternative commands to specifically check the HBA info:
wmic /user:<login> /node:<ip> /Namespace:\\root\WMI path MSFC_FCAdapterHBAAttributes
Alternative commands to be executed on the scanned/target host: wmic PATH Win32_PhysicalMemory
If these commands fail with an error starting with "0x800", use the article below Discovery: A WMI scan or wmic fails with an error starting with "0x800" If the command works on the scanned host, but fails from the proxy, the root cause is in the network (typically a firewall, local or otherwise). If the command does not return any result (it's blocked, no error message, no prompt): Root cause 1: Firewall/network issue.
Solution: open the required ports documented in the section “WMI” of this page.
Root cause 2: The password for the service account expired Root cause 3: Remote UAC is enabled. Solution: See "UAC" in this page.
FYI: This root cause also leads to the symptom described in the KA below: Discovery: A Windows host scan fails with "Credentials for localhost\userName are not valid". A Windows credential test (using a local account) fails with "Remote login via proxy denied". If the command returns this (no error code) ... ERROR:
Description = The remote procedure call failed ... the proxy debug logs of Discovery may collect more information. For example, it may log the error code 0x800706be
If the command returns "Access denied" Root cause 1: Incorrect Username/domain/password entered. Solution: Make sure you are entering the correct credentials
Root cause 2: Permission/policy issue with the account. Solution : Involve Windows admin team to check. |