<?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: No ping response from AAD in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246591#M6624</link>
    <description>&lt;P&gt;There are no drops and 0 bytes for return traffic&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jan 2026 15:15:27 GMT</pubDate>
    <dc:creator>ciscojuniperf5</dc:creator>
    <dc:date>2026-01-26T15:15:27Z</dc:date>
    <item>
      <title>No ping response from AAD</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246507#M6621</link>
      <description>&lt;P&gt;I have a rule in Palo Alto PA 440 running 11.2.6 to allow 'any' to Azure AD. I see only DNS responses from Azure AD. For ping and LDAP packets received is zero. The traffic is hitting the right rule though. I did a packet capture I don't see ping request on the transmit stage on the firewall. Ping and LDAP working from another site. How do I fix this.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jan 2026 06:07:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246507#M6621</guid>
      <dc:creator>ciscojuniperf5</dc:creator>
      <dc:date>2026-01-25T06:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: No ping response from AAD</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246552#M6623</link>
      <description>&lt;P&gt;First, verify the routing to ensure there is no asymmetric routing in the network.&lt;BR /&gt;You can identify the correct egress interface for the traffic using the following command:&lt;BR /&gt;&lt;STRONG&gt;test routing fib-lookup virtual-router default ip 8.8.8.8&lt;/STRONG&gt;&lt;BR /&gt;If the monitor logs show 0 bytes for return traffic, it likely indicates that the return path is taking a different route. Do you see any drops in packet capture?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 04:53:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246552#M6623</guid>
      <dc:creator>arusharma</dc:creator>
      <dc:date>2026-01-26T04:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: No ping response from AAD</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246591#M6624</link>
      <description>&lt;P&gt;There are no drops and 0 bytes for return traffic&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 15:15:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246591#M6624</guid>
      <dc:creator>ciscojuniperf5</dc:creator>
      <dc:date>2026-01-26T15:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: No ping response from AAD</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246594#M6625</link>
      <description>&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN&gt;Thank you for your response. This issue is now resolved. A route to this site subnet was missing in Azure, it started working once the route was added in Azure&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 26 Jan 2026 15:43:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/no-ping-response-from-aad/m-p/1246594#M6625</guid>
      <dc:creator>ciscojuniperf5</dc:creator>
      <dc:date>2026-01-26T15:43:31Z</dc:date>
    </item>
  </channel>
</rss>

