<?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: DHCP Server Delay in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45264#M33261</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Upgrading to 4.1.13 or 5.0.5 will solve the issue... it was an implementation issue in the way that PA's DHCP server was implemented. The PA wasn't responding with a NACK when a&amp;nbsp; DCHP&amp;nbsp; client requested an IP outside of the PA's IP pool (a "SHOULD" implementation detail as defined per the DHCP RFC), so the client was timing out, which was causing the delay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI we went to 4.1.13 on our internal firewalls and the issue has gone away.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Jul 2013 19:48:48 GMT</pubDate>
    <dc:creator>ericgearhart</dc:creator>
    <dc:date>2013-07-19T19:48:48Z</dc:date>
    <item>
      <title>DHCP Server Delay</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45261#M33258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone ever encountered a delay when the PA is handing out DHCP?&amp;nbsp; I have a test network setup to do some captive portal testing for our guest network and I'm noticing it's taking anywhere between 5 - 25 seconds to get an IP address.&amp;nbsp; Wireless network is set for open with no encryption (just for testing remember).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not saying it's not something to do with our wireless controllers, just wondering if anyone else has ever experienced anything like this...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2012 19:09:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45261#M33258</guid>
      <dc:creator>mrsold</dc:creator>
      <dc:date>2012-11-20T19:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server Delay</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45262#M33259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may be running into a delay for the client to send a discover. If you run a PCAP you can confirm. Windows will sometimes make a DHCP request with a transactionID which does not belong to the pan. The request is also using DHCP option 50 and requesting the same Ip address. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will retry for 30 seconds and then send another discover with new transaction ID and the pan will respond to this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The pan does not send a Neg Ack to the original request but will answer a new discover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dominic&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2012 20:19:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45262#M33259</guid>
      <dc:creator>dburns</dc:creator>
      <dc:date>2012-11-20T20:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server Delay</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45263#M33260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So was it ever determined how to resolve this issue identified?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 19:08:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45263#M33260</guid>
      <dc:creator>tlyde</dc:creator>
      <dc:date>2013-07-19T19:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server Delay</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45264#M33261</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Upgrading to 4.1.13 or 5.0.5 will solve the issue... it was an implementation issue in the way that PA's DHCP server was implemented. The PA wasn't responding with a NACK when a&amp;nbsp; DCHP&amp;nbsp; client requested an IP outside of the PA's IP pool (a "SHOULD" implementation detail as defined per the DHCP RFC), so the client was timing out, which was causing the delay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI we went to 4.1.13 on our internal firewalls and the issue has gone away.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 19:48:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-delay/m-p/45264#M33261</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-07-19T19:48:48Z</dc:date>
    </item>
  </channel>
</rss>

