Yes! It works!
To recap : My laptop has an Atheros AR9002WB-1NG adapter, windows 8.1. Even when it had windows 8, it was unable to connect, but unlike now, I didn't look closely enough about the type of network. Originally I thought it was
this problem. But they confirmed that others with windows 8 had no issues with this. Then , when I tried configuring the network manually, I could not find the WPA-enterprise option at all, only the
So here I was, and Greg Seth's answer gave me an idea.
In the following instructions, some commands are obvious, so I won't explain unless necessary. So here's what you do :
0) Go to command line, preferably Administrator (not tried without).
1) C:\Windows\System32> cd \Users\<User>\Documents
2) C:\Users\<User>\Documents> netsh
3) netsh> wlan
4) netsh wlan> show profiles
5) delete profile name=<yournetwork>
Enclose the name of network within quotes, this is to ensure that you can cleanly set up the right profile. Don't close the netsh, we'll need it some more. If you do, just reach there the same way as before.
6) Right click the connection icon in lower right corner > open Network and Sharing Center > Set up a new connection or network > Manually connect to a wireless network
7) Try to create a profile, and try to get as many details to correspond with your requirement. The rest we'll edit in command line, so let's make it as easy as possible.
8) Do the same at the next screen. Edit Network settings > change all the parameters that you can, to match the requirement. My university tech support has a detailed document listing the options to choose, usually for windows 7, or even windows 8. get
as many of them as possible.
9) Finish. Move back to your netsh terminal
10) netsh wlan> show profile <profilename>
without quotes this time. This should show your previous attempt at creating a profile in the GUI dialog boxes. In my case, it had WPA2 and AES. It has to become WPA and TKIP. I also set my authMode to userOnly, since I hadn't done it right in the dialog box
11) netsh wlan> set profileparameter
displays a humongous list of parameters with detailed options, just carefully examine the syntax. It's all here.
12) netsh wlan> set profileparameter name=<profilename> authentication=wpa encryption=tkip authMode=userOnly
13) netsh wlan> set profileparameter
Don't exit this yet.
14) Now click the connection icon, and connect to the network. It will ask you the username and password in a different style, that was my clue something was different this time.
15) It should connect. In my case atleast, it did. Verify by browsing.
16) netsh wlan> export profile name=<profile name>
In order that you're not put through this ordeal again, export the profile safely to a file. Again, the profile name in quotes.
17) Wonder why microsoft makes things difficult for us!
Proposed as answer by
Thursday, October 24, 2013 1:27 PM
Marked as answer by
Kate LiMicrosoft contingent staff, Moderator
Tuesday, November 05, 2013 9:45 AM