WMI Access issue

Insomaniac
Kilo Expert

Hi Experts,

I am trying to discover some of the windows machine with the local credentials provided by the team. when i am trying to do the RDP from the mid server i am able to login to the device while i am trying to do the same through the discovery it is giving me an error as 

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))

Could some one guide where i can look to resolve the problem.

 

4 REPLIES 4

robertgeen
Tera Guru

This is one of the most generic RPC error messages you can get unfortunate. I would start by confirming that they have mapped your credential to the local admin group on the server. Can you check with that first? I would also make sure there isn't a local firewall that is stopping WMI calls from accessing the server. Those are the 2 most common reasons for that error code.

DaveHertel
Kilo Sage
Kilo Sage

As Robert said, this is a very common generic error for access to target devices to be discovered.  I recommend adding debugging info for credentials Credentials Troubleshooting doc here (London)

This will add info to the INPUT portion of classification probe that helps deduce what is going on including:

  • Cred types attempted
  • IP addresses of the machine(s) that were targeted
  • Success/failure response of each cred attempted

 

Does this help? Hope so...

chuckm
Giga Guru

The error message 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)) can be caused by 2 primary issues.  I will discuss the first 2 troubleshooting steps I always work through before attempting further troubleshooting steps.

Step 1 (Validate Credential using RDP):
RDP from the MID server to the Remote Windows device to validate the Windows credential as you have done.  This is excellent way to validate the credential.  BUT this step only validates the credential - because RDP communicates on port 3389 to login to the Remote Windows device while ServiceNow Discovery uses a different range of ports for login and discovery communication.

find_real_file.png

Step 2 (Validate WMI port 135 and port ranges 49152 - 65535 are open):
Validate the ServiceNow Discovery WMI ports between the MID Server and the Remote Windows device are open in the Firewall.  ServiceNow Discovery uses WMI for discovery, therefore port 135 from the MID Server to the Remote Windows device must be open for initial communication AND high ports 49152 - 65535 must be open for the remainder of the communication.  Even though this is a large range of open ports, only a portion of this range are dynamically allocated.

find_real_file.png

If you are in a lab environment, a quick way to validate step 2 is to turn off the Remote Windows or SEP firewall and initiate discovery.  In a production environment, I review the firewall logs looking for blocks.

A slightly more helpful error message might look like:  Failed to access target system. Please check credentials (Step 1: Validate Credential using RDP from the MID Server) and firewall settings (Step 2:  Validate WMI port 135 and high ports 49152 - 65535 are open) on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).

 

Hi Chuckm,

We are facing issues with WMI in some servers that reside in protected zones. Port 135 is part of our Firewall rule request, however higher random ports are being blocked by the appliance. They have mentioned that one way to allow this is by implementing UUID filtering. However, I am not sure which UUID should we request for Windows discovery.

I found this link from Juniper: https://kb.juniper.net/InfoCenter/index?page=content&id=KB12057, and I'm thinking that MS-RPC-EPM UUID is the one.

Also, and according to your diagram, this ports should be enabled with the MID server as the destination and the discoverable server as the source?

Have you faced this issue before? Obviously firewall team does not want to allow all the dynamic ports range, since it represents an important vulnerability.

Thanks!

Miguel.