Discovery error :Authentication failure with the local MID server service credential and Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied.

[Amit39]

Hi,

While performing discovery for data centers/Labs, I am getting the below errors for that target machine.

Discovery Log Warning - 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))

Discovery Log Warning   - Authentication failure with the local MID server service credential.

Discovery Log Information Discovery completed

Discovery Log Information -   Active, couldn't classify: No WMI connection, now finished

Discovery Log Information -   Active, now Classifying

Is this related to ACL/Firewall being blocked the discovery communication between selected MID and the target machine. And due to this discovery is unable to grand access to the target machine.

Else getting error due to any port not open (443, 135), if yes, may I know the list of mandatory port need to open to perform the successful completion of   discovery.

May I know the reason behind this error and please advise me the solution method so that discovery will be able to hit this machine and gather all the respective information.

Quick help would be much appreciated.

Thank you in advance...!!

Regards,

Amit

[HugoFirst]

Hello amitpanda,

You are on the right path.   It probably is a problem with the user id used to discovery the server not being able to login, or perhaps the network is disallowing the midserver access to the target system.     I find that it's helpful to discern which it is.   So try to login to the device using the same credentials as discovery is using.   If that fails, then you should work with the people who   manage user accounts and   access in your organization.   If you can login with the discovery credentials, then it is probably a network issue.   I recommend that you first login to the midserver and then attempt to access the server.     It should become apparent if the network is blocking you.

[Amit39 · Accepted solution]

Hi Steve,

Thank you for the information.

After removing the firewalls and open those respective ports, I am getting "RPC Server not available" error after discovery. WBEMTEST also failed from source MID server to target machine -> Error saying RPC server unavailable.

Error:

Failed to access target system.   Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Regards,

Amit

[HugoFirst]

RPC Server Unavailable can result from many causes.    

I googled it for you and found a page with several tips:

Link: Troubleshooting 'RPC server is unavailable' error in WIndows

Another thought, check with your windows admin and verify that the RPC server is enabled and running on the target host.