Connect to WPA2-AES network

Hello,
I don't manage to connect my MBP to a WPA2 network with AES encryption which needs also protected EAP. In fact I don't even find an option about the encryption mode under Leopard.
If anyone has an idea about what steps I should try I would be very grateful.
Thank you in advance

I think your problem is using the "enterprise" login setting. Try using just WPA2 Personal or WPA Personal (NOT enterprise) when logging in wirelessly. Then just type in the passphrase and it should work.

Similar Messages

Unable to connect to a Wifi WPA2 AES network

Hello
I have an issue to connect to a Wireless WPA2 AES network. I am using an iPhone 4 with iOS 6.0.1
Is that a known issue?

IPhone 5 won't connect to WPA2 wireless network

I just got a new iPhone 5 from AT&T and it will not connect to my AT&T home wireless network. I keep getting "unable to join network "SSIDNAME". It has connected before but briefly before dropping the connection. When it does connect, the access is extremely slow. I see a thread on this issue and hope there is a fix soon.

I've rebooted the AT&T supplied wireless router which helped with the connectivity issue but when I do get connected, the Safari browsing is painlessly slow and I can't seem to get the full bandwidth potential as I did with my old iPhone. I'm returning my iPhone 5 to AT&T soon if this doesn't get resolved soon.

Cannt connect to WPA2-AES encrypted wifi

there is no issue with a WEP wifi. i googled this problem and none of them solved my problem. i updated IOS to 6.1.2. i reset my phone. however, it still does not work.
thanks in advance

Try http://archpi.dabase.com/#wireless. It worked like a charm for me with RPI2 + http://www.amazon.co.uk/Andoer-Wireless … B008IZQCGK which has the same chipset and it's using kernel module 'rt2x00' https://wireless.wiki.kernel.org/news/2011-07-22. USB ID: 148f:5370.
Last edited by phedoreanu (2015-04-25 22:35:28)

MAC OS 10.4.11 connecting to WPA2 Enterprise not permanently working

Hi,
I have an issue with the following environment. I will try to simply my wording to help understand the problem.
Hardware: Macbook Pro 17" Intel Core 2 Duo and Macbook laptops
Operating System: Both run MAC OS 10.4.11 fully updated (According to Apple Reps, this operating system is no longer supported)
Airport cards: Both have Airport Extreme cards. The Macbook Pro's card is using Firmware version 1.4.4 ( card type requirement to connect to WPA2 Enterprise network)
Connection type: Connected via PEAP (Inner Protocol:MSCHAPv2)
Wireless Access Point (WAP): Cisco Aironet 1142: Macbook connects to WAP to gain access to the Internet.
Cisco ACS version 5 server (validates macbook username and password entries to Microsoft AD servers.)
Microsoft Windows Server 2003 with Active Directory (holds user accounts)
Other Operating systems MAC OS 10.5 to MAC OS 10.7 (Leopard, Snow Leopard, and Lion make automatic connections.)
Basically, the process is that the macbook user enters in their email username and password into a WPA2 Enterprise wireless connection. The Cisco 1142 broadcasts the SSID for the user to connect to. Once the wireless connection is made to the Cisco 1142 WAP, the WAP sends the username and password to the ACS server. The ACS server verifies the username and password from the macbook to Microsoft Windows Server AD user accounts. If the password is validated, then the ACS grants access to the wireless Internet to the macbook user.
The wireless configuration involves the following process:
1. Click on the desktop, Go should be available now.
2. Click on Go, then Applications. The Applications window will appear.
3. Click on Internet Connect.
4. By default, The 802.1X connection is not available. We will be using the 802.1X connection to enter and save the username and password. Click on File and select "New 802.1X Connection."
5. A windows should appear. Under Configurations, select Edit Configurations.
6. An 802.1X windows will appear to enter in the following:
- Description: name of connection
- Network port: Airport
-User Name: domain\username or just username of email account
-password: password for email account
-Wireless Network: SSID of Cisco Aironet 1142 Wireless Access Point (WAP)
-Authentication PEAP configured with outer identity of anonymous. We uncheck TTLS, EAP-FAST, LEAP, and MD5.
7. Click Ok. Select Connect and it should connect to the SSID if the username and password are valid accounts.
8. Select File and then "Export 802.1X Configuration to login Window."
To verify connection:
1. We go to Apple - System Preferences and select Network.
2. The Airport should say that it is conected to the SSID. You are connected to the Internet via Airport.
3. Go a little deeper, we click on configure for the Airport.
4. Under By default join: select Preferred networks. Under network name, we should see the SSID connection. We select it and click on the edit button.
5. We verify that the connection has Network Name, Wireless Security, User Name, Password, and 802.1X Configuration entered in correctly. We select Ok after verification or modification. Then we select Apply Now to save any changes.
---------------------------------------------------------------The Problems---------------------------------------------------------------------
1. When shutting down the system and then turning it on. The Airport doesn't make a connecation to the SSID being broadcasted automatically. We would have to turn the airport off and back on for it to make an connection.
2. When the laptop is left idle or goes to sleep, the wireless connection drops. The user would have to turn the airport off and back on to stay connected.
Is there a fix for this?
Thank you to anyone that would take time to read this and provide helpful feedback.

The "v" key at startup is not Safe Mode. Try holding the Shift key down and restart for Safe Mode. This will disable extensions and help it start. It also checks some things out.
Can you start it up from your Tiger disc? Hold the C key down at startup until you see the Apple.
Your hard drive may be going kaput. Hope you have a good backup.

HP Wireless Printers cannot connect to WPA2-secured WiFi networks with Cisco/Meraki WAPs

In the last two months, I've had the displeasure of working with two very different HP printers and attempting to make them work on a WPA2-secured wireless network. All attempts to authenticate fail with "invalid phassphrase".
I'm not the first person to encounter this, it's a problem with many different HP wireless printers (I just happen to have physical access to the OfficeJet Pro 8610 & Deskjet 3511).
My equipment is a Cisco ASA 5505 Firewall running ASA 9.1x & Cisco Aironet 1142 running IOS 15.3.x.
What does work on the WPA2/AES SSID: Apple MacBook Air running OSX 10.10.2, Three Windows-Based laptops running Windows 8.1 Update 1, an iPhone 5s, Three Windows Phone 8.1 devices, Roku 2, PlayStation 4, PlayStation 3, Sharp Aquos TV, Amazon Streaming Stick, and an Android Tablet (Jellybean). Basically, everything.
What does not work on the WPA2 network: OfficeJet Pro 8610 & Deskjet 3511.
To test the theory there is a problem with HP's implementation of WPA2 with regard to Cisco Aironet IOS, I built out a second SSID that only works in WPA/TKIP mode. This solution works. Both HP printers will join the WPA/TKIP network.
So, I'm able to demonstrate there is a certain connectivity issue. When i look at AAA Debug on the WAP's console, I can observe the HPs attempt to authenticate "Bind I/F" on the WPA2 SSID, however they do not achieve authentication and do not pass the AAA phase. However, on the WPA SSID, they bind and authenticate successfully.
To help illustrate this, here is my WAP running config. It's about as simple as it can get. There is no relevant MAC filtering or ACLs bound to any interface. Noting that I have an ACL on remote access to the WAP (i.e. Locked down to SSH, disabling telnet). The main point being that the ASA firewall is not a factor in this problem as the issue is at the WAP before WPA2 authentication can complete, therefore the printers never reach the network / when the printers connect to the WPA network, the operate fully & correctly.
If anyone at HP can indicate why this particular config is somehow improper or broken, that would be fantastic. There should be no reason why Cisco / Meraki WAP owners have to lower wireless encryption standards just for a printer, be forced into wired, create separate SSIDs with lower encryption specifically for a device.
Building configuration...
Current configuration : 6064 bytes
! Last configuration change at 12:46:47 UTC Fri Aug 20 1993 by admin
version 15.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname 10-10-50-1
logging buffered 1024768
logging rate-limit console 9
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
no ip source-route
no ip cef
ip domain name freedom.local
dot11 syslog
dot11 vlan-name inside vlan 50
dot11 vlan-name inside-wpa-only vlan 70
dot11 ssid inside
   vlan 50
   band-select
   authentication open
   authentication key-management wpa version 2
   mbssid guest-mode
   wpa-psk ascii 7 xxxxxx
   information-element ssidl
dot11 ssid inside-wpa-only
   vlan 70
   band-select
   authentication open
   authentication key-management wpa
   mbssid guest-mode
   wpa-psk ascii 7 xxxxxx
   information-element ssidl
dot11 band-select parameters
   cycle-count 3
   cycle-threshold 200
   expire-supression 20
   expire-dual-band 60
   client-rssi 75
dot11 wpa handshake timeout 500
dot11 network-map
username ADMIN privilege 15 secret 5 xxxxxx
ip ssh version 2
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 50 mode ciphers aes-ccm
encryption vlan 70 mode ciphers aes-ccm tkip
ssid inside
ssid inside-wpa-only
antenna gain 0
mbssid
speed basic-1.0 basic-2.0 basic-5.5 basic-11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
channel 2412
station-role root
l2-filter bridge-group-acl
interface Dot11Radio0.50
encapsulation dot1Q 50 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.70
encapsulation dot1Q 70
no ip route-cache
bridge-group 70
bridge-group 70 subscriber-loop-control
bridge-group 70 input-address-list 700
bridge-group 70 output-address-list 700
bridge-group 70 spanning-disabled
bridge-group 70 block-unknown-source
no bridge-group 70 source-learning
no bridge-group 70 unicast-flooding
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.50
encapsulation dot1Q 50 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.70
encapsulation dot1Q 70
no ip route-cache
bridge-group 70
bridge-group 70 spanning-disabled
no bridge-group 70 source-learning
interface BVI1
mac-address xxxx.xxxx.xxxx
ip address 10.10.50.1 255.255.255.0
no ip route-cache
ip forward-protocol nd
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip route 0.0.0.0 0.0.0.0 10.10.50.2
logging history size 100
access-list 111 permit tcp any any neq telnet
bridge 1 route ip
line con 0
access-class 111 in
line vty 0 4
access-class 111 in
length 0
transport input ssh
line vty 5 15
access-class 111 in
transport input ssh
end

I get the same behavior with a laserjet m451nw. I need to enable tkip to get the printer working, it doesn't support pure aes-ccm (every other device here supports pure aes-ccm, even cheap ones), although it's advertised as working.
The following snippet of config works, but I still think it should work without the tkip "hack".
dot11 ssid whatever
vlan 1
band-select
authentication open
authentication key-management wpa version 2
interface Dot11Radio0
encryption vlan 1 mode ciphers aes-ccm tkip

WPA-TKIP WPA2-AES Connection speed

Hi,
My customer uses controller based wireless network. There is a connection speed problem between two SSID's. First SSID uses WPA(TKIP+AES) and WPA2(TKIP+AES) encryption method and dot1x authentication method. Second SSID uses open authentication (this is a guest SSID)
802.11 a/n/ac is enable on WLC and client can connect with these methods. But clients connect to the first SSID with 802.11 b/g (54 Mbps) and connect to the second SSID with 802.11 a/n/ac. Customer wants to know why our clients connect with low speed to first SSID even if a/n/ac is enable.
Sometimes WPA-TKIP encryption methods can reduce the connection speed. Do you have any idea about that and official document about this problem?
Thanks,
Burhan,

TKIP and AES are two different types of encryption that can be used by a Wi-Fi network. TKIP stands for “Temporal Key Integrity Protocol.” It was a stopgap encryption protocol introduced with WPA to replace the very-insecure WEP encryption at the time. TKIP is actually quite similar to WEP encryption. TKIP is no longer considered secure, and is now deprecated. In other words, you shouldn’t be using it.
AES stands for “Advanced Encryption Standard.” This was a more secure encryption protocol introduced with WPA2, which replaced the interim WPA standard. AES isn’t some creaky standard developed specifically for Wi-Fi networks; it’s a serious worldwide encryption standard that’s even been adopted by the US government. For example, when you encrypt a hard drive with TrueCrypt, it can use AES encryption for that. AES is generally considered quite secure, and the main weaknesses would be brute-force attacks (prevented by using a strong passphrase) and security weaknesses in other aspects of WPA2.
The “PSK” in both names stands for “pre-shared key” — the pre-shared key is generally your encryption passphrase. This distinguishes it from WPA-Enterprise, which uses a RADIUS server to hand out unique keys on larger corporate or government Wi-Fi networks.
In summary, TKIP is an older encryption standard used by the old WPA standard. AES is a newer Wi-Fi encryption solution used by the new-and-secure WPA2 standard. In theory, that’s the end of it. But, depending on your router, just choosing WPA2 may not be good enough.
While WPA2 is supposed to use AES for optimal security, it also has the option to use TKIP for backward compatibility with legacy devices. In such a state, devices that support WPA2 will connect with WPA2 and devices that support WPA will connect with WPA. So “WPA2″ doesn’t always mean WPA2-AES. However, on devices without a visible “TKIP” or “AES” option, WPA2 is generally synonymous with WPA2-AES.
WPA and TKIP compatability options can also slow your Wi-Fi network down. Many modern Wi-Fi routers that support 802.11n and newer, faster standards will slow down to 54mbps if you enable WPA or TKIP in their options. They do this to ensure they’re compatible with these older devices.
In comaprison, even 802.11n supports up to 300mbps — but, generally, only if you’re using WPA2 with AES. Theoretically, 802.11ac offers theoretical maximum speeds of 3.46 Gbps under optimum (read: perfect) conditions.
In other words, WPA and TKIP will slow a modern Wi-Fi network down. It’s not all about security!

Accept Certificate when connecting to an SSID with WPA2-AES encryption.

When I try to Connect my Iphone to an SSID with WPA2-AES encryption,i need to accept the certificate and gets authenticated.When i switchover to different SSID and reconnect again to the same WPA2-AES SSID i do not get the Certificate accept page.
When i click on the Forget Network and deisconnect from the SSID and re-connect again,i will be prompted to acept the certificate.Is this a normal behavior in Iphone.
Any suggestions would be greatly appreciated.
Thanks and regards,
Sendhil Balakrishnan

Hi
with the config i have i seem to be able to login using either tkip or aes, but i don't think i have got mixed mode configured on the AP so it should only accept WPA2-AES encryption but it also accepts TKIP making me believe something is configured incorrectly.
should i change anything in the config on the AP to only allow WPA2-AES encryption?
many thanks
rogier

Palm Pre & WPA2 AES Wireless Networks

I have a palm pre that I'd like to connect to a campus network that uses WPA2 AES encyption. I have the certificate required for this network already installed on the pre. However, when attempting to login to the network, it does not use the certificate and asks for a username/password. Of course, the logins will not work. Any workaround or is this just not supported?
Post relates to: Pre p100eww (Sprint)

Have you tried putting your domain name before the username, i.e. <DOMAIN>\<USERNAME>? e.g.
Username: School\John Doe
Password: **********
If you network is not hidden, you don't even need to specify the security setting. I think it does it automatically when I select a network from the list, at least for me. Good luck!

Connecting to WPA/WPA2-Enterprised network

hi all,
i just came to mcgill and was trying to connect to the school network. But it kept saying something like 'authorization failed'. School website has only instructions for BlackBerrys:
"Select wpa.mcgill.ca * (WPA/WPA2-Enterprise). Fill in the following fields:
Name: wpa.mcgill.ca *
SSID: wpa.mcgill.ca *
Security Type: PEAP
User Name: McGill Username
User password: McGill Password
CA Certificate: Thawte Premium Server CA
Inner Link Security: EAP-MS-CHAP V2
Token: None Selected
Server subject: blank
Server San: blank "
Help plz
Solved!
Go to Solution.

idecline wrote:
hi all,
i just came to mcgill and was trying to connect to the school network. But it kept saying something like 'authorization failed'. School website has only instructions for BlackBerrys:
"Select wpa.mcgill.ca * (WPA/WPA2-Enterprise). Fill in the following fields:
Name: wpa.mcgill.ca *
SSID: wpa.mcgill.ca *
Security Type: PEAP
User Name: McGill Username
User password: McGill Password
CA Certificate: Thawte Premium Server CA
Inner Link Security: EAP-MS-CHAP V2
Token: None Selected
Server subject: blank
Server San: blank "
Help plz
Try configuring your N97 with these instructions:
Since your WLAN network seems to require more advanced PEAP authentication settings you should probably create / edit appriate WLAN connection profile, known as (Internet) Access Point, manually in a following manner:
1. Go to Tools -> Settings -> Connection -> Network Destinations
2. Check if your earlier failed attempt to connect has already created an non-funtional IAP named as your WLAN network SSID (look for a entry named wpa.mcgill.ca) under "Internet" destination.
3. If you can see existing IAP named as your WLAN SSID then you can Edit that one with necessary changes. (skip to 7.)
4. If you don't see any existing IAPs that are named like your WLAN network then go to the desired "Destination" (e.g. Internet) and select Options -> Add Connection Method.
5. Assuming you are in the coverage area of your WLAN network you can let phone "Automatically check for connection methods" (i.e. phone scans available WLAN networks) and you should be able to select the correct WLAN network name (wpa.mcgill.ca) from the list. Once you have selected the WLAN network your "Internet" Destination should now have been added with a new Access Point (IAP) that is named "wpa.mcgill.ca". Note that at this point the particular connection method is still incorrectly configured for your purposes (since by defaul it has EAP-SIM & EAP-AKA authentication methods enabled).
6. Now you should manually Edit your newly created wpa.mcgill.ca Internet Access Point with necessary PEAP settings.
7. Configure following WLAN and authentication settings:
"Connection name" defaults to name of your WLAN network (wpa.mcgill.ca) but you can also change this if you wish
- "Data Bearer" naturally needs to be "Wireless LAN"
- "WLAN network name" should match your WLAN network's name (SSID) exactly (wpa.mcgill.ca)
- "Network status": Public
- "WLAN network mode": Infrastructure
- "WLAN Security mode": WPA/WPA2
=> Go to "WLAN security settings"
- Ensure that "WPA/WPA2 mode is set to "EAP"
- Leave "WPA-2 Only mode" to "OFF" unless you are absolutely sure that your WLAN network is configured to stricly pure WPA2 mode (i.e. network might be configured to support both WPA and WPA2 security thus enabling WPA-2 Only mode on the phone will cause all your connection attempts to fail).
=> Go to "EAP plug-in configuration"
- Enable "EAP-PEAP" and make sure that "EAP-SIM" and "EAP-AKA" are disabled (via Options -> Disable)
=> Select "Configure" for EAP-PEAP authentication method
- Leave "Personal Certificate" to "Not defined"
- Select "Thawte Premium Server CA" to be used as an "Authority certificate"
- Set "User name in use" to "User defined" (since there is no Personal Certificate where it could be read automatically)
- Enter your username (McGill Username) to "Username" field
- Set "Realm in use" to "User defined" and leave following "Realm" field empty.
- Note that in case your username (McGill Username) contains the realm (i.e. format is username@realm ) then you can enter realm part of your ID to "Realm" field and enter only the username part to the "Username" field.
- Configure "Allow PEAPv0" to Yes
- Configure both "Allow PEAPv1" and "Allow PEAPv2" to "No"
=> Go to "EAP's" tab to configure inner authentication method for the PEAP (use the small arrow pointing right on top of the screen to move between tabs)
- Enable "EAP-MSCHAPv2" authentication method and Disable all other methods (Option -> Enable / Disable)
- Select "Edit" for the EAP-MSCHAPv2
- Enter you username (McGill Username) to "User name" field
- Configure "Prompt password" to No or Yes depending on whether you want your password to be prompted everytime you make an connection or if you prefer saving your password to following "Password" field permanenly so that it won't be prompted during everytime you connect to this WLAN network with PEAP/EAP-MSCHAPv2 authentication.
- If you you selected "No" to password prompting then enter your password (McGill Password) to "Password" field.
=> Exit the configuration with "Back" (several times) and you should hopefully be able to connect with this setup.
If needed you can also change the priority order of the connection methods (IAP's) within the Internet Destination since your new connection most likely ended up being lowest priority WLAN connection within your Internet destination. This should however not be a problem unless you have some other WLAN networks defined as an IAP and these other WLAN networks are simultaneously available at the location of the wpa.mcgill.ca WLAN network.
Hope this helps you to get connected!!
Message Edited by saataja on 17-Sep-2009 05:16 PM

Xp won't connect to wpa2-psk security enabled network

I have 3 laptops, 2 with win 7 premium and 1 with xp home edition, the win 7's will connect to the internet fine...but the xp won't connect at all, now if I turn off the security xp will connect fine, can anyone tell me what my problem is please?
Thank you Kindly for any help

1. Make sure, you verify under "Preferred Networks" click on the connection that's not working, click properties.
Verify WPA2 is an option in "Authentication". If it's not download the latest drivers for your wireless adapter, restart computer and check again.
2. Next problem is XP's Wireless Lan Manager; it is absolute garbage on XP for WPA2. I have seen many XP SP3 unable to connect to WPA2 because of this. You need to use the wireless manager that comes with your wireless adapter drivers. When
you install them opt to install with the software, not just the driver.
Supreme Master of XP

Issue connecting touchpad to WPA2 PSK network

I have an issue connecting my touchpad to any WPA2 PSK networks. The SSID is broadcast and other devices can connect but the touchpad errors with "unable to associate" even though I typed in the correct password. Any help is appreciated, and no I do not want to change the network settings since this device is supposed to utilize WPA2.
Post relates to: HP TouchPad (WiFi)

Hi Terabyte,
I don't mean to take over deltatuks thread but as we are having the same issue i'll continue!
I have power cycled the router and turned off/on the wireless on the device. I've just ran the tests and they all passed! including wifi! lol.
Still not working though.
This is very strange

Wifi won't connect to WPA2 network after waking from sleep, requires reboot

My office has a WPA2 network that I use my MBP to connect to. When I go home for the day, I close the MBP and put it to sleep. When I get home and open it, it automatically connects to my home wifi network. I do the same coming back to work and when it wakes up it shows a connection to the wifi network, but whenever I initially do any network task, the connection drops and I am unable to connect until I reboot my mac.
I've tried turning off the wifi before sleeping, then turning it back on, but it does the same thing.
Any ideas?

Hi,
I'm thinking about a trouble with the route table. Try this in a terminal session after startup:
netstart -rn
ping <network address>
After somes answer, close the cover to go to sleep mode.
Open the cover and look the result of the ping command
Normaly you don't have a network
cancel the ping command and redo the netstat commande
Normaly some rows are missing in the result (i don' know why)

Connecting to WPA/WPA2 Enterprise Network

I am trying to configure an Apple TV to connect to our corporate network. I have a service account in AD that I am using in the profile, have pointed to our cert and trusted it in the profile, selected WPA/WPA2 Enterprise, and selected PEAP as the 802.1X authentication. I have done this after going over the settings with our network security engineer. Everything looks correct. After installing the profile and connecting it to the TV, I can only get a 169.X.X.X address (should be our private WiFi network of 10.9.X.X. Has anyone successfuly done this?

This is a user to user help forum only so no one here knows what Apple is working on.
http://www.apple.com/feedback/iphone.html

Unable to connect to Wi-Fi connection using WPA2 PSK authentication and encryption type TKIP

I was referred to here from this thread at the Windows Insider Program: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/unable-to-connect-to-wi-fi-connection-using-wpa2/07bae1ed-c7fb-4f85-9d26-5549cc23e57a?msgId=2eb70420-fe35-494b-a13d-dcacd4d55eb9&rtAction=1426697691002
My issue is copy/pasted below:
Original Title: TKIP selection in WiFi network settings
I have a workplace WiFi connection using WPA2 PSK authentication and encryption type TKIP.
On the machine I used to test Windows 10, I had a previous installation of Windows 7 professional which connected to my workplace WiFi using the above settings. After installing Windows 10, my workplace wifi settings were imported and worked fine.
Windows 10 had a system crash, and since I had deleted my previous windows installation, I performed a complete reinstall of Windows 7. However, when I went to install Windows 10 again, I had not taken the time to set up my workplace Wifi on Windows
7 before installing Windows 10. As a result, I had to set up my workplace wifi as a new connection in Windows 10.
When going to set up the wifi connection, the encryption type was grayed out, but appeared to default to AES. Searching the internet suggested that Windows 8.1 did not need a encryption type selected, because Windows could automatically determine
if it was TKIP or AES, hence why the option to select encryption type was grayed out. However, after completing the setup of my workplace wifi, Windows 10 could not connect to my workplace wifi. After restoring Windows 7 with a factory reset, and setting up
the workplace wifi (the encryption type selection was not grayed out and I manually selected TKIP encryption), my workplace wifi was working again.

I was referred to here from this thread at the Windows Insider Program: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/unable-to-connect-to-wi-fi-connection-using-wpa2/07bae1ed-c7fb-4f85-9d26-5549cc23e57a?msgId=2eb70420-fe35-494b-a13d-dcacd4d55eb9&rtAction=1426697691002
My issue is copy/pasted below:
Original Title: TKIP selection in WiFi network settings
I have a workplace WiFi connection using WPA2 PSK authentication and encryption type TKIP.
On the machine I used to test Windows 10, I had a previous installation of Windows 7 professional which connected to my workplace WiFi using the above settings. After installing Windows 10, my workplace wifi settings were imported and worked fine.
Windows 10 had a system crash, and since I had deleted my previous windows installation, I performed a complete reinstall of Windows 7. However, when I went to install Windows 10 again, I had not taken the time to set up my workplace Wifi on Windows
7 before installing Windows 10. As a result, I had to set up my workplace wifi as a new connection in Windows 10.
When going to set up the wifi connection, the encryption type was grayed out, but appeared to default to AES. Searching the internet suggested that Windows 8.1 did not need a encryption type selected, because Windows could automatically determine
if it was TKIP or AES, hence why the option to select encryption type was grayed out. However, after completing the setup of my workplace wifi, Windows 10 could not connect to my workplace wifi. After restoring Windows 7 with a factory reset, and setting up
the workplace wifi (the encryption type selection was not grayed out and I manually selected TKIP encryption), my workplace wifi was working again.

Connect to WPA2-AES network

Similar Messages

Maybe you are looking for