<?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 DHCP Server - Conflict IP's in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-conflict-ip-s/m-p/1248396#M126004</link>
    <description>&lt;P&gt;Has anybody else experienced an issue with their DHCP server leases being constantly filled up with conflict IP's by one device?&lt;/P&gt;
&lt;P&gt;There is no pattern to which device will do this, it seems at random. I'm on version 11.1.6&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any guidance would be much apricated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CPATT_0-1771337718677.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/70712i45F273E264AE7528/image-size/medium?v=v2&amp;amp;px=400" role="button" title="CPATT_0-1771337718677.png" alt="CPATT_0-1771337718677.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Feb 2026 14:20:37 GMT</pubDate>
    <dc:creator>CPATT</dc:creator>
    <dc:date>2026-02-17T14:20:37Z</dc:date>
    <item>
      <title>DHCP Server - Conflict IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-conflict-ip-s/m-p/1248396#M126004</link>
      <description>&lt;P&gt;Has anybody else experienced an issue with their DHCP server leases being constantly filled up with conflict IP's by one device?&lt;/P&gt;
&lt;P&gt;There is no pattern to which device will do this, it seems at random. I'm on version 11.1.6&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any guidance would be much apricated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CPATT_0-1771337718677.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/70712i45F273E264AE7528/image-size/medium?v=v2&amp;amp;px=400" role="button" title="CPATT_0-1771337718677.png" alt="CPATT_0-1771337718677.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2026 14:20:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-conflict-ip-s/m-p/1248396#M126004</guid>
      <dc:creator>CPATT</dc:creator>
      <dc:date>2026-02-17T14:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server - Conflict IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-conflict-ip-s/m-p/1248419#M126011</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1024229019"&gt;@CPATT&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So&amp;nbsp;when the firewall is acting as a DHCP server, it performs an ARP probe before assigning an IP address. If any device responds to that ARP request, the firewall assumes the IP is already in use and marks it as conflict IP, removing it from the available pool.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since there are multiple conflicts and all are coming up within the 192.168.2.0/24 subnet, Im wondering if you have something within that VLAN that is responding to multiple addresses. Log into the CLI and run a show arp all. Are there multiple IPs mapped to the same MAC?&amp;nbsp;Also, in Monitor -&amp;gt; System logs, do you see any “conflicting ARP” entries that list a sender MAC?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Feb 2026 05:28:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-conflict-ip-s/m-p/1248419#M126011</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2026-02-18T05:28:06Z</dc:date>
    </item>
  </channel>
</rss>

