2504 was on 8.3, and 8.5. I'm trying 8.8.125 on the 3504. I haven't heard if the problem went away or not. ... View more

This is very similar to an issue I have in our foreign offices. We have 2504's and Cap2602I,s but updating to 3504's to hopefully fix the issue.   We seem to see the same issue with Intel wireless. A device seems to be connected, but can't go anywhere and can last up to 2 hours. It's extremely random and hard to recreate, but I was able to get it to happen a couple times to a test device. From packet captures and debugs, I can see it being a ping/DHCP issue. It seems that Intel devices ping the default gateway every few seconds. I think this is to detect a vlan change cause if it misses 5 pings, it kicks off DHCP. Now, what I saw is the WLC sent the request, and got the response from the DHCP server, but a packet capture on the device showed no response from the server and if you do ipconfig, you should see the computer with a default 169 address. I worked with TAC on this and they blamed it on Intel and closed the case.   A month or so down the road, I got it to happen again, and this time had a sniffer to see the wireless traffic. I could see the DHCP response on the WLC, but the sniffer was not seeing the packet being broadcast, so it proved it's a Cisco issue.   It also seems to be with 802.1x or higher auth as a hotspot with a psk never had the issue.   My downside is out support lapsed as we are upgrading to 3504's, so I can't open another ticket until I see the same issue on the new controllers. We had the issue on 8.5 code, and I was hoping the 8.8 code had fixed it. The weird issue is I have never seen it in our main facilities, but we have 2802's and 4800's in those, so may be with the older APs. ... View more