We have an internal 5508 controller that has two SSID's on it. A secure SSID which uses an ACS server to authenticate users through AD, and a guest SSID which tunnels out to a DMZ 5508 anchor controller. The guest users have no issues at all. We upgraded our controllers to 7.6.100.0 about 3 weeks ago. Since then, we've had an issue with the data path, for the anchor controller was down, and would only come up after reboot of the internal controller. That was the 1st issue. Over the past few days, I've had users from all over the country tell me that they cannot get connected to our secure network. All users have Win7 machines. All they see is the yell yield sign, on their wireless connection. In the Network and Sharing center, they see the wireless network listed as an unidentified network (public network). In the ACS, the users are authenticating with no problem (I can see it in the ACS logs), and they do receive an IP address. However, they have absolutely no connectivity. I have them try to ping the default gateway, of the subnet that they're assigned, and it comes back with request timed out. Of course they can't get to the internet, or do anything, since they have no connectivity back to their gateway. I've restarted the internal controller (thinking that there must be a hang like with the data path anchor issue) which didn't work, I've blown away the SSID, and recreated it. That didn't work. I even restarted the ACS, although that wasn't an issue. It seems like any users that were connected, prior to the issue, and have no shut down their pc, are ok. Users that have shut down, or have removed the secure wireless network profile, from their computer, can no longer connect. They just get that the network is unidentified. I'm not sure if there was any sort of Win7 update, or some other push, but I want to make sure that from the WLC perspective, there's no issue. Thanks for any help!
