I don't know if this is the same kind of problem we experienced. We had an issue with newer Intel Centrino Wireless Chipset and Windows 8 running version 10.5.x. As soon as clients upgraded to 10.5.x ( I have not tried version 10.6.1 yet), it would not even see our SSID or had problems maintaining a connection. What we had to do was revert back to the original drivers that came with the laptops.
I have a Windows 8 Pro Surface with a Marvell Avastar 350N chipset running version 14.69.17060.83 without a problem on our corporate Wi-Fi network (Aruba). Edward Ip | ITS | Wireless Systems Administrator 613 727 4723 | ext 7112 Algonquin College | 1385 Woodroffe Avenue | Room C316 | Ottawa | Ontario | K2G 1V8 | Canada algonquincollege.com -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Zeller, Tom S Sent: Wednesday, April 24, 2013 5:23 PM To: [email protected] Subject: [WIRELESS-LAN] Microsoft Surface WiFi issue I'm no longer directly involved in the WiFi here, but I was helping someone with a Microsoft Surface (Intel version) that is perfectly up-to-date. My Mac Air WiFi worked perfectly with our Aruba AP throughout the exercise. His would connect, get DHCP, get a lease renewal in five min (ten min lease) and a few minutes later Windows would tell him he had "limited" Internet, but in fact he could only ping his own IP and not the router (that's pretty limited!). The WiFi bars icon never wavered. I'm suspecting a failure to renegotiate keys. Anyone else seeing Surface WiFi issues? Tom Zeller Senior Technology Analyst Indiana University [email protected] (812) 855-6214 > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. -- ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
