I am having Pan-OS integarted user Id

[PavanT]

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

[BPry]

@PavanT,

A couple months back Microsoft pushed out an update that did some DCOM hardening that you are running into (KB5004442). I'm guessing you or your server team finally got around to patching your servers and enabled the registry key. My guess is that you are using an outdated version of PAN-OS or the User-ID agent, because I don't recall having to do anything about this particular patch and I can't find the advisory that was sent out about it. 

[PavanT]

@BPry 

Thanks for your response. Can I know which version of PAN OS are affected?

[DarrinH]

We are experiencing the same problem.  Just installed Microsoft Patch Tuesday updates on our Domain Controllers.  Now getting the Windows Event ID 10036.  "The server-side authentication level policy does not allow the user DOMAIN\userid SID () from address <> to activate DCOM server.  Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application."   Anyone else out there getting these errors or have a solution?  Our Paloalto PA-3050 is current on all updates, running version 9.1.11 of the software.

[Ben-Price]

Hi All,

Yes, I have a client that has just patched their Windows 2016 servers and is now receiving the same error. Client is running PAN OS 9.1.11-h2 and User-ID agent 9.1.11-h2 on PA-3020 (latest available for this model device).

Tried the below Reg key to no avail:

https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-...

And this to no avail:

Component services > computers > My computer > properties > set default properties > change default authentication level to 'packet integrity' rather than 'connect'

@BPry  @nikoolayy1 Any ideas here?

[HutchisonPorts]

I am Having the problem also with two different pan-os 9.1.3 and 10.0.4

[Ben-Price · Accepted solution]

@HutchisonPorts @PavanT @DarrinH @BPry 

Managed to fix this issue with a workaround, by configuring the firewall to use WinRM-http over Kerberos. Reference links below:

https://libredd.it/r/paloaltonetworks/comments/pl5dm7/new_2019_dc_event_log_messages_from_panos_user...

https://live.paloaltonetworks.com/t5/general-topics/best-way-of-doing-user-id-mapping-wmi-winrm-http...

https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/user-id/map-ip-addresses-to-users/configur...

[echahine]

Ben I'm trying to do the same, and I followed the links down to the last detail, and I'm getting connection refused(0). Any ideas?

[Ben-Price]

@echahine where are you seeing that error? can you provide a screen shot or log file?

[echahine]

First I'm seeing a connection refused on the GUI (image attached), and the error we're getting in the logs is connection failed, error code=0

[PavanT]

@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

[echahine]

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.

[jthoyle]

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". 

[denisse_puebla]

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

[bserrato]

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