BAD ADDRESS in dhcp

Question

_{Wednesday, August 24, 2016 12:37 PM}

hi;
I use windows server 2012 r2 as DHCP server.
Scope:   192.168.0.1 - 192.168.1.254
Netmask: 255.255.254.0
Gateway: 192.168.1.223
DNS:  192.168.1.223

exclude: 192.168.1.1 - 192.168.1.254
  192.168.0.1 - 192.168.0.20
  192.168.0.240 - 192.168.0.254

the problem is the DHCP server leased BAD_ADDRESS for all IP Address.
the Reserved address works good; and the other ip list in the bad address.

All replies (6)

_{Wednesday, August 24, 2016 1:47 PM ✅Answered}

Hi

 Usually BAD ADDRESS temporary leases are created by the DHCP server when an IP conflict is detected. make sure that those addresses are not in use.
Check this and setup on your DHCP: http://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx

Once you setup DHCP conflict detection it should resolve the issue on DHCP and automatically resolve conflicts

Also if you have a dhcp failover cluster,you should check the article to fix;https://blogs.technet.microsoft.com/teamdhcp/2014/02/24/dhcp-failover-fixes-in-kb-2919393-for-windows-server-2012-and-kb-2919355-for-windows-server-2012-r2/

Otherwise you should check event viewer menu for error log's..

This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

_{Monday, October 17, 2016 6:29 AM ✅Answered}

hi again.

I use one Mikrotik Device in my network and thats the problem. the conflict dhcp in configuration.

thanks

_{Thursday, August 25, 2016 5:25 AM}

Thanks;
I check that and set delay to 1; but doesn't work.
I check the Events and see that Event ID: 20287
DHCP client request from C80084A02BB2 was dropped since the applicable IP address ranges in scope/super scope 192.168.0.1 - 192.168.1.254 are out of available IP addresses. This could be because of IP address ranges of a policy being out of available IP addresses.

2500 new error!!

how can I fix that?

_{Thursday, August 25, 2016 5:30 AM}

Thanks;
I check that and set delay to 1; but doesn't work.
I check the Events and see that Event ID: 20287
DHCP client request from C80084A02BB2 was dropped since the applicable IP address ranges in scope/super scope 192.168.0.1 - 192.168.1.254 are out of available IP addresses. This could be because of IP address ranges of a policy being out of available IP addresses.

2500 new error!!

how can I fix that?

_{Thursday, August 25, 2016 8:37 AM | 1 vote}

Hi

 You should first do DHCP database cleanup for expired leases (cause the issue)

http://social.technet.microsoft.com/wiki/contents/articles/25098.how-to-force-a-dhcp-database-cleanup-for-expired-leases-in-a-specific-scope.aspx

https://blogs.technet.microsoft.com/platformspfe/2014/08/12/windows-server-2012-r2-dhcp-expired-leases-not-getting-scavenged/

Then if necessary you should Increasing the number of IP addresses;

https://support.microsoft.com/en-us/kb/255999

Also you can check this ms article details about the issue;https://technet.microsoft.com/en-us/library/dn800668(v=ws.11).aspx

This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

_{Monday, September 5, 2016 2:06 AM}

Hi Seyed,

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.

Best Regards,

John

Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].