none
Strange records in DHCP server RRS feed

  • Question

  • Hello All,

    Every day I see a log off strange records on my DHCP server. Can anybody help with troubleshoot steps? 

    I remove them manually but I want to find a root case. 

    Saturday, August 17, 2019 6:18 PM

All replies

  • Hi,

    how long is the lease time? Is it a scope failover configuration?

    A BAD_ADDRESS entry appears if a DHCP client rejects the address offered to it as a lease by the DHCP server. This usually means that *at that time* this IP address was in use by somebody else. This is often seen in DHCP server migrations where you migrate the scopes but not the leases.

    There is a setting "Number of conflict detection attempts" in the properties of the "IPv4" node. It is set to 0 by default. Try increasing this to 3 and, if the BAD_ADDRESS problem goes away, lowering it to 1.


    Evgenij Smirnov

    http://evgenij.smirnov.de


    Sunday, August 18, 2019 8:55 AM
  • Hi,

    how long is the lease time? Is it a scope failover configuration?

    A BAD_ADDRESS entry appears if a DHCP client rejects the address offered to it as a lease by the DHCP server. This usually means that *at that time* this IP address was in use by somebody else. This is often seen in DHCP server migrations where you migrate the scopes but not the leases.

    There is a setting "Number of conflict detection attempts" in the properties of the "IPv4" node. It is set to 0 by default. Try increasing this to 3 and, if the BAD_ADDRESS problem goes away, lowering it to 1.


    Evgenij Smirnov

    http://evgenij.smirnov.de


    Hello Evgenij,

    Yes, DHCP in Hot standby mode.

    I see this along time. thx, will try.

    Sunday, August 18, 2019 9:27 AM
  • Hi,

    how long is the lease time? Is it a scope failover configuration?

    A BAD_ADDRESS entry appears if a DHCP client rejects the address offered to it as a lease by the DHCP server. This usually means that *at that time* this IP address was in use by somebody else. This is often seen in DHCP server migrations where you migrate the scopes but not the leases.

    There is a setting "Number of conflict detection attempts" in the properties of the "IPv4" node. It is set to 0 by default. Try increasing this to 3 and, if the BAD_ADDRESS problem goes away, lowering it to 1.


    Evgenij Smirnov

    http://evgenij.smirnov.de


    Now  I see 15+ bad_addresses each time.
    Friday, August 23, 2019 4:54 PM