<?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 Re: Why Firewall is not detecting Active Directory? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332447#M84047</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;My guess is that the user-id agent cannot talk to Active Directory for some reason. Perhaps the service account you are using does not have the proper permissions or its a routing issue. Here are a few links that may help out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Configuring and troubleshooting&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5bCAC" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5bCAC&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Practices for securing user-id:&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVPCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVPCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jun 2020 21:59:28 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2020-06-08T21:59:28Z</dc:date>
    <item>
      <title>Why Firewall is not detecting Active Directory?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332211#M84011</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have configured the User-ID to authenticate Global Protect's users and for User Mapping.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, the Firewall shows the LDAP as "host unreachable".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have an MGT IP address, but I have changed the LDAP's service route to look for LDAP's request in the internal interface. Also, I have checked the User and Password in the Server Profile and everything is ok.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a step that I am missing or is it something related to the MGT interface?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2020 03:51:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332211#M84011</guid>
      <dc:creator>iscott</dc:creator>
      <dc:date>2020-06-08T03:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Why Firewall is not detecting Active Directory?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332319#M84031</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Do a packet capture (under Monitor), add all 4 stages, filter by LDAP server destination IP and add it also in a second filter stage as source (for returning traffic from LDAP server).&lt;/P&gt;&lt;P&gt;2. Once filter &amp;amp; pcap are active try to simulate LDAP authentication&lt;/P&gt;&lt;P&gt;3. If you see a drop stage pcap file see if it contains LDAP/389/636 traffic&lt;/P&gt;&lt;P&gt;4. If not you can open the transmit pcap and check the Palo Alto MAC address against 'show interfaces hardware' in ssh to match the MAC address against the physical interface - this will verify packet are egressing as per your service route configuration&lt;/P&gt;&lt;P&gt;5. Also just validate you are not NAT'ing this traffic by mistake&lt;/P&gt;&lt;P&gt;6. lastly, check security policy for a rule to match this traffic, Override the 'intrazone-default' &amp;amp; 'interzone-default' to add 'log at session end' so you'll see EVERYTHING (the default for these two is no log at all so you will not see monitor logs for hits on these 2 rules)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Shai&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2020 13:56:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332319#M84031</guid>
      <dc:creator>ShaiW</dc:creator>
      <dc:date>2020-06-08T13:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: Why Firewall is not detecting Active Directory?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332447#M84047</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;My guess is that the user-id agent cannot talk to Active Directory for some reason. Perhaps the service account you are using does not have the proper permissions or its a routing issue. Here are a few links that may help out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Configuring and troubleshooting&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5bCAC" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5bCAC&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Practices for securing user-id:&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVPCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVPCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2020 21:59:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-firewall-is-not-detecting-active-directory/m-p/332447#M84047</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2020-06-08T21:59:28Z</dc:date>
    </item>
  </channel>
</rss>

