I realize this in a old thread but it fits exactly what issue i'm having as well. Just like the first poster mentioned my dhcp server scope is being flooded with requests. Every 10-12 seconds a new one labeled BAD_ADDRESS. The unique id is very similar. They all end with 02010a. In my case i know exactly what's causing it I'm just not sure why.
I have a Windows 8 virtual machine running on my laptop. The virtual network adapter for that virtual machine (guest) is set to bridged mode. It continually tries to pull an IP address from my dhcp server but never actually gets internet nor lan access. Even with a static IP address my guest machine can't access the network. The MAC address for the guest machine ends in 2e112f which isn't anywhere close to what the dhcp server is reporting. If i switch my guest machine's network adapter back to nat instead of bridged it works just fine.
-DHCP server in running on Windows 2008 R2.
-Host machine is running Windows 7 Pro
-Guest machine is Windows 8 Pro x64, ipv6 disabled
-Vmware Workstation 9
-Virtual Network configuration is set to auto bridge with my wireless and wired adapters selected.
If the host machine is accessing my network via wireless ap the problem presists. If I switch to a wired connection my Windows 8 guest machine works as expected. The strange thing about all of this is i have other virtual machines (Win7, Ubuntu 12, WinXP, Debian) that work fine via wireless and virtual bridge. Only the windows 8 guest seems to act up.
Maybe someone can shed some light on this. Its nice to know what other types of devices I need to look for that can cause BAD_ADDRESS on my dhcp server. Add virtual machine with a bridged network adapter over a wireless connection to that list.