User authentication errors with Active Directory

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

User authentication errors with Active Directory

L4 Transporter

 

 

Hi,

 

We have a problem with a FW Paloalto: Model: VM300

 

We have had to upgrade the functional level of our Microsoft domain and update security patches of our Domain controllers on Windows 2012R2. As of this moment we are receiving in the domain controllers the following error:

"The server-side authentication level policy does not allow the user CENTRAL\adminXXX SID (S-1-5-21-2134262353-1336673973-2068054413-6951) from address 192.168.XX.XX to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application."

 

Could anybody helps me?

 

Thanks so much

 

Regards

 

5 REPLIES 5

L3 Networker

Hi AlPalo,

 

if you change the integrated PanOs user-id  agent from WMI to WinRM http or https, will resolve this problem for you.

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

Hi,

 

thanks for your answer, but i cannot deployment user-id. Are there another solution since AD without do anything on the FW?

 

Regards

L1 Bithead

We have change to "WinRM over HTTPS with Kerberos" and we are still getting the event log error :

The server-side authentication level policy does not allow the user Domain\userid SID (S-XXXXXXXXXXXXXXXXXXXXXXX) from address FW_INTERNAL_IP to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.

What could be still active?

Cyber Elite
Cyber Elite

Hi @MEDOCHEMIE and @Alpalo ,

 

Please see this thread -> https://live.paloaltonetworks.com/t5/general-topics/user-identification-and-winrm-on-http/m-p/481674 and let me know if you are able to fix the issue.

 

Thanks,

 

Tom

Help the community: Like helpful comments and mark solutions.

L1 Bithead

Hi @TomYoung,

unfortunately i did not find something that will work in our case.

We don't want to disable AgentLess UserID nor to perform the reg hacks for DCOM access.

WinRM-HTTPS with Kerberos should have been working natively according to PaloAlto.

There is something else messing which i cannot find it.

  • 12140 Views
  • 5 replies
  • 0 Likes
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!