Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, May 26, 2019 5:17 AM
We are facing issues in DHCP which is showing as "BAD IP ADDRESS" for a particular VLAN where the wired users connecting to it.
we have 802.1x Authiecation enabled in all the switches. we could not find any logs in switches ?
can any one let us know what we need to check in DHCP Server 2016 ?
Please find the below outputs which are captured in DHCP server scope for a particular Vlan where the wired users used to connect.
Due to this our scope is filling out every day. temporary we are deleting the bad address manually in DHCP.
192.168.242.116 BAD_ADDRESS 5/24/2019 6:01:58 AM DHCP 74f2a8c0 This address is already in use Full Access N/A None
Can any one help on this.
All replies (12)
Monday, May 27, 2019 2:45 AM
Hello vinuwhity,
Thank you for posting in this forum.
BAD_ADDRESS usually indicates an address conflict. This means that the IP address in the lease distributed by the DHCP server has been used by other clients.
The example you gave shows that this is an issue with address conflicts.
Please refer to this article: Enable IP Address Conflict Detection to enable DHCP conflict detection ( Although the versions are different, the operation is the same ), which will automatically solve the problem caused by address conflicts.
Best Regards,
Leon
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, May 27, 2019 7:28 AM
Hey we are currently running windows 2016 sever.
I could see the article related to windows 2008 server.
Monday, May 27, 2019 7:34 AM
Hi vinuwhity,
This article just shows you the specific steps to enable this feature.
I have checked Windows Server 2016 and the steps to enable that feature are the same as those described in the article.
Best Regards,
Leon
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, May 28, 2019 6:59 AM
i will check with DHCP team will update further.thanks for the information.
Tuesday, May 28, 2019 9:49 AM
I dont see this option in 2019. while cliking advance its showing the path name .
currently we are using 2019 DHCP server R2 Standard .
Wednesday, May 29, 2019 5:52 AM
Hi,
I installed the operating system of Windows Server 2019 today. I found that even on this operating system, the steps are still the same.
Right-click IPv4->Properties->Advanced->Conflict detection attempts.
For Conflict detection attempts, type a number greater than 0 (zero) and less than 6, and then click OK. The number you type determines how many times the DHCP server tests an IP address before leasing it to a client.
In addition, which machine is your DHCP server installed on? 2016 or 2019?
Best Regards,
Leon
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, June 3, 2019 9:32 AM
Hi,
Just checking in to see if the information provided was helpful.
Please let us know if you would like further assistance.
Best Regards,
Leon
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, June 7, 2019 8:18 AM
Hi,
Was your issue resolved?
If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
If no, please reply and tell us the current situation in order to provide further help.
Best Regards,
Leon
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, June 26, 2019 3:19 PM
still i facing that issue after increasing the conflict detection attempts
Monday, December 23, 2019 4:27 PM
Check DHCP logs under Windows\System32\DHCP\ Open log in notepad for any day and search for conflict. The line above it will give you system name which is a Rogue system which repeatedly looks out for IP and cause scope to run out.
Find these systems and take them out of network and re-image them.
Log Sample -
12/19/19,08:36:36,Renew,10.24.117.252,system,7A1B5B6B,,1062426,0,,,,0x4D5E30,MSFT 5.0,,,,0
12/19/19,08:36:40,Conflict,10.24.117.252,BAD_ADDRESS,,,0,6,,,,,,,,,0
Also for quick work around
Add these systems to DHCP reservation until you fix why their IP request issues.
Wednesday, February 26, 2020 12:59 PM
Hi,
Could you pls share how this issue is resolved?
Regards:Mahesh
Friday, March 6, 2020 8:15 AM
Pls refer the below thread for full details
Regards:Mahesh