Conflict detection attempts Windows DHCP Server


Recommended Posts

I am confused about the "Conflict detection attempts" feature in a Windows DHCP Server. I wanted to set this to a higher value than 1, Say for example 4 or 5. This would wait 5 pings before assigning a client device a spare IP. This should stop all 99.99% of IP Conflicts appearing on Windows Client Devices. Is this right? As its pretty certain after 5 pings that address is free.

However I was told that this number is the number of Rouge DHCP Servers that are allowed on the network so it has to be set at 1 and that if it detected 1 (or more) DHCP servers on the network it shuts itself down.

Which is correct?

Well for starters something not answering ping does not mean its not there on that IP, its firewall might just prevent answering ping.

What windows dhcp server are you using 2k8r2, 2012, 2016?

https://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx

I have never seen any sort of setting that detection of another dhcp server it would shut it self down, this seems like a self defeating sort of feature - if detect rouge dhcp server, shut yourself down and allow just the rouge?  That doesn't seem like a good idea.

  On 20/11/2015 at 15:02, BudMan said:

Well for starters something not answering ping does not mean its not there on that IP, its firewall might just prevent answering ping.

What windows dhcp server are you using 2k8r2, 2012, 2016?

https://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx

I have never seen any sort of setting that detection of another dhcp server it would shut it self down, this seems like a self defeating sort of feature - if detect rouge dhcp server, shut yourself down and allow just the rouge?  That doesn't seem like a good idea.

Yeah sorry, I meant normal LAN stuff that does allow DHCP. Firewall isnt the issue is, More ping latency. So hence I set I would have set it to 4 or 5 rather than one. 2012 server.

setting it higher than 3 could cause for lots of issues in delays in getting a lease.  Many hosts that do dhcp have firewalls and do not answer ping..  Windows built in firewall blocks pings for example out of the gate, it might allow from same segment..  But many dhcp servers are not directly on the same segment, you use a relay/helper say on the switch to forward the dhcp request to the dhcp server.

Many clients and servers also check that nothing answers an arp for that IP, if they show that IP in use they would send back a decline for that lease to the dhcp server.  This was back in the NT4 days, like sp 2 or something when they added that dhcpdecline feature from the rfc 1541 I do believe.

To be honest duplicate IPs handed out by dhcp server is very rare these days, normally its statics where this happens because of lack of good IP management.  Or misconfiguration of dhcp servers where you have more than 1 using, etc..  Most clients wont even accept a lease for a IP they find as duplicate.  I can not recall the last time I have seen a dupe IP issue with dhcp servers.

So for example here is a sniff of dhcp transaction.  Notice right after the discover that arps are sent, server asking hey anyone have this IP 192.168.3.101...  If nothing back it sends the offer, then the request and then you see the ack, you also see right after the ack the client sends out a ARP saying hey anyone got this 192.168.3.101 address.  If the client got something back, it should then send a decline to the dhcp server and then ask for another IP.  The decline would say hey, I don't like that address since something else seems to have it.  And then do another discover process after the dhcp server should of marked that IP as bad.

dhcpprocess.thumb.png.9c2ca0a8c9a988cb35

To be honest you shouldn't even have to send out pings, like I mentioned many devices might not even answer that - but have never seen anything not answer ARP..  Even with a firewall.

If you may have guessed dhcp is one of my fun protocols ;)  Just like dns...  If your having problems with dupes -- be more than happy to track down the reason with you.

 

Edited by BudMan

Are your different DHCP servers have different scopes?

Besides a router issue I can  see both servers trying to give an IP address that is the same. One handshakes and gives it an IP address while the other DHCP server thinks it's free and reports a conflict as it is already assigned.

In addition I believe you can set your servers to use DHCP assigned to a SID during it's lease too which could stop conflicts as one hand (DHCP server) doesn't know what the other is doing. Set different scope ranges for each box and try to assign to MAC or SID during a lease. So let's say someone shut's down his or her pc before the lease is up? The system comes back and does another DHCP broadcast when the LAN is initialized. The SID is recognized and the previous IP address is assigned. That would cut this down.

  On 20/11/2015 at 15:02, BudMan said:

Well for starters something not answering ping does not mean its not there on that IP, its firewall might just prevent answering ping.

What windows dhcp server are you using 2k8r2, 2012, 2016?

https://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx

I have never seen any sort of setting that detection of another dhcp server it would shut it self down, this seems like a self defeating sort of feature - if detect rouge dhcp server, shut yourself down and allow just the rouge?  That doesn't seem like a good idea.

2000 and 2003 did from what I remember, vaguely remember them shutting down when dhcp was handed out by gateway. I haven't really played with multiple dhcp severs on 2008, but 2012 does have a load balancing feature. 

I don't recall that, but sure its  possible - not like MS doesn't do some really stupid ###### all the time..  Now I could see if dhcp server was set to non authoritative and it saw an authoritative dhcp server, maybe.. But you would normally always have your dhcp set for authoritative..  Otherwise you can have issues with devices that come from other networks and have other leases switching to your network.

Not exactly sure what John T is after here, to be honest I would just leave it at 0, it should arp and the client should arp as well looking for devices that already have that IP..  Having it "ping' is just going to slow down the handing out of leases.  Ping would be useful if the dhcp server is not on the same layer 2 as the clients, ie you relay/helper to get to your dhcp server.  Since his arp is not going to get an answer if he is on a different l2 segment.  You should be ok since the client should detect and send back decline..  But if you have lots of different devices/os'es on our network - its possible some dhcp clients don't do proper checking or use of decline, etc.

Without a better understanding of the specific network, how dhcp is deployed in the network - the issue being seen..  To just answer the generic question, if you want to use that feature and have your dhcp server ping - 1 should be enough..  I sure and the hell would not go above say 3 or your going to have issues I would think with waiting for that to come back before the offer is sent.

LOL! DHCP servers don't shut down, they just don't hand out the IP address because another DHCP server has answered the broadcast. 

If you have multiple DHCP servers on your network, you can do a 70\30 or 80\20 scope split, which then you'd use the delay option on one of the servers.

I remember the down arrow on the 03 server when a linksys was handing out addresses.  Or maybe it was 00.  I don't remember the details, I remember the troubleshooting. 

Edited by sc302
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I enjoy using Discover Weekly. I have found new music using it. Just sometimes it goes off the rails and doesn't remember I don't like rap. I'm not sure this update is anything helpful, but I guess I'll try it if it comes to free accounts.
    • Yep, I got 250 mbps down / 50 mbps up on Qatar last week and about a 30 ms ping.
    • Here are all the new features added to Microsoft 365 Copilot in June 2025 by Usama Jawad Towards the end of each month, Microsoft publishes a roundup of the features that it added to some of its popular software in the previous four weeks. We have already talked about the new capabilities introduced in Excel and Teams during the month of June 2025, and now, it's time to talk about Microsoft 365 Copilot. We'll start off with admin-facing capabilities since there are only a few of them. For starters, the usage metrics for Copilot in the Copilot Analytics tool now have new prompt categories that give more insights as to how users are engaging with Copilot. This feature has just begun rolling out, but another enhancement to the usage metrics that is already available is dedicated statistics for intelligent meeting recaps. Finally, Microsoft 365 admins can now view and manage their inventory of agents and connectors and also have more granular control over costs and billing policies. On the user side of things, we have intelligent assistance in Copilot Chat, powered by ContextIQ. This layer of intelligence can scope prompts to internal (SharePoint, OneDrive) and external data sources, find files in the chat, and proactively offer relevant suggestions as you type. In the same vein, the Copilot mobile app is being updated so you can talk to the AI in a natural manner using your voice. In addition, users can also get access to deep reasoning agents such as Researcher and Analyst for more complex and research-oriented needs. The Create experience in the app is also being updated with the ability to generate stories and branded templates. Other interesting Copilot capabilities rolling out to Edge customers are the ability to prompt the AI through the search bar, access agents from within the browser, and take advantage of Copilot's impressive text summarization capabilities. That's not all though, other features in tow include: Enhancements to Copilot in Outlook: Schedule meetings through Copilot chat, summarization of email attachments, a new sidebar experience in the classic Outlook app, meeting preparation, and automated meeting invite creation Improved image generation and large file handling in Copilot Chat: More photorealistic image generation with better text depiction, ability to generate longer summaries from bigger files, and PDF scanning capabilities for insights Memory in Copilot: Copilot will now remember certain items from your conversation and you can modify or delete them Transferred calls summary with Copilot in Teams Phone: Generate a summary of a call and transfer it to a target New file extension for Copilot Pages: Copilot Pages will now have .page extension with an updated file icon Copilot Notebooks availability in OneNote: We already covered this in detail here Seamlessly add brand-approved images with Copilot in PowerPoint: Integration of Copilot with SharePoint Organization Asset Library (OAL) and Templafy asset libraries Explain formulas on the grid with Copilot in Excel: Self-explanatory, exactly what it says on the tin Expanded availability for the Microsoft 365 Copilot app: Availability of the Microsoft 365 Copilot app on Mac You can read more details about each of the aforementioned features here.
    • Damn, I blocked OldGuru a long time ago and you have to go and quote them so I have to read that creepy a$$ take. LOL Anyway 100% that dude can't find women that will have sex with him.
    • OneNote for Windows gets support for Dynamic DPI by Usama Jawad OneNote for Windows (part of Microsoft 365) is a pretty useful app if you're actively engaged in note-taking activities and also appreciate some rich text formatting capabilities. In fact, it also offers some decent integrations with Copilot, which make it an important piece of software in productivity-based environments. Now, Microsoft has introduced a feature that will likely make people with multi-monitor setups very happy. The OneNote for Windows application now supports Dynamic DPI (dots per inch). What this means is that you can use OneNote across any screen and it will scale according to the display's resolution, and you won't get a disconcerting and distracting blurring effect. You can extend your display to a high-resolution monitor and shift OneNote across displays without a hitch or any distraction. This is similar to the UX that is already present in Word, Excel, and PowerPoint. This Dynamic DPI support not only extends to the main text area but also to the section tabs, the Notebooks pane, drop-down menus, and Copilot Notebooks. All of these should look crisp and polished moving forward, without any manual adjustment or even an app restart required from the user's side. Microsoft has highlighted that it was encouraged to work on this capability after receiving user feedback from customers in this area. Dynamic DPI is now available to Current Channel (CC) customers on OneNote for Windows, running Version 2504 (Build 16.0.18827.20042) or later. That's not all, though. Another smaller enhancement present in OneNote moving forward is a revamped setup experience when you launch OneNote on a new Windows device for the first time. You will now receive a list of your five most recently used (MRU) notebooks that will open instantaneusly with a click. If you have more than five notebooks, you can pick and choose the files that you want to open. That said, Microsoft is looking to expand and improve on this experience in the future since it is fairly limited right now.
  • Recent Achievements

    • Week One Done
      dennis Nebeker earned a badge
      Week One Done
    • One Year In
      timothytoots earned a badge
      One Year In
    • One Month Later
      CHUNWEI earned a badge
      One Month Later
    • Week One Done
      TIGOSS earned a badge
      Week One Done
    • First Post
      henryj earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +FloatingFatMan
      194
    3. 3
      ATLien_0
      163
    4. 4
      Xenon
      78
    5. 5
      wakjak
      72
  • Tell a friend

    Love Neowin? Tell a friend!