954,323 Members — Technology Publication meets Social Media
Username:
Password:
Lost login information?
Have something to say? Contribute New Article Reply to this Article

DHCP Server: BAD_ADDRESS

I have DHCP installed on our server, and while checking the leases I noticed a few BAD_ADDRESS entries. I delete them but they return within a few seconds. Anyone know the cause of this and how to prevent it?


Thanks!

Duki
Nearly a Posting Virtuoso
1,475 posts since Jun 2006
Reputation Points: 817
Solved Threads: 32
 

Can you trace the bad adress to any workstations?:?:
How many workstations do you have?:?:
How many can you see in the DHCP list?:?:
Do workstation addresses match those in the DHCP list?:?:
Are all the workstations set to DHCP?:?:

Do they have all the correct subnet masks?

These are all things you should check.

knsljo
Junior Poster
167 posts since Jul 2006
Reputation Points: 11
Solved Threads: 8
 
Can you trace the bad adress to any workstations?:?: How many workstations do you have?:?: How many can you see in the DHCP list?:?: Do workstation addresses match those in the DHCP list?:?: Are all the workstations set to DHCP?:?: Do they have all the correct subnet masks? These are all things you should check.


Can't trace the addresses
roughly 25
(random)
from what i can tell
no (we're in the process of switching over to new network architechture)
yes

Duki
Nearly a Posting Virtuoso
1,475 posts since Jun 2006
Reputation Points: 817
Solved Threads: 32
 

You need to check this when all DHCP configured machines are running.
Take a note of all there ip addresses and cross reference it with the DHCP list.
The machines that are not configured with DHCP could have static ip addresses that conflict with addresses that are issued by DHCP. If they are on the same network and they are switched on after a workstation which has been issued with the same ip address they will conflict. You need to make sure that the DHCP server cannot issue any of the static ip addresses.
eg: set DHCP to issue 192.168.1.100-192.168.1.150 then set all static addresses outside of this range.
This is just one possibility.
Hope this helps.

knsljo
Junior Poster
167 posts since Jul 2006
Reputation Points: 11
Solved Threads: 8
 

thanks for the reply.


all of our static ips are 13.240.x.x and the dhcp is set to lease 192.168.x.x

Duki
Nearly a Posting Virtuoso
1,475 posts since Jun 2006
Reputation Points: 817
Solved Threads: 32
 

Well I figure it's about time to bring this post back to life.... :sad:


I'm still getting a bunch of BAD_ADDRESS entries in my DHCP Address Lease scope. The MAC Address is shorter than the work stations'....

Duki
Nearly a Posting Virtuoso
1,475 posts since Jun 2006
Reputation Points: 817
Solved Threads: 32
 

Moved.

'Stein
Lapsed Skeptic
Team Colleague
1,941 posts since Jan 2006
Reputation Points: 222
Solved Threads: 106
 

What do you mean with "Moved." ?

I have the same problem.
- bad_address
- shorter MAC

Duki, were you able to solve the problem ?

smisse
Newbie Poster
1 post since Nov 2007
Reputation Points: 10
Solved Threads: 0
 

Ive had this before when 2 machines had the same mac (dont know why, i thaught they were supposed to be unique to the h/w?)

jbennet
Moderator
Moderator
18,523 posts since Apr 2005
Reputation Points: 1,826
Solved Threads: 601
 

Well yes and no. We recently installed new servers, which do not give this error. I figure it was something configured wrong in DNS or DHCP on my behalf; it was my first DC.

Duki
Nearly a Posting Virtuoso
1,475 posts since Jun 2006
Reputation Points: 817
Solved Threads: 32
 

i've similar problem here is my sceanrio:

2003 - DHCP no DNS
BAD ADDRESS
Lesser MAC ID
no static IP from the client side.

still getting " BAD ADDRESS"

any help?

snpslm
Newbie Poster
1 post since Dec 2008
Reputation Points: 10
Solved Threads: 0
 

Same problem with MAC addresses and the all end in the same 6 characters and the first 2 are different. Only 8 characters in these MAC's

K2HAL
Newbie Poster
1 post since Jan 2010
Reputation Points: 10
Solved Threads: 0
 

Hi

I know this is an old thread but take a look at this: http://johntear.tumblr.com/post/17028050150/bad-address-entries-in-dhcp-database

A Windows DHCP client sends an ARP request when it receives an IP address from the server, if a host on the same broadcast domain responds the client sends a DHCP DECLINE to the server which results in the BAD ADDRESS entry.

In my case it was a Cisco firewall with proxy arp enabled.

Hope this helps.

marraboy
Newbie Poster
1 post since Feb 2012
Reputation Points: 10
Solved Threads: 0
 

This article has been dead for over three months

Post: Markdown Syntax: Formatting Help
You