03-09-2015 09:21 AM
When we turn on wired and or wireless containment on our IAP's our MS DHCP scopes generate "bad addresses". Once the bad addresses start they don't stop and can fill a scope pretty quickly and prevent wireless clients from connecting. On one occasion we've traced this back to a Mac client running in bridged mode but most of the time we can't determine the cause. The only way to get around this to turn off both wired and wireless containment which we obviously don't want to do.
Wondering if anyone else has experienced this or knows what would cause this.
03-10-2015 09:53 AM
spent some more time troubleshooting this it appears we only have the DHCP "bad address" issue when wired containment is on. We have over 100 IAPS sites and we've experienced this system at, at least 20 different sites (three alone this week).
We're running 220.127.116.11-18.104.22.168_46028 on all our IAPS.