I am having Pan-OS integarted user Id

cancel
Showing results for 
Search instead for 
Did you mean: 

I am having Pan-OS integarted user Id

L1 Bithead

For some reason the Agent stopped working on the end user computer. when i checked the event log i came with an error for the id 10036 ( The server-side authentication level policy does not allow the user domain\user SID (X-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXX-XXXXX) from address xxx.xxx.xxx.xxx to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application ).

 

Can i know how to resolve this issue

16 REPLIES 16

@echahine ,

 

The Problem we are having  is on the user computers,

If you go to Event viewer --> Windows Logs --> System and look for events related to 10036

We are having the authentication error 10036 when using WMI, and we can't solve it. What we're trying to do now is to switch to WinRM-HTTP, its not even connecting to the AD server in the first place.

In order to use WinRM-HTTP, you need to make sure your PA service account in AD has been added to the "Remote Management Users" group. You also have to configure a Kerberos Server Profile on the device tab in the PA. Just create a new Kerberos profile, and add the FQDN of all of your domain controllers to it. Once that is done, you have to apply that Kerberos Server Profile by clicking the 'gear' icon in the Palo Alto Networks User-ID Agent Setup area under Device > User Identification. (select it using the drop-down) Once you commit those changes, your DCs under Server Monitoring should show "Connected" instead of "Connection Refused". 

Hey I have the same error, I made the solution that palo alto sends but have no luck, i get that error, could you manage to resolve the issue???

L0 Member

Hey, to the people having issues with Kerberos.
Step 6 indicates RC4 is not a supported cipher.  Have you confirmed your Windows Server is no longer defaulting to RC4?
If someone could test and update the thread that would help the rest.
- Configure Server Monitoring Using WinRM 
- Windows Configurations for Kerberos Supported Encryption Type | Microsoft Docs 

Hello, we are facing the same errors and would change from WMI to WinRM-http. Do you know if is there any disruption in the user ip mapping on the firewall while doing the change? We are monitoring 4 domain controllers, eventually I can change the configuration one by one.

In our case we simply switched to Windows User-ID Agent, which is more reliable and consistent.

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!