Can't create a WPA2-Enterprise wireless connection; missing Microsoft: PEAP

Answered Can't create a WPA2-Enterprise wireless connection; missing Microsoft: PEAP

  • Tuesday, May 24, 2011 11:23 PM
     
     

    OS: Windows 7 64-bit Enterprise
    Hardware: Lenovo T410S w/Intel 5300 ABGN Wireless

    If I try to build the wireless connection manually and choose WPA2-Enterprise, then click next, I get 'An unexpected error occurred.' and no options to configure; just close.

    I then tried to create a Preshared Key WPA2 connection. This worked fine. When I go to edit the connection, I have the ability to select the WPA2-Enterprise options, however in the list of Network Authentication methods (under Security Tab), I don't have the Microsoft: PEAP or SmartCard options. I only have Cisco: LEAP,PEAP,EAP-FAST and Intel: EAP-SIM,EAP-TTLS,EAP-AKA (6 entries).

    It's my theory that because the Microsoft options are missing, the wizard gets the unexpected error. I'm wondering how I get the MS ones back.

     

All Replies

  • Wednesday, May 25, 2011 9:18 AM
    Moderator
     
     Answered

    Hi,

     

    Thanks for posting in Microsoft TechNet forums.

     

    Do you have Symantec installed? It is said the issue could be due to conflict with Symantec Endpoint Protection. Please uninstall\reinstall Symantec if it is there.

     

    Best Regards

    Magon Liu

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked As Answer by AR5 Wednesday, May 25, 2011 4:46 PM
    •  
  • Wednesday, May 25, 2011 4:45 PM
     
     
    That was it! Wow. Thank you very much!
  • Monday, July 25, 2011 10:35 PM
     
     
    That worked for me too!!!  Thanks
  • Sunday, February 10, 2013 6:51 PM
     
     Proposed

    Actually, there's MS article dealing with this problem:

    http://support.microsoft.com/kb/2699785

    • Proposed As Answer by Algil Sunday, February 10, 2013 6:51 PM
    •