- My View
Troubleshooting discovery on a specific Windows server. The server is in the same domain as other servers which are discoverable. The discovery account is verified to work on other systems and also works on the problem server to:
But, it does not work for discovery against this particular host. The discovery log warning is: Failed to access target system. Please check credentials and firewall settings on the target
system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
In the ECC input, I can see all of the Windows credentials tried and failed.
What else is required for Windows discovery?
This looks like permission issue. Check following thread if that helps:
0x80070005 – E_ACCESS_DENIED
Access denied by DCOM security.
|The user does not have remote access to the computer through DCOM. Typically, DCOM errors occur when connecting to a remote computer with a different operating system version.||Give the user Remote Launch and Remote Activation permissions in dcomcnfg. Right-click My Computer-> Properties Under COM Security, click "Edit Limits" for both sections. Give the user you want remote access, remote launch, and remote activation. Then go to DCOM Config, find "Windows Management Instrumentation", and give the user you want Remote Launch and Remote Activation. For more information, see Connecting Between Different Operating Systems|
If I am able to run WMI and PS queries remotely, does that not already verify that the account has DCOM access?
Are you testing WMI and PS queries from MID server box to the target server and return success? If that's correct, enable additional logging as what Pavel suggested to find more hints.
Beside, test the credentials (use the Test Credential link) to the target server and check if it return verified. This can help to rule out credentials issue.
Try to set up mid.cim.debug parameter to "true" for a pertinent MID server to see more details about the possible issues.
Maybe additional logging information will give you some insights.
MID server needs to be restarted to apply changes.
Hi Sean, have you tried to run discovery on this server and confirm that it doesn't work? The reason I ask is that there was a defect in older releases where the credential test would fail but you could still successfully discover the device.