Windows Server 2003
1819832 Members
2855 Online
109607 Solutions
New Discussion юеВ

Re: DHCP Server BAD_ADDRESS

 
SOLVED
Go to solution
Tim Willett
Occasional Contributor

DHCP Server BAD_ADDRESS

Good Morning, I have a strange problem and was wondering if someone else had this issue. We recently migrated from a Netware 6.5 DHCP Server to 2 Windows 2003 DHCP Servers. From the very first day the subnet where all of our servers live would be flooded with BAD_Address in the scope until they would finally run out of addresses. I would delete all of the bad addresses and they would all be back by the next day. I looked at the logs and it seemed like alll of the ILO ports were reporting all of these addresses as being in use to the dhcp server and would cause them to be marked as bad_address. I have un-plugged all of the ILO ports on the network and there are no more bad_address in the scopes on the dhcp servers. All of these cards had address assigned by the DHCP Server I could see them in the scope. Does anyone have any suggestions on how I might resolve this?

Thanks

Tim
3 REPLIES 3
Oren Maoz
Respected Contributor
Solution

Re: DHCP Server BAD_ADDRESS

Hi Tim,

make sure IP addresses assigned to iLo ports are not part of the scope in your DHCP server.
if they are change the scope or exclude those addresses
Tim Willett
Occasional Contributor

Re: DHCP Server BAD_ADDRESS

That is actually a really good idea. Here is an update, After going thru the logs better, I realized it was 1 ILO card not all of them. I have all cards plugged back in except the faulty one and everything seems to be fine. No more bad addresses on the DHCP server. NOt sure what is wrong with the card yet, but one is better than all of them.

Thanks for the recommendation

Tim
Tim Willett
Occasional Contributor

Re: DHCP Server BAD_ADDRESS

I have located the faulty card. I am either gonna fix it or leave it off the Network. May just assign an IP and be done with it.

Thanks again