none
Secure Wi-Fi Connection Issues

    Question

  • I've successfully installed Windows 8 Release Preview on my Build Conference Samsung Tablet PC.  It works really well. 

    However, I do have a problem trying to connect to a secure Wi-Fi network.  I can connect to an unsecure Wi-Fi network with out any issue.  I'm trying to connect to a Wi-Fi network that requires the following:

    • Security Type: WPA2-Enterprise
    • Encryption Type: AES
    • Network AUthentication Method: Microsoft: Protected EAP (PEAP)

    The Wi-Fi card and driver on this device is:

    • Device: Option GTM67x PCIe WiFi Adapter
    • Driver Provider: Microsoft
    • Driver Date: 3/22/2012
    • Driver Version: 3.0.0.128
    • Digital Signer: Microsoft Windows
    • Provider: Qualcomm Atheros Communications, Inc.

    Has eanyone experienced the same problem and does anyone has a solution?

    Thanks,

    Bob

    Friday, June 08, 2012 5:48 PM

Answers

  • This is a known issue with Cisco access points. Microsoft is working with Cisco to fix their firmware. The issue revolves around the fact that Windows 8 will support 801.11w, and there is a bug in the Cisco firmware which causes connections to fail. 

    In the mean time you can solve this issue by installing version v9.2.0.474 which can be found on the Atheros websiteThe site is hard to navigate. I suggest searching for "9.2.0.474". Then the "click for download" button. A new page opens and you'll just need to wait for 15 seconds for the download to present itself.

    The driver doesn't come with an installer, so you'll need to open the device manager and choose update driver on the wifi adapter. navigate to the folder where you extracted the driver to let it install it. Afterwards Windows Update will attempt to reinstall the 3.0.0.x driver version. Hide the update to prevent it from installing the Windows 8 driver.

    This driver is a Windows 7 driver and it does not support 801.11w, thus it does not trigger the issue.


    My blog: blog.jessehouwing.nl

    • Marked as answer by Bob Elward Friday, June 08, 2012 9:16 PM
    Friday, June 08, 2012 8:12 PM
  • Jesse,

    Thank you.  This did the trick.  It was a little difficult to get the right location to download the drivers.  Here the link to the location that I used so other can find it easily:

    http://download2.dvd-driver.cz/atheros/drivers/ar5xxx/win7-9.2.0.474-whql.zip

    Thanks again,

    Bob

    • Marked as answer by Bob Elward Friday, June 08, 2012 9:11 PM
    Friday, June 08, 2012 9:10 PM

All replies

  • This is a known issue with Cisco access points. Microsoft is working with Cisco to fix their firmware. The issue revolves around the fact that Windows 8 will support 801.11w, and there is a bug in the Cisco firmware which causes connections to fail. 

    In the mean time you can solve this issue by installing version v9.2.0.474 which can be found on the Atheros websiteThe site is hard to navigate. I suggest searching for "9.2.0.474". Then the "click for download" button. A new page opens and you'll just need to wait for 15 seconds for the download to present itself.

    The driver doesn't come with an installer, so you'll need to open the device manager and choose update driver on the wifi adapter. navigate to the folder where you extracted the driver to let it install it. Afterwards Windows Update will attempt to reinstall the 3.0.0.x driver version. Hide the update to prevent it from installing the Windows 8 driver.

    This driver is a Windows 7 driver and it does not support 801.11w, thus it does not trigger the issue.


    My blog: blog.jessehouwing.nl

    • Marked as answer by Bob Elward Friday, June 08, 2012 9:16 PM
    Friday, June 08, 2012 8:12 PM
  • Jesse,

    Thank you.  This did the trick.  It was a little difficult to get the right location to download the drivers.  Here the link to the location that I used so other can find it easily:

    http://download2.dvd-driver.cz/atheros/drivers/ar5xxx/win7-9.2.0.474-whql.zip

    Thanks again,

    Bob

    • Marked as answer by Bob Elward Friday, June 08, 2012 9:11 PM
    Friday, June 08, 2012 9:10 PM
  • Is Cisco aware of this issue and are they aware that it is their bug?  I recently opened up a tac case on this issue and their response was that they had previously identified/analyzed the issue and concluded that it wasn't their issue.
    Monday, June 11, 2012 5:54 PM
  • I can't say. I know microsoft is tracking the issue and from what I've heard so far the issue only exists with Cisco Access Points.  I don't have more specifics. Except what was shared with me, this can share:

    The reason I ask is that we’re currently tracking an issue of Cisco APs interoperating with Win8 Wi-Fi Drivers that support 802.11w, which is a management frame protection support amendment to the 802.11 spec. The interoperability issue prevents the OS from connecting to Cisco APs.

    We have only observed the issue with Cisco APs, so if you have any non-Cisco APs in your enterprise deployment, you should be able to connect to them.


    My blog: blog.jessehouwing.nl

    Monday, June 11, 2012 6:20 PM
  • Unfortunately, that driver is an unsigned driver and you need to boot Windows into the startup mode that allows you to run unsigned drivers (link below).  I'm running Release Preview on a Samsung Series 7 Slate (3G model).  Initiating the mode for running unsigned drivers required an external USB keyboard so you can press the correct boot option (This is ridiculous for a tablet! Am I missing something?).  The worst part of this is that you have only temporarily allowed use of that unsigned driver because when you reboot for any reason (e.g. Windows updates) you boot back into “standard” Windows and the unsigned driver won’t load!

    http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/how-to-install-unsigned-driver-on-windows-8/fd19f3b1-ac35-4aa0-84c0-58b66b382d43

     

    Thursday, July 12, 2012 2:40 PM
  • As far as I can tell this driver is properly signed. At least it's installed like any other driver on my machine without any issues.

    My blog: blog.jessehouwing.nl

    Thursday, July 12, 2012 6:00 PM
  • Full brief from Cisco:

    Hi all,

    I wanted to pre-advise colleagues in advance of a formal Field Notice coming out shortly that a serious software bug exists in all Cisco centralised wireless controller versions which support pre-standard Management Frame Protection (MFP) that will render Windows 8 devices completely unable to connect to Cisco APs under centralised control, with no easy workaround.

    This will affect every institution on the list using Cisco centralised wireless so I hope the non-Cisco colleagues won't mind this broadcast as it's quite important to avoid clients starting to pop up that can't connect for no apparent reason. Cisco has asked every employee, every partner and every other contractor we have a relationship with to proactively reach out to our/their customers to advise of this problem - so you might hear this twice or more from various contacts / lists / sources over the coming weeks.

    Problem: Microsoft Windows 8, to be released on October 26th, is among the first clients to support IEEE 802.11w natively in the OS. Clients running 802.11w fail to connect to Cisco's MFP capable APs because of interoperability issues in the service capability negotiation. It is /not/ possible to address this by simply disabling MFP on the Cisco Infrastructure, and Microsoft confirm that Windows 8 does not provide any way (e.g., RegKey, Group Policy) to turn off 802.11w as it is considered a positive feature to always have turned on for security purposes. The Cisco bug ID tracking this is CSCua29504.

    Solution: The only two solutions are:
    1. Update the Controller code to a fixed version.
    2. Downgrade to a pre-Windows 8 wireless NIC driver on the client device - where that option is available - as 802.11w is NIC driver and/or supplicant dependant. The only allowance Windows 8 makes is to not enforce 802.11w on pre-Windows 8 driver sets which will not work with most vendors' NICs otherwise. Clearly, the support implications of advising end users to do this will not scale, will not work indefinitely, and Cisco is not relying on this option as any kind of sustainable or permanent workaround.

    The plan is to patch the bug so that Windows 8 and other 802.11w capable clients can connect to Cisco infrastructure on the 7.0 code train (Early September), 7.2 code train (Late September) and 7.3 first release code train (Available by the end of August).

    This fix does not implement 802.11w but instead ensures that the communication from 802.11w enabled clients is interpreted correctly by the Access Point. There are no plans to patch this on the 5.0, 5.1, 5.2, 6.0 and 7.1 code-trains which have passed their End of Software Maintenance (EoSM) or End of Life (EoL) dates, and so 7.0 is the minimum release to move to if still running <=7.0 and needing the fix; and 7.2 if running 7.1. This issue does not affect version 4.2 and previous.

    Finally, the IEEE standard version of MFP - 802.11w (called Protected Management Frames - PMF) - will be supported in 7.4 (early Q1 2013).

    For now, I would advise scheduling a software upgrade window on your Cisco controllers ready for when the fixed code versions are released (if not wishing, or not able due to controller model, to adopt 7.3 soon). This will avoid a flurry of user support cases coming in the day they start arriving on campus with Windows 8 devices on or soon after launch. The route to obtain the fixed software versions is via your normal support channel.

    It goes without saying that this is a deeply unfortunate situation to have arisen, but I hope you won't shoot the messenger! :-) As bugs go this is right up there as quite a stunner. I expect to be quite busy over the next few months across Public Sector as this ripples out to customers who have not been reachable in advance for whatever reason.

    Please feel free to share this as widely as possible with any colleagues or other institutions you believe would be interested that are not on this list.

    Regards,
    Paul
    --
    Paul A. Hill CCDP, CCNP Wireless, CWNP Inc. CWDP & CWSP
    Head of Wireless Technologies, Public Sector UK

    Cisco Systems Ltd. E-mail: phill@cisco.com
    10 New Square Direct Tel: +44 (0)20 8824 8534
    Bedfont Lakes Direct Fax: +44 (0)20 7900 2337
    Feltham Mobile *: As Direct Telephone
    Middlesex Main Tel: +44 (0)20 8824 1000
    TW14 8HA Main Fax: +44 (0)20 8824 1001
    United Kingdom Voicemail: 844 48534
    * Single Number Reach rings all of my contact devices simultaneously.

    Cisco Systems Limited (Company Number: 02558939), is registered in England and Wales with its registered office at 1 Callaghan Square, Cardiff, South Glamorgan CF10 5BT.


    My blog: blog.jessehouwing.nl

    Monday, October 08, 2012 12:47 PM
  • This is a known issue with Cisco access points. Microsoft is working with Cisco to fix their firmware. The issue revolves around the fact that Windows 8 will support 801.11w, and there is a bug in the Cisco firmware which causes connections to fail. 

    In the mean time you can solve this issue by installing version v9.2.0.474 which can be found on the Atheros websiteThe site is hard to navigate. I suggest searching for "9.2.0.474". Then the "click for download" button. A new page opens and you'll just need to wait for 15 seconds for the download to present itself.

    The driver doesn't come with an installer, so you'll need to open the device manager and choose update driver on the wifi adapter. navigate to the folder where you extracted the driver to let it install it. Afterwards Windows Update will attempt to reinstall the 3.0.0.x driver version. Hide the update to prevent it from installing the Windows 8 driver.

    This driver is a Windows 7 driver and it does not support 801.11w, thus it does not trigger the issue.


    My blog: blog.jessehouwing.nl

    Hi Jesse,

    within the version v9.2.0.474 package, there are several drivers, which one are we to use? 

    my notebook said the adapter is intel centrino advance n 6235, but there is no exact match. 

    which one do we supposed to use?

    thanks.

    Friday, January 10, 2014 11:11 AM
  • That Intel chipset doesn't need these drivers. You need to download the latest drivers from Intel.

    My blog: blog.jessehouwing.nl

    Friday, January 10, 2014 12:45 PM