• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:


I am facing an environment of a single DHCP server running on Win NT 4.0 SP6a and 100+ Win XP/2000 workstations that's configured to get IP from DHCP. The server and clients are on the same subnet and there is only one scope configured on DHCP.
Every day I come across at least two BAD_ADDRESS on the DHCP console and the description says that "the address has been declined".
Could you suggest a way to prevent BAD_ADDRESS from happening on my DHCP server?
3 Solutions
Check if one of these articles appies:

IP addresses that are assigned to a DHCP client in a Windows XP environment are marked as BAD_ADDRESS in the DHCP server address lease table

Multihomed DHCP Clients May Cause "Bad_Address" Entry on a DHCP Server in Windows NT 4.0
look at that and if that or something like that happend to you: http://www.wer-weiss-was.de/theme119/article672848.html

Does all computers get an IP address from this server? or is there one that doesn't?
is there a fixed address out there not known to the DHCP server? after a client receives an IP it checks if it is already used by another machine on the same network; if it is, the client sends a "DHCPDECLINE" to the server which marks the address as "BAD ADDRESS" cause it exists in the range of the DHCP Server but is not assigned from it ;
Mark WaldenCommented:
I have never work in a NT environment, but this happens to us from time to time.  DHCP will ping an address to see if its out there.  If there is a reply from that address and DHCP does not know of it, DHCP will mark it as a bad address as stated above by Cruxy.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now