WMI access denied in System Logs but Device > User Identification shows connected on all DC's

cancel
Showing results for 
Search instead for 
Did you mean: 

WMI access denied in System Logs but Device > User Identification shows connected on all DC's

L2 Linker

Hello,

 

I've seen on my Palo Alto 3220 system logs dashboard applet a ton of Access Denied messages regarding our domain controllers.  However if I go over to Device > User Identification, all 4 of our DC's there are listed as connected in green.  All 4 are Microsoft Active Directory, WinRM-HTTP.  If they are green and connected there, why am I seeing errors in the system logs?

 

01/26 14:29:58 Server monitor dcname(vsys1) is connected

01/26 14:29:58 Server monitor dcname(vsys1): connection failed, HTTP code 500, s:Receiverw:InternalErrorThe WS-Management service cannot process the request. The WMI service returned an 'access denied' error. 200The WS-Management service cannot process the request. The WMI service returned an 'access denied' error. H

2 REPLIES 2

L2 Linker

show user ip-user-mapping all showed valid user to IP mappings.

show user server-monitor statistics showed 4 DC's in the connected state, but if you kept running that command over and over you'd see a random DC go to not connected, then access denied, then connected again.  The windows program WBEMTEST with the same service account credentials we use against the DC's launched with no issue.

 

We changed them from WinRM-HTTP to WMI and committed, and no issues since.

 

There's no problem with it on WMI, that's ok to have it set to that method if it works right?

Maybe check the article below and also you may double check the DC config itself as only WBEMTEST may not be enough, also check for network flapping or bottleneck issues or firewall CPU/Memory issues as the integrated WMI agent is causing cpu/memory issues to the firewall. Also the trust between the 4 DC could be in some cases not configured correctly.

 

Agentless User-ID 'access denied' Error in Server Monitor - Knowledge Base - Palo Alto Networks

 

 

Also check for known issues for your firewall version or addresses issues for the versions after your version. Example:

 

Known Issues (paloaltonetworks.com)

 

PAN-OS 9.1 Addressed Issues (paloaltonetworks.com)

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!