<?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: ping -a not resolving name anymore in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445497#M100478</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;I hope any one tell me how this ping -a works.&lt;/P&gt;&lt;P&gt;is it working by querring the name "from the DNS" so I need to have access to the DNS which is already provided.&lt;/P&gt;&lt;P&gt;is it using the netbios name? how to enable this app in the security rules?&lt;/P&gt;&lt;P&gt;"by the way, just now I found the ping -a is working to other zone"&lt;/P&gt;</description>
    <pubDate>Thu, 04 Nov 2021 15:11:56 GMT</pubDate>
    <dc:creator>MRamadanAHafiez</dc:creator>
    <dc:date>2021-11-04T15:11:56Z</dc:date>
    <item>
      <title>ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445019#M100418</link>
      <description>&lt;P&gt;Hello Bro,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;In our network we used to be in the same vlan of our employees endpoint and we used to use the command ping -a x.x.x.x&lt;/P&gt;&lt;P&gt;to resolve the name of the pinged IP.&lt;/P&gt;&lt;P&gt;after we have moved our PCs "admins" to a different zone, now we can't use this command anymore, the ping is working but the paramenter -a is not getting any names.&lt;/P&gt;&lt;P&gt;knowing that we have a full access to the dns still.&lt;/P&gt;&lt;P&gt;I belive this is firewall matter and as I read ping -a uses some layer 2 staff.&lt;/P&gt;&lt;P&gt;things are not clear, so how to have ping -a getting the names with the command output again?&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 17:07:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445019#M100418</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-11-02T17:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445097#M100423</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/159497"&gt;@MRamadanAHafiez&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This option works perfectly fine through security zones on my firewall without any issues. If this only started happening after you moved these machines into a new security zone, try enabling logging on your interzone-default to ensure your capturing denied traffic and see if anything is getting blocked due to not being included in your rulebase.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 23:50:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445097#M100423</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-11-02T23:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445127#M100431</link>
      <description>&lt;P&gt;Thank you &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;so much for the reply.&lt;/P&gt;&lt;P&gt;We are not blocked from anything from our new zone, and the monitor logs says nothing denied.&lt;/P&gt;&lt;P&gt;I will double check but if you tell me how ping-a works that may help me resolving it.&lt;/P&gt;&lt;P&gt;Any ideas appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 04:52:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445127#M100431</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-11-03T04:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445128#M100432</link>
      <description>&lt;P&gt;Was the name resolution working via DNS or Netbios? It’s possible it was Netbios and reason it worked prior to the move.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 05:24:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445128#M100432</guid>
      <dc:creator>aortiz</dc:creator>
      <dc:date>2021-11-03T05:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445142#M100436</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/195251"&gt;@aortiz&lt;/a&gt;&amp;nbsp;name resolution working via dns no problem after and before zones separation, this is for dns.&lt;/P&gt;&lt;P&gt;But after changing to the new zone ping -a x.x.x.x&amp;nbsp; Not working "was working before Changing zone".&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 06:54:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445142#M100436</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-11-03T06:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445396#M100462</link>
      <description>&lt;P&gt;If it worked via DNS and your DNS traffic is not being blocked, then it should still work. I suspect the name resolution was working via Netbios which uses broadcast destination address and most likely not being forwarded across. You can test ping -a from new zone to verify it still works on same broadcast domain and play with nslookups to test DNS.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 23:46:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445396#M100462</guid>
      <dc:creator>aortiz</dc:creator>
      <dc:date>2021-11-03T23:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445401#M100463</link>
      <description>&lt;P&gt;Hi, 1. can you check interface setting and its zone protection configuration. It may be possible ping is blocked on interface level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. can you check output of tracert and check where it gets dropped . It will give you idea about the hop which comes in between source and destination. You can check all devices if you are sure that PA configuration is fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Is ping not working for specific subnet or whole network&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 00:39:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445401#M100463</guid>
      <dc:creator>Dalidali</dc:creator>
      <dc:date>2021-11-04T00:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445473#M100473</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/159497"&gt;@MRamadanAHafiez&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Offhand I don't know how ping -a functions in the background and whether it uses netbios or DNS for the name resolution. The only thing that I can tell you for sure is that I can do it successfully across security zones without any issues. This is the first time that I've actually even heard of ping -a, and it's not extremely useful personally, but it's perfectly functional across L3 security zones without any issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 13:38:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445473#M100473</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-11-04T13:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445497#M100478</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;I hope any one tell me how this ping -a works.&lt;/P&gt;&lt;P&gt;is it working by querring the name "from the DNS" so I need to have access to the DNS which is already provided.&lt;/P&gt;&lt;P&gt;is it using the netbios name? how to enable this app in the security rules?&lt;/P&gt;&lt;P&gt;"by the way, just now I found the ping -a is working to other zone"&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 15:11:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445497#M100478</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-11-04T15:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445984#M100524</link>
      <description>&lt;P&gt;Hello Bro,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; After using the packet capture, I have discovered that the commanf ping -a x.x.x.x uses the LLMNR "Linl-Layer Multicast name resolution", Kindly anyone correct me or tell me how to allow this kind of multicast app " abit risky app, but i need to POC it"&lt;/P&gt;</description>
      <pubDate>Sat, 06 Nov 2021 20:49:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/445984#M100524</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-11-06T20:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: ping -a not resolving name anymore</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/446846#M100633</link>
      <description>&lt;P&gt;Use of LLMNR is not recommended. I suggest you use DNS for name resolution.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Nov 2021 23:43:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-a-not-resolving-name-anymore/m-p/446846#M100633</guid>
      <dc:creator>aortiz</dc:creator>
      <dc:date>2021-11-10T23:43:05Z</dc:date>
    </item>
  </channel>
</rss>

