<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic User-ID Integration with AD Failing (Access Denied / Kerberos Errors – Event ID 10036) in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/user-id-integration-with-ad-failing-access-denied-kerberos/m-p/1233753#M6079</link>
    <description>&lt;P data-start="293" data-end="301"&gt;Hi Team,&lt;/P&gt;
&lt;P data-start="303" data-end="579"&gt;I'm working on integrating my &lt;STRONG data-start="333" data-end="375"&gt;Active Directory (Windows Server 2016)&lt;/STRONG&gt; with a &lt;STRONG data-start="383" data-end="412"&gt;Palo Alto PA-450 firewall&lt;/STRONG&gt; to enable &lt;STRONG data-start="423" data-end="448"&gt;User-ID functionality&lt;/STRONG&gt;. While setting up the server monitoring configuration, I'm running into issues when using both WMI and WinRM-based authentication.&lt;/P&gt;
&lt;H3 data-start="581" data-end="602"&gt;Issue Details:&lt;/H3&gt;
&lt;UL data-start="603" data-end="780"&gt;
&lt;LI data-start="603" data-end="686"&gt;
&lt;P data-start="605" data-end="686"&gt;When using &lt;STRONG data-start="616" data-end="623"&gt;WMI&lt;/STRONG&gt;: The firewall shows &lt;STRONG data-start="644" data-end="661"&gt;Access Denied&lt;/STRONG&gt; under Server Monitoring.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="687" data-end="780"&gt;
&lt;P data-start="689" data-end="780"&gt;When using &lt;STRONG data-start="700" data-end="723"&gt;WinRM with Kerberos Http&lt;/STRONG&gt;: The firewall shows &lt;STRONG data-start="744" data-end="779"&gt;Kerberos error&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-start="782" data-end="839"&gt;In the AD event viewer, I’m seeing the following message:&lt;/P&gt;
&lt;BLOCKQUOTE data-start="841" data-end="1129"&gt;
&lt;P data-start="843" data-end="1129"&gt;&lt;EM data-start="843" data-end="1105"&gt;The server-side authentication level policy does not allow the user &lt;CODE data-start="912" data-end="924"&gt;&amp;lt;username&amp;gt;&lt;/CODE&gt; from address &lt;CODE data-start="938" data-end="953"&gt;&amp;lt;firewall IP&amp;gt;&lt;/CODE&gt; to activate the DCOM server. Please raise the activation authentication level at least to &lt;CODE data-start="1044" data-end="1077"&gt;RPC_C_AUTHN_LEVEL_PKT_INTEGRITY&lt;/CODE&gt; in the client application.&lt;/EM&gt;&lt;BR data-start="1105" data-end="1108" /&gt;&lt;STRONG data-start="1110" data-end="1122"&gt;Event ID&lt;/STRONG&gt;: 10036&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;H3 data-start="1131" data-end="1165"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Troubleshooting Done So Far:&lt;/H3&gt;
&lt;UL data-start="1166" data-end="1594"&gt;
&lt;LI data-start="1166" data-end="1254"&gt;
&lt;P data-start="1168" data-end="1254"&gt;Verified that the &lt;STRONG data-start="1186" data-end="1205"&gt;AD user account&lt;/STRONG&gt; has local admin rights on the domain controller.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1255" data-end="1330"&gt;
&lt;P data-start="1257" data-end="1330"&gt;Confirmed &lt;STRONG data-start="1267" data-end="1276"&gt;WinRM&lt;/STRONG&gt; is enabled and configured correctly on the AD server.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1393" data-end="1461"&gt;
&lt;P data-start="1395" data-end="1461"&gt;Ensured the correct encryption types (AES128, AES256) are enabled.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1462" data-end="1538"&gt;
&lt;P data-start="1464" data-end="1538"&gt;Verified the firewall can resolve the FQDN and ping the domain controller.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1539" data-end="1594"&gt;
&lt;P data-start="1541" data-end="1594"&gt;Checked time synchronization between firewall and AD.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Also verified as mentioned in the below procedure&lt;BR /&gt;&lt;SPAN data-teams="true"&gt;&lt;A id="menur2a5" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://knowledgebase.paloaltonetworks.com/kcsarticledetail?id=ka10g000000clggca0" href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0" target="_blank" rel="noreferrer noopener" aria-label="Link https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0&lt;/A&gt;&lt;BR /&gt;&lt;A id="menur2a7" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://knowledgebase.paloaltonetworks.com/kcsarticledetail?id=ka10g000000clk0cac" href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC" target="_blank" rel="noreferrer noopener" aria-label="Link https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-start="1596" data-end="1683"&gt;Despite this, the firewall still fails to authenticate and collect user-to-IP mappings.&lt;/P&gt;
&lt;HR data-start="1685" data-end="1688" /&gt;
&lt;H3 data-start="1690" data-end="1712"&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt;Request for Help:&lt;/H3&gt;
&lt;P data-start="1713" data-end="1759"&gt;Can someone please help clarify the following:&lt;/P&gt;
&lt;UL data-start="1760" data-end="2132"&gt;
&lt;LI data-start="1760" data-end="1875"&gt;
&lt;P data-start="1762" data-end="1875"&gt;What specific &lt;STRONG data-start="1776" data-end="1812"&gt;DCOM or WinRM permission changes&lt;/STRONG&gt; are needed on the domain controller to allow this integration?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1876" data-end="2006"&gt;
&lt;P data-start="1878" data-end="2006"&gt;How to ensure &lt;CODE data-start="1892" data-end="1925"&gt;RPC_C_AUTHN_LEVEL_PKT_INTEGRITY&lt;/CODE&gt; is accepted by the AD server for connections coming from the Palo Alto firewall?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="2007" data-end="2132"&gt;
&lt;P data-start="2009" data-end="2132"&gt;Any &lt;STRONG data-start="2013" data-end="2029"&gt;Group Policy&lt;/STRONG&gt; or &lt;STRONG data-start="2033" data-end="2053"&gt;registry changes&lt;/STRONG&gt; required on the domain controller to allow Kerberos to work with the firewall?&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-start="2134" data-end="2187"&gt;Any insight or guidance would be greatly appreciated!&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jul 2025 18:37:27 GMT</pubDate>
    <dc:creator>M.R107318</dc:creator>
    <dc:date>2025-07-10T18:37:27Z</dc:date>
    <item>
      <title>User-ID Integration with AD Failing (Access Denied / Kerberos Errors – Event ID 10036)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/user-id-integration-with-ad-failing-access-denied-kerberos/m-p/1233753#M6079</link>
      <description>&lt;P data-start="293" data-end="301"&gt;Hi Team,&lt;/P&gt;
&lt;P data-start="303" data-end="579"&gt;I'm working on integrating my &lt;STRONG data-start="333" data-end="375"&gt;Active Directory (Windows Server 2016)&lt;/STRONG&gt; with a &lt;STRONG data-start="383" data-end="412"&gt;Palo Alto PA-450 firewall&lt;/STRONG&gt; to enable &lt;STRONG data-start="423" data-end="448"&gt;User-ID functionality&lt;/STRONG&gt;. While setting up the server monitoring configuration, I'm running into issues when using both WMI and WinRM-based authentication.&lt;/P&gt;
&lt;H3 data-start="581" data-end="602"&gt;Issue Details:&lt;/H3&gt;
&lt;UL data-start="603" data-end="780"&gt;
&lt;LI data-start="603" data-end="686"&gt;
&lt;P data-start="605" data-end="686"&gt;When using &lt;STRONG data-start="616" data-end="623"&gt;WMI&lt;/STRONG&gt;: The firewall shows &lt;STRONG data-start="644" data-end="661"&gt;Access Denied&lt;/STRONG&gt; under Server Monitoring.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="687" data-end="780"&gt;
&lt;P data-start="689" data-end="780"&gt;When using &lt;STRONG data-start="700" data-end="723"&gt;WinRM with Kerberos Http&lt;/STRONG&gt;: The firewall shows &lt;STRONG data-start="744" data-end="779"&gt;Kerberos error&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-start="782" data-end="839"&gt;In the AD event viewer, I’m seeing the following message:&lt;/P&gt;
&lt;BLOCKQUOTE data-start="841" data-end="1129"&gt;
&lt;P data-start="843" data-end="1129"&gt;&lt;EM data-start="843" data-end="1105"&gt;The server-side authentication level policy does not allow the user &lt;CODE data-start="912" data-end="924"&gt;&amp;lt;username&amp;gt;&lt;/CODE&gt; from address &lt;CODE data-start="938" data-end="953"&gt;&amp;lt;firewall IP&amp;gt;&lt;/CODE&gt; to activate the DCOM server. Please raise the activation authentication level at least to &lt;CODE data-start="1044" data-end="1077"&gt;RPC_C_AUTHN_LEVEL_PKT_INTEGRITY&lt;/CODE&gt; in the client application.&lt;/EM&gt;&lt;BR data-start="1105" data-end="1108" /&gt;&lt;STRONG data-start="1110" data-end="1122"&gt;Event ID&lt;/STRONG&gt;: 10036&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;H3 data-start="1131" data-end="1165"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Troubleshooting Done So Far:&lt;/H3&gt;
&lt;UL data-start="1166" data-end="1594"&gt;
&lt;LI data-start="1166" data-end="1254"&gt;
&lt;P data-start="1168" data-end="1254"&gt;Verified that the &lt;STRONG data-start="1186" data-end="1205"&gt;AD user account&lt;/STRONG&gt; has local admin rights on the domain controller.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1255" data-end="1330"&gt;
&lt;P data-start="1257" data-end="1330"&gt;Confirmed &lt;STRONG data-start="1267" data-end="1276"&gt;WinRM&lt;/STRONG&gt; is enabled and configured correctly on the AD server.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1393" data-end="1461"&gt;
&lt;P data-start="1395" data-end="1461"&gt;Ensured the correct encryption types (AES128, AES256) are enabled.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1462" data-end="1538"&gt;
&lt;P data-start="1464" data-end="1538"&gt;Verified the firewall can resolve the FQDN and ping the domain controller.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1539" data-end="1594"&gt;
&lt;P data-start="1541" data-end="1594"&gt;Checked time synchronization between firewall and AD.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Also verified as mentioned in the below procedure&lt;BR /&gt;&lt;SPAN data-teams="true"&gt;&lt;A id="menur2a5" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://knowledgebase.paloaltonetworks.com/kcsarticledetail?id=ka10g000000clggca0" href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0" target="_blank" rel="noreferrer noopener" aria-label="Link https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGGCA0&lt;/A&gt;&lt;BR /&gt;&lt;A id="menur2a7" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://knowledgebase.paloaltonetworks.com/kcsarticledetail?id=ka10g000000clk0cac" href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC" target="_blank" rel="noreferrer noopener" aria-label="Link https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clk0CAC&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-start="1596" data-end="1683"&gt;Despite this, the firewall still fails to authenticate and collect user-to-IP mappings.&lt;/P&gt;
&lt;HR data-start="1685" data-end="1688" /&gt;
&lt;H3 data-start="1690" data-end="1712"&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt;Request for Help:&lt;/H3&gt;
&lt;P data-start="1713" data-end="1759"&gt;Can someone please help clarify the following:&lt;/P&gt;
&lt;UL data-start="1760" data-end="2132"&gt;
&lt;LI data-start="1760" data-end="1875"&gt;
&lt;P data-start="1762" data-end="1875"&gt;What specific &lt;STRONG data-start="1776" data-end="1812"&gt;DCOM or WinRM permission changes&lt;/STRONG&gt; are needed on the domain controller to allow this integration?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1876" data-end="2006"&gt;
&lt;P data-start="1878" data-end="2006"&gt;How to ensure &lt;CODE data-start="1892" data-end="1925"&gt;RPC_C_AUTHN_LEVEL_PKT_INTEGRITY&lt;/CODE&gt; is accepted by the AD server for connections coming from the Palo Alto firewall?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="2007" data-end="2132"&gt;
&lt;P data-start="2009" data-end="2132"&gt;Any &lt;STRONG data-start="2013" data-end="2029"&gt;Group Policy&lt;/STRONG&gt; or &lt;STRONG data-start="2033" data-end="2053"&gt;registry changes&lt;/STRONG&gt; required on the domain controller to allow Kerberos to work with the firewall?&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-start="2134" data-end="2187"&gt;Any insight or guidance would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 18:37:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/user-id-integration-with-ad-failing-access-denied-kerberos/m-p/1233753#M6079</guid>
      <dc:creator>M.R107318</dc:creator>
      <dc:date>2025-07-10T18:37:27Z</dc:date>
    </item>
  </channel>
</rss>

