on 11-20-2013 11:38 AM
Hello again all:
We are starting to see an increase in number of clients reporting they are frequently being dropped or cannot connect to our wireless network recently after it had been working for quite awhile (since start of our semester), and so far it appears to be occuring with our Windows 8 users who upgraded to version 8.1. The wierd part is they cannot connect in some locations (they usually report it is their room) but in other locations they do connect fine. We do have a mixture of AP-125 and AP-135 APs on campus and even within a building in some cases, so we are just now trying to correlate to see if it is just a certain combination of Windows 8.1 and an AP-125 or AP-135 that is not working for them. But thought I would throw it out on this forum and see if we are the only ones seeing this phenomenon. Thanks in advance for any ideas you might have troubleshooting this or can give us any feedback if you have experienced this as well.
on 11-20-2013 11:54 AM
We had/have an issue with windows 8/8.1; It sounds similar to yours, on our 802.1x network eduroam users were connecting and then dropping and having difficulty getting online. A symptom was that they were often asked to re-enter credentials.
The solution was to DISABLE 'Enable Pairwise Master Key (PMK) caching.
This is found in the wlan network properties, security tab, advanced settings, new window 802.11 settings.
on 11-20-2013 12:05 PM
We had similar behavior. All of he affected clients were Windows 8. We would have individual clients that could not connect to an AP but could walk to another floor or building and connect just fine. We would reboot the AP they should be connecting to and they would then be able to connect. We spent a lot of time working on the issue. Two weeks ago upgraded to 220.127.116.11 and so far we have not see the issue return. Our environment is primarily 104's and 105's.
on 11-20-2013 12:14 PM
If possible, update to 18.104.22.168. There were some bugs in earlier 6.3 versions affecting AP-125s. The APs would eventually run out of memory and either reboot or just stop accepting clients.
Rebooting the APs temporarily restored service, but the better fix is to upgrade.
on 12-12-2013 03:29 PM
on 12-12-2013 07:59 PM
Good to know. We had a few reports of some WIn8 cients earler in the semester. One solution that appeared to have helped was to disable the 802.11n mode in the client or "downgrade" to a previous driver version (15.x). Advising users to simply upgrade to the lastest driver is always preferred over tweaking client settings.