11-17-2013 06:56 PM
Microsoft DHCP will mark any lease or reservation as BAD_ADDRESS if it detects an IP conflict on the network. I guess the first thing I would ask is if you can give us a little information about what your environment looks like.
11-17-2013 08:06 PM
noticed wifi user connection issue, checked dhcp and two scopes out of 17 for that ssid shows full, lease details shows too many BAD-ADDRESS, lease time is 15 mins, even then those bad address lease time doesnt match with this setting.
11-18-2013 12:15 AM
Am I right in assuming this is DHCP on a Microsoft server, rather than something different?
If so, can you please post a screenshot of the entries you're seeing?
There can be a number of reasons why this might occur. The following is an example.
Can you also confirm if there is a DHCP relay/helper in the client VLANs? I would imagine there is? What is it? I've seen some IP routing devices corrupt DHCP relayed messages before.
Depending on what the above reveals, the next best step might be to run a sniffer on the server to watch the DHCP requests coming in and replies out. That will almost certainly identify root cause.