Question Locked

Bad Addresses in DHCP keep coming back

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello. This problem has been bugging me for the last few months and I can't seem to find any good info on why I am getting this problem or how to fix it. Here is the problem:
We have 3 Domain Controllers, 2 of which are DHCP servers, all running Server 2003 SP-2 Standard Ed. Both DHCP servers have a range from 192.168.2.1 to 192.168.3.254. Server A has excludes addresses 2.1 through 3.0. Server B excludes addresses 3.0 through 3.254. We also have about 140 DHCP reservations for certain PCs on the network. We have been seeing a number of reservations turn to "BAD_ADDRESS" and we are left to recreate the reservation. Any thoughts?

8 replies

by shasca

Any known DNS issues? what is the lease duration?

Cause: The client running Windows 98, Windows Millennium Edition, or Windows XP could not find a DHCP server and has used IP autoconfiguration to configure its IP address.
In some larger networks, disabling IP autoconfiguration might be desirable for network administration.

Solution: First, use the ping command to test connectivity from the client to the server. Your next step would be to either verify or manually attempt to renew the client lease. Depending on your network requirements, it might be necessary to disable IP autoconfiguration at the client. You can learn more about IP autoconfiguration and how it works prior to making this decision

To reconcile a scope
Open DHCP.

In the console tree, click the applicable scope.
Where?

DHCP/applicable DHCP server/applicable superscope (if used)/applicable scope

On the Action menu, click Reconcile.

In the Reconcile dialog box, click Verify.
Inconsistencies found are reported in the status window.

If the scope is found to be consistent, click OK.
If the scope is not consistent, select the displayed addresses that need to be reconciled, and click Reconcile to repair inconsistencies.

another on leases-http://technet.microsoft.com/en-us/library/cc780476.aspx

Hope there is something in here of use. Let us know.

by chris.aug

I check the event logs of our Domain Controllers and Exchange on almost a daily basis. All event logs are blue. The Lease duration is set to 3 days. Although I never have seen a BAD_ADDRESS on a non-reservation address. It is always an address I have a DHCP reservation for.
I'll try the scope reconcile and see what it tells me. Thanks.

EDIT: No problems with the reconcile. The scope database is consistent on both servers.

by shasca

Has this system previously worked fine? For how long? Any network upgrades in between?

What if any events show on a PC that received the address error?

too add
DHCP Service logs startup and shutdown events in the Event Viewer. You can enable detailed monitoring logs:
Right-click the DHCP server in the DHCP Administration Tool
Click Properties
On the General tab, click Enable DHCP Audit Logging
This will create a log file winnt\system32\dhcp\DhcpSrvLog.xxx.

by chris.aug

I checked out the link. To bad they didn't resolve the problem. Thanks though.

by chris.aug

We haven't been having any problems for years. This BAD_ADDRESS problem just started out of the blue a few months ago and we hadn't made any changes back then. Recently we upgraded our Domain Controllers to SP-2 (we thought it might fix this issue but it didn't).

I had DHCP logging on. Here is a clip of the logs that record the error. Anyone able to decipher what's happening?

30,04/21/09,01:14:15,DNS Update Request,91.3.168.192,NMS727.NMSLAB.local,,
13,04/21/09,01:14:15,Conflict,192.168.3.91,BAD_ADDRESS,,
32,04/21/09,01:14:15,DNS Update Successful,192.168.3.91,NMS727.NMSLAB.local,,
30,04/21/09,01:14:25,DNS Update Request,91.3.168.192,BAD_ADDRESS,,
15,04/21/09,01:14:25,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
32,04/21/09,01:14:25,DNS Update Successful,192.168.3.91,BAD_ADDRESS,,
15,04/21/09,01:14:26,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:27,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:28,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:29,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:30,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:31,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:32,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:33,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:34,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:35,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:36,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:37,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:38,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:39,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:40,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:41,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:42,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,

by shasca

(Conflict,192.168.3.91)from log

"Server B excludes addresses 3.0 through 3.254" from original post

What is the reasoning behind the exclusions. Static Ip's?

It's possible one on server b isn't applying properly

See if the bad addresses are of a specific IP range.(i.e.3.0-3.254)

This discussion is closed to new replies.