My hd2 is running TyphooN CyanogenMod 7. I attend the University of Arizona and can't connect to their network. What happens is it scans, connects, authenticates, then disconnects? I have spent the last 2 weeks looking for a solution such as editing my wpa_supplicant and either my wifi gets an error or it still does not connect.
Also, I went down to my university's tech center and they told me I SHOULD be able to if the EAP is PEAP and the phase 2 is MSCHAPV2 but everytime i change it, it goes back to "none".
I have even tried switching to other roms in hope that it will work and still no luck.
please help me!
i had the same problem. i believe most ROMS have had this issue until recently. There are a few kernels that have been released that i believe address this issue. I'm using HyperDroid and it has this fix. if you insists on sticking with the ROM you have then just find a kernel with the fix.
grimmjaw said:
i had the same problem. i believe most ROMS have had this issue until recently. There are a few kernels that have been released that i believe address this issue. I'm using HyperDroid and it has this fix. if you insists on sticking with the ROM you have then just find a kernel with the fix.
Click to expand...
Click to collapse
Thanks grimmja! I will flash it over right now! is there anything else you did besides just set up the entering identification and password for the wifi?
hi everyone,
I have a similar problen, I am able to connect to my university wifi but I can't open any page other than the university pages. I fixed the proxy settings but it did not work. can anyone help me?
I should mention that I am using winmo not android.
Thank you so much grimmjaw! I updated the kernel to tytung r6 kernel and it connected in seconds!
Last Thursday I installed the 4.010.11 update from Acer and my wifi connection at work worked perfectly for one day. After the first day it switches very slowly back and forth between "Connecting" and "Scanning" but never actually connects. Looking at the active connections on the WAP we can see the MAC address of the tablet trying to connect but it won't do it.
We are using:
EAP method: PEAP
Phase 2: none
CA cert: unspecified
User cert: unspecified
Identity: my username
Anonymous identity:
Password: my password
My co-worker has a Xoom and it connects fine and both of our Android phones connect too.
We did not make any changes to the wireless configuration. The WAP I'm trying to connect to is an HP ProCurve MSM422 AP.
Today I backed everything up and did a factory reset and the A500 still won't connect. The unit connects just fine to all non 802.1x WAPs.
I have not installed the Acer wifi fix since my understanding is that it is rolled into the 4.010.11 update.
I've become pretty reliant on my tablet at work so this is driving me nuts. Anyone have any ideas?
Thanks,
Matt
same scenario for me, it appeared on the .08 update and I had hoped the .11 update would take care of this issue. However it didn't.
My Nexus One connects fine to the 802.1x connection. My A500 connects to wpa or open networks without trouble.
I don't use my A500 at work but I wish I could if I wanted to.
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Sent from my A500 using XDA Premium App
FloatingFatMan said:
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
Click to expand...
Click to collapse
The threads on here don't mention 802.1x and my tablet works fine with all the other wireless protocols. The other threads also reported that it would connected and disconnect quickly. My tablet takes several minutes before it switches from "Connecting" to "Scanning" and vice verse.
I have done all the other fixes (double reset, system restore, deleting the DHCP cache (was never there to delete on mine), using static instead of DHCP, etc) and they do not help, not even temporarily. I have not flashed the fix from Acer since the PDF in the patch.zip does not list my newer version as being affected. My understanding, after reading all those other threads, is that the patch is rolled into the .11 update.
dude64 said:
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Click to expand...
Click to collapse
I've done a factory restore and it did not help. First thing after restoring I went into my wireless settings and it would not connect. I figured since it worked for a day after doing the .11 update it would at least work temporarily after a restore but no dice.
-
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Wilda said:
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
Click to expand...
Click to collapse
Just got done trying the patch (after all the other resets suggested on the Acer website) and it didn't work. According to the documentation with the patch, it is only for versions .07-.09.
I'd also like to add that I use WEP on my home network and I connected without a problem this morning. We also use PEAP here at work, so maybe that's the issue.
FloatingFatMan said:
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Click to expand...
Click to collapse
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
rvholland said:
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
Click to expand...
Click to collapse
OK, I see what you're talking about now. The A500 only supports 802.11 b/g/n. Not sure what you connected to on the first day, but there is no listed support for 802.1X.
I'm not sure you've got a handle on the difference yet. 802.11 b/g/n is the wireless LAN spec, 802.1X is an authentication protocol used on top of the 802.11 layer instead of WEP or WPA2/WPA.
My A500, like the OP's, when running 3.0 worked fine on the network with 802.1X EAP authentication. If you are in the presence of a network running 802.1X and attempt to connect you are presented with a menu for information such as the info in the OP's first post. This info may still be entered in 3.1 for the 802.1X EAP network but it is not authenticating in 3.1 like it used to do in 3.0.
I suspect that the A500 is not presenting its entered credentials correctly such that the authentication process can complete.
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
well I installed the patch and will report tomorrow on the results...
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
To answer FloatingFatMan the WAP has two antennas which can be set independently. Right now one is set for b/g and the other for n. As was previously stated 802.1x is an authentication protocol and has nothing to do with speed. In our case it allows wireless users to be authenticated through Active Directory instead of using a password like WEP or WPA.
I'll try the Acer patch today and see if I have any better luck than rvholland.
pfc.joker said:
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
Click to expand...
Click to collapse
rvholland said:
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
Click to expand...
Click to collapse
I have the same version as pfc.joker (just the 16GB model), but I got the same results as rvholland. Went home and worked fine but at work it's borked. I haven't been able to find anything useful on the web regarding this. Anyone talked to Acer about it? I'm afraid they are going to charge me $100 for the call.
4.010.13 doesn't help
My a500 updated late yesterday to 4.010.13 and even though there was reference to some wifi tweaks it does not improve the situation I'm having on 802.1X authenticated wifi.
Retried this morning at work and the same results of scanning-connecting-disconnected and then followed by simply staying at scanning for a long time.
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
I received the 4.010.13 update last night and hoped it would fix the issue but like rvholland I too still cannot connect to the wireless at work. Hopefully a fix is found soon.
rvholland said:
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
Click to expand...
Click to collapse
Same thing here. Watching the connections on the WAP it looks like the A500 tries to connect but hangs on the authentication and therefore never gets to the point where the DHCP server can assign an IP.
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
rvholland said:
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
Click to expand...
Click to collapse
Thanks for taking the time to check in with Acer. We only have a few weeks before school starts and have a lot of projects that need to be done before the students come back so I have very little time to look into this right now. I sure hope you can get a hold of someone that actually realizes this is a separate wireless issue and is not fixed with .10 or the wifi patch on their website.
Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
UPDATE:
Asof Oct 15, 2012: This issue has been fixed in the 4.1.2 OTA.
jonnyg000 said:
Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
Click to expand...
Click to collapse
I'm afraid this is a Jelly Bean bug and not an issue with your particular device. You can see one of the many bug reports here: h t t p://code.google.com/p/android/issues/detail?id=34212 (forum wont let me post links yet ). The link provided has a flashable fix that I can confirm works for the Verizon Galaxy Nexus, but does not seem to work on the Nexus 7 based on the posts.
We basically have to wait for Google to fix this or for another dev to write a Nexus 7 compatible fix. Lastly, this bug fix is not included in custom ROMs, so you have to run it yourself either way. Very annoying on Google's part to break this.
crobles81 said:
I'm afraid this is a Jelly Bean bug and not an issue with your particular device. You can see one of the many bug reports here: h t t p://code.google.com/p/android/issues/detail?id=34212 (forum wont let me post links yet ). The link provided has a flashable fix that I can confirm works for the Verizon Galaxy Nexus, but does not seem to work on the Nexus 7 based on the posts.
We basically have to wait for Google to fix this or for another dev to write a Nexus 7 compatible fix. Lastly, this bug fix is not included in custom ROMs, so you have to run it yourself either way. Very annoying on Google's part to break this.
Click to expand...
Click to collapse
Thanks for the response. That bug looks exactly like the problem.
Apparently this bug has been open for 2 weeks without a fix, not boding well for JellyBean as an iOS competitor.
i uses wifi tether for root and worked with infuse hspa+
jonnyg000 said:
Thanks for the response. That bug looks exactly like the problem.
Apparently this bug has been open for 2 weeks without a fix, not boding well for JellyBean as an iOS competitor.
Click to expand...
Click to collapse
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
crobles81 said:
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
Click to expand...
Click to collapse
So should we flash it or copy it to the system/bin like the one post at the bottom says using root explorer? Do we need to rename that file at all or download as is?
Thanks,
Same problem here. Works fine on ICS device, but no go with 4.1.1 Nexus 7.
Verified permission....still doesn't work
I verified that the wpa_supplicant in /system/bin has the rwxr-xr-x permission.
Still doesn't work the EAP-TLS
Nexus 7 Network Configuration problems
From a less technical standpoint, similar issues:
Clear Wireless Internet Service at office and home.
New Nexus 7 16GB tablet.
No problem with initial network configuration at office. I entered the PW in the identified network and was instantly online.
Network at home, also Clear Wireless, with different name and PW, gave me long delay and repeatedly "Authentication Problem" failure. Two other devices (Android phone and Windows laptop) continued to function normally on the home network.
Call center wasted about an hour and wanted me to call the device manufacturer (ASUS) help call center, which I declined to do. Supervisor was better at English but not at network configuration. A trip to the Clear Wireless brick & mortal location and a temp tech rep there resulted in his ordering a new (replacement) modem for home use.
I could not delete or 'forget' the home network on my Nexus 7 to rescan for a new network configuration for the home network.
Took the Nexus 7 to the office and it again signed me on without a problem, but the home network disappeared while many other nearby business networks showed up.
My next step is to take the device back home and hope that a re-scan of the available networks will re-create a home network that will not result in the "Authentication Problem" failure from what I believe to be its faulty configuration that I was previously unable to modify, delete or 'forget'. I assume that "forget" means to delete or remove.
From the process of elimination, it appears to me that the home network configuration that was automatically created by the device is flawed and unless I can remove or re-configure it am at an impasse. Reconfiguration or removal for a re-scan were not available options when first attempted, unless and until, I get it home and am permitted to do so this time, I may have to return the device to Google under warranty.
Any related or similar problems or suggestions from others would be appreciated.
Thanks
crobles81 said:
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
Click to expand...
Click to collapse
In order to apply the "working" patch from the thread, you need an unlocked bootloader with CWR or to manually install the file in the filesystem with "root" (Superuser) access; either way, you're breaking the stock-ness of the device (not a cool thing to do in a corporate environment that prohibits such actions).
In order for most corporate users (which this bug almost exclusively affects) to use any Android 4.1+ device on the WiFi at their offices, Google will need to fix this with an OTA, and FAST.
I can't believe that google still hasn't patched this. They acknowledged the problem over a month ago and have a fix ready, but nothing has been done. I don't want to unlock my bootloader and root my N7 just to fix a stupid wifi bug that google already knows about. Between this and the random touch sensitivity issues all I can say is that google is lucky I'm already past the full refund period, or they would be getting this tablet back.
ravage485 said:
I can't believe that google still hasn't patched this. They acknowledged the problem over a month ago and have a fix ready, but nothing has been done. I don't want to unlock my bootloader and root my N7 just to fix a stupid wifi bug that google already knows about. Between this and the random touch sensitivity issues all I can say is that google is lucky I'm already past the full refund period, or they would be getting this tablet back.
Click to expand...
Click to collapse
I am not sure about fix for EAP-TLS. I tried all of the workarounds and it does not work. Perhaps that is why patch is still not issued.
6opuc said:
I am not sure about fix for EAP-TLS. I tried all of the workarounds and it does not work. Perhaps that is why patch is still not issued.
Click to expand...
Click to collapse
Same problem in my work wifi network with the Nexus 7, my Nexus One and other iphone or android devices working fine.
I do not want to root yet my one day old device to avoid problems with the warranty.
So bad that google does not pay attention to these problems that are really annoying for the new users :/
Managed to get it working
jonnyg000 said:
Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
Click to expand...
Click to collapse
Hope this helps ...
Managed to get nexus 7 connected to 802.11 wifi. So now Nexus 7 automatically switch between home wifi and corporate wifi. To have corporate wifi connectivity I needed to add the CA certificate (Ask your network administrator for it) in the tablet directory structure. No need to root the device for that. just follow instructions at the following instructions:
To install a certificate from your tablet's internal storage:
Copy the certificate or key store from your computer to the root of your device's internal storage (that is, not in a folder).
Go to Settings > Personal > Security > Credential storage > Install from storage.
Touch the filename of the certificate or keystore to install. Only certificates that you haven't already installed are displayed.
If prompted, enter the key store password and touch OK.
Enter a name for the certificate and touch OK.
Typically, a CA certificate included with a client certificate is installed at the same time. You can also install separate CA certificates using the same steps.
If you have not already set a pattern, PIN, or password for your device, you’re prompted to set one up. The type of lock that's acceptable may be predetermined by your system administrator.
You can now use the certificate that you installed when connecting to a secure network or for client authentication with Email, Chrome, and third-party apps. After a certificate is installed successfully, the copy in storage is deleted. (source: support.google.com)
All items as quoted above were entered except for phase 2 item.
Security type: WPA2-enterprise
Network authentication method: PEAP
fast Roaming enabled with PMK caching
Encryption type AES
EAP may work, but not TLS
xPBA said:
Hope this helps ...
Managed to get nexus 7 connected to 802.11 wifi. So now Nexus 7 automatically switch between home wifi and corporate wifi. To have corporate wifi connectivity I needed to add the CA certificate (Ask your network administrator for it) in the tablet directory structure. No need to root the device for that. just follow instructions at the following instructions:
To install a certificate from your tablet's internal storage:
Copy the certificate or key store from your computer to the root of your device's internal storage (that is, not in a folder).
Go to Settings > Personal > Security > Credential storage > Install from storage.
Touch the filename of the certificate or keystore to install. Only certificates that you haven't already installed are displayed.
If prompted, enter the key store password and touch OK.
Enter a name for the certificate and touch OK.
Typically, a CA certificate included with a client certificate is installed at the same time. You can also install separate CA certificates using the same steps.
If you have not already set a pattern, PIN, or password for your device, you’re prompted to set one up. The type of lock that's acceptable may be predetermined by your system administrator.
You can now use the certificate that you installed when connecting to a secure network or for client authentication with Email, Chrome, and third-party apps. After a certificate is installed successfully, the copy in storage is deleted. (source: support.google.com)
All items as quoted above were entered except for phase 2 item.
Security type: WPA2-enterprise
Network authentication method: PEAP
fast Roaming enabled with PMK caching
Encryption type AES
Click to expand...
Click to collapse
I see that your authentication works, but for example, my school uses CA certs for their 801.11x network that work with TLS as a phase 1.
Successfully installing the CA cert and properly identifying the signal do absolutely nothing for my tablet other than give it an authentication loop.
Have tried multiple times at re-installing the certificate to see if it was just not done right the first time to no avail.
It's the TLS authentication library on the device (at least that's what the code.google bug report page says).
I'm not sure if this will really help those of you at work, but I was having authentication issues on my home network as well. I discovered that I was able to get around the authentication bug by connecting via WPS (Wifi protected setup). Just go to wifi settings and hit the symbol that looks like two arrows in a circle. If your router supports WPS it should have a button with the same symbol. Just press and hold until a light comes on and you should be able to connect just fine.
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
biggiestuff said:
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
Click to expand...
Click to collapse
I can confirm that updating to 4.1.2 did solve my problem with connecting to the Wi-Fi at my company. We use 802.x PEAP MVSCHAPv2 :good:
biggiestuff said:
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
Click to expand...
Click to collapse
Yup, the 4.1.2 OTA fixed it :highfive: .. only took the Android team 3+ months to release a patch after root cause was identified.. how agile of them..
'Tis a shame corporate has since banned the use of N7's for business use because of the WiFi issue in Stock 4.1.1. :silly:
I just had to submit a re-eval request on 4.1.2+ in order to stop blocking the N7 MAC's from the network.. ( that should only take about 1-4 MORE months to get the device re-reviewed, approved, and enabled.. yay ).
I am confused on how you got your Nexus 7 fixed. My work's wifi network also uses Dynamic WEP 802.1x, but even after updating to V4.1.2 I still can't connect. (Although I could with my old Galaxy Tab running V2.2)
Encryption: WEP
Security: 802.1X EAP
EAP Method: PEAP
Phase 2: MCHAPv2
The network shows up as "Secured with WEP", but if I try to create an identically named network with 802.1x settings (or start with a bogus password for WEP and try to use the WifiACE app to add the 802.1x settings), I still just end up with an identically named network that is always "Not in range".
What did you do after the V4.1.2 update to get it to work?