Share via

BAD_ADDRESS logged in DHCP server Windows Server 2019

Techshan 216 Reputation points
2022-08-16T21:57:44.99+00:00

Hello,

Recently we got an incident in which clients in one site in one particular subnet not able to connect to network.

Found that IP address is exhausted in that particular scope, when checked found that many BAD_ADDRESSES entries logged in DHCP server . We deleted those BAD_ADDRESS and got free IP's .

But we need to find the reason why BAD_ADDRESS are logged in DHCP server.

Can any one shed some lights on how to investigate?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,484 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,044 questions

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Techshan 216 Reputation points
    2022-09-19T20:40:23.593+00:00

    @Khuong_Nguyen

    How the first network adapter nnn.nn.1.1 replies the DHCP server for the ping request to second network adapter with address nnn.nn.1.2 and how the DHCP server marks nnn.nn.1.2 as BAD_ADDRESS?

    0 comments
  2. Avijit Dutta 1 Reputation point
    2022-09-20T06:28:10.487+00:00

    Few Suggestions, (might be possible you already performed these steps)

    1) Check for any Static IP in the workstations, if present, removes those IPs and reconcile the DHCP Database.
    2) Exclude the Server/Network device IPs from the DHCP Scope so that DHCP doesn't lease those IPs.

    0 comments
  3. Techshan 216 Reputation points
    2022-09-20T13:21:19.933+00:00

    In our environment, reservations are in place for static ip addresses in the scope for certain servers/workstations, still we are investigating the issue with MS

    0 comments
  4. Leachman, Michael 0 Reputation points
    2023-06-25T17:30:34.23+00:00

    The following Microsoft KB article is what helped solve the BAD_ADDRESS issues for us:

    https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-registration-behavior-when-dhcp-server-manages-dynamic-dns-updates

    We created a group policy preference (for all domain workstations) which added the following registry entry:

    1. Navigate to the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
    2. Under the subkey, create the following entry:
    • Name: RegistrationOverwrite
    • Type: REG_DWORD
    • Value: 2
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.