I have DHCP set up on an NT 4 server. When I look at some of the addresses that are being assigned, a few say "bad address". Does anyone know why this is and if the address can be repaired? Thanks

DHCP marks an address as bad when a client refuses the lease. This is typically caused when DHCP offers an IP that the client determines as already existing on that network. The BAD_ADDRESS will evetually clear when the lease time expires. You can manually remove the BAD_ADDRESS entries without any problems. Here's an article that helps explain the details a little better: http://www.win2000mag.com/Articles/Index.cfm?ArticleID=4827 I still get BAD_ADDRESS in my DHCP scopes but I don't understand why the client rejects the lease. I only allow DHCP to lease IP's above .100 on a segment, saving the .1-.99 IP's for network hardware, servers and printers. I can't imagine that a PC could get an offer for an IP that DHCP has leased to another PC. I suppose its possible the client could've received offers from both DHCP servers on that segment, accepted one and rejected the other. The rejected one would then show up as a BAD_ADDRESS.

SYMPTOMS DHCP Duplicate IP Detection is marking the IP address as Bad_Address when the response is "host unreachable". Duplicate IP detection code should read the ICMP packet and do nothing if the host is unreachable, instead of marking the address as if a valid response was received. Bad_Address flagging is part of the Duplicate IP Detection feature added to Windows NT 4.0 in Service Pack 2. CAUSE Bad_Address indications are being caused by a Windows for Workgroups 3.11 bug that occurs when all of the following conditions are present: Windows for Workgroups 3.11b clients are present on the network. At least two DHCP servers are present on the network, and at least one of them has Duplicate IP Address Detection enabled. The DHCP servers are separated from the Windows for Workgroups clients by a router. The router has ARP cache enabled. The router has the BOOTP relay agent enabled. The DHCP server receives a "Destination Host Unreachable" packet as a result of the client bug and the behavior of DHCP's Duplicate Address Detection. By current design, DHCP marks the IP address as BAD_ADDRESS if there is ANY response to ICMP echo request. RESOLUTION To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack WORKAROUND You can work around this problem by doing one of the following: Upgrade all WFWG clients to Windows 95 or Windows NT clients. -or- Disable the ARP cache on the CISCO router. (ARP cache is enabled by default on most routers.) STATUS Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. MORE INFORMATION The problem occurs in the following scenario: The Windows for Workgroups client broadcasts an IP address request (a DhcpDiscover packet) to the two DHCP servers. The first DHCP server responds to the request and assigns an IP address to the client through the normal sequence of DHCP handshaking between it and the client. The client binds to the given IP address. As part of Duplicate IP Address Detection , the second DHCP server sends an ICMP echo packet to the IP address it is attempting to assign (that is, the next available address in its pool). This is to confirm that the address is not already in use. Because the router has ARP cache enabled, it associates the media access control address of the Windows for Workgroups client to the IP address already assigned to the client from the first DHCP server. It then sends the ICMP echo packet to the media access control address of the Windows for Workgroups client. The client receives the packet, but the packet contains a different IP address (the one from the second DHCP server) than the one it has bound to its stack. Because of this address discrepancy, it responds back to the server with "Destination Host Unreachable". When the second DHCP server with Duplicate Address Detection receives an ICMP error response "Host Unreachable". The Error code is set to IP_DEST_HOST_UNREACHABLE.