<?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: Random UDP 137 to Public IP's after connecting global protect in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/random-udp-137-to-public-ip-s-after-connecting-global-protect/m-p/345616#M369</link>
    <description>&lt;P&gt;A little more information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This only seems to happen when global protect client is active, and doesn't happen on all clients.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The UDP 137 traffic is Net Bios Name Query (Appears to be reverse lookup)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Name query NBSTAT *&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt; to random Public IP's&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>Wed, 26 Aug 2020 18:51:26 GMT</pubDate>
    <dc:creator>JakeHarris</dc:creator>
    <dc:date>2020-08-26T18:51:26Z</dc:date>
    <item>
      <title>Random UDP 137 to Public IP's after connecting global protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/random-udp-137-to-public-ip-s-after-connecting-global-protect/m-p/345604#M367</link>
      <description>&lt;P&gt;After installing and connecting to Global Protect, FW policy logs are showing large amounts of UDP 137 getting blocking from Global Protect clients going to many random Public IP's.&amp;nbsp; Any idea what would cause this?&amp;nbsp; Public IP's have been MS, AWS, Google owned.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 17:38:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/random-udp-137-to-public-ip-s-after-connecting-global-protect/m-p/345604#M367</guid>
      <dc:creator>JakeHarris</dc:creator>
      <dc:date>2020-08-26T17:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Random UDP 137 to Public IP's after connecting global protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/random-udp-137-to-public-ip-s-after-connecting-global-protect/m-p/345616#M369</link>
      <description>&lt;P&gt;A little more information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This only seems to happen when global protect client is active, and doesn't happen on all clients.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The UDP 137 traffic is Net Bios Name Query (Appears to be reverse lookup)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Name query NBSTAT *&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt;&amp;lt;00&amp;gt; to random Public IP's&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>Wed, 26 Aug 2020 18:51:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/random-udp-137-to-public-ip-s-after-connecting-global-protect/m-p/345616#M369</guid>
      <dc:creator>JakeHarris</dc:creator>
      <dc:date>2020-08-26T18:51:26Z</dc:date>
    </item>
  </channel>
</rss>

