Currently Being ModeratedOct 14, 2011 2:33 PM (in response to zerohorn)
Me too similar problem. We can connect via LEAP and provide AD credentials. Works fine for a while but when the device locks and asks for a PIN or Password to unlock users are prompted for the WEP password. It is like it isn't caching passwords correctly.
Currently Being ModeratedOct 16, 2011 1:00 PM (in response to WillGonz)
I have the exact same issue as WillGonz. Apple need to address this issue as it is very annoying. I need to create the profile manually every time I need to access the wifi..!
Currently Being ModeratedOct 16, 2011 8:12 PM (in response to zerohorn)
Users at my work are having the exact same issue after updating to iOS5.
We use both WPA Enterprise, TKIP, PEAP for G networks and WPA2 Enterprise, AES, PEAP for N networks.
I've tested on my first gen iPad and iPhone 4, and any other staff who have upgraded have the same issue. All connected fine prior to the upgrade.
My iPhone 4 and iPad both still work perfectly at home using WPA2 Personal.
Anyone have any ideas?
-- Oh, still have the same issue when manually adding the profile
Currently Being ModeratedOct 17, 2011 3:23 AM (in response to zerohorn)
I have the same problem:
Cisco WLC's -> WPA2 Enterprise AES + EAP-PEAP 802.1x with CCKM
Pre 5.0 - all worked fine
Post 5.0 - it tries to connect and after few moments i get error - couldn't connect.
Info from controller:
10/17/2011 12:16:37 CEST INFO 172.16.16.X Sending EAP request to client from radius server. 6.f. ..l
10/17/2011 12:16:38 CEST ERROR 172.16.16.X Retransmitting EAP-ID request to client,retransmission timer expired. 5.y. ..l
10/17/2011 12:16:39 CEST ERROR 172.16.16.X Retransmitting EAP-ID request to client,retransmission timer expired. 5.y. ..l
10/17/2011 12:16:40 CEST ERROR 172.16.16.X Authentication failed for client as EAP ID request from AP reached maxmium retransmissions. 5.yp ..l
10/17/2011 12:16:40 CEST ERROR 172.16.16.X De-authentication sent to client. 5.oP ..l
10/17/2011 12:16:40 CEST ERROR 172.16.16.X 5.yp ..l
10/17/2011 12:16:40 CEST ERROR 172.16.16.X EAPOL-key is invalid, scheduling client for deletion. 5.yp ..l
On the Radius server i don't see any activity regarding this device.
I had this network configured on my iPhone - after upgrade and restore it remembered it. Every time i was in vicinity of my Enterprise WLAN it tried to connect - resulting int express battery drain - 6-7 hrs and battery was empty from 100%
Currently Being ModeratedOct 17, 2011 4:27 AM (in response to zerohorn)
That is a bug. Hope Apple will release a hotfix ASAP!!!!!
Currently Being ModeratedOct 17, 2011 4:56 AM (in response to zerohorn)
The problem is only related to Cisco and iphone/ipad with IOS5. As we have also a trapeze network and there we don't have the problem.
Currently Being ModeratedOct 17, 2011 5:09 AM (in response to zerohorn)
I'm glad I'm not the only one. Does anyone know what we need to do to file bug with Apple?
Currently Being ModeratedOct 17, 2011 5:48 AM (in response to peterfrombuggenhout)
So have Apple already known this bug? When will they release the fix?
Currently Being ModeratedOct 17, 2011 12:38 PM (in response to zerohorn)
Funny thing with my Iphone 4 and 4s is that i am not having this issue with my Iphone 4 which is upgraded to IOS 5, but i am having this issue with the 4s out the box. Makes me wonder if this is IOS 5 ralated or 4s related.
Currently Being ModeratedOct 17, 2011 3:12 PM (in response to zerohorn)
I also am experiencing this issue. Would like to know if there is a solution available.
Currently Being ModeratedOct 17, 2011 5:13 PM (in response to zerohorn)
Same problem here. My 4 upgraded to ios5 worked on Friday at work as WPA Enterprise connection. Came in today with my new phone and it logs on but loses it's connection everytime the phone goes to sleep. I have to set up the connection from scratch every time. It's definitely the phone and not the ios. I can't believe this was not discovered before.
Currently Being ModeratedOct 17, 2011 5:50 PM (in response to zerohorn)
It looks like we are all having a similar problem - Except -
The issues we are having ARE iOS5 specific, as there were no issues what so ever prior to upgrading, and we have now tested in the iPad, the iPad2, iPhone 3gs and iPhone 4. It is only when using 802.1x Authentication. We created a separate SSID for testing purposes with Open Authentication and had no problems. Also had no problems using WPA or WPA2 PSK authentication.
After upgrade, if previously connected, the phone must retain the Wireless Certificate as they keep trying to connect to the wireless and sometimes look like they have connected (when in 'settings' rather than stating 'not connected' next to Wi-Fi is states the SSID of our network), yet if you try to do anything to use it, or even click on Wi-Fi to show surrounding networks it 'drops out'.
This results in seriously poor battery life as it is constantly trying to connect. The phones also get quite warm due to the constant interaction with the Access Point. Once you choose 'forget network' the certificate is gone, so the phones stop trying to constantly connect. This means battery life etc. is back to normal. When attempting to re-connect we get 'Unable to join the network "Network SSID".
I have not reported this bug to Apple, also not sure whether anyone else has (not too sure how, will look into it) but a bit of Google searching pointed me to this thread, and also another one on a separate website. Hopefully something comes up.
Currently Being ModeratedOct 17, 2011 5:56 PM (in response to Alaine89)
But my network connection was fine on my iphone 4 after upgrading to ios5. It wasn't until I tried with my 4s that I had this problem. Seems to differ to everyone.
Currently Being ModeratedOct 18, 2011 5:34 AM (in response to Alaine89)
Alaine89, you are spot on with your description of the problem. This is exactly the same problem we are having, you just explained it with much better detail than I did. Have you had any luck finding a way to report a bug without having a developer account? From what I found it looks like need a developer account to report bugs. I agree this is definately an IOS 5 bug rather than a device specific bug.
Hopefully IOS 5.0.1 is right around the corner with a fix for this.