Related
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
My WiFi was working fine on my Xoom, and now it gets stuck while "obtaining IP address." It says for a split second "remembered" as if it was connected and starts the ongoing circular process of "obtaining IP address" all over again. I saw that galaxy tab users had this same problem and found a resolution by connecting "static" instead of "DHCP." I didn't try that as I honestly don't know how. What I do know is that there are a few devices like my OG droid, my laptop, my mothers' laptop, my xbox 360 that are connected to the same WiFi network. This randomly happened, when I decided to disconnect from WiFi to run a speed test on 3G and I was unable to connect to WiFi ever since. I tried unplugging/plugging the routers, turning the Xoom off and on, and even went so far as to doing a factory reset on the Xoom and I still can't connect. 3G works fine, but I have a 1GB cap and I would rather only use that while I'm on the go, and obviously WiFi is definitely faster. If I can't resolve this, I still have enough time to return this thing. Call me a newb, but I need a little help!
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Bauxite said:
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Click to expand...
Click to collapse
How do I get the xoom to forget the network? How do I remove the xoom as a remembered device? Sorry but I really don't know how to do that..
EDIT: I went into settings>privacy>backup and restore> and unchecked "back up application data, Wi-Fi passwords, and other settings to googles servers and was still unable to connect.
I think if you long press on the wifi network it will give you the option to forget it.
As for the router, do you remember setting it up? The settings pages where you set the wifi name and password and such.. it should have a section where it tells you which devices are connected.
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
droiduser1988 said:
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
Click to expand...
Click to collapse
Of course, anything that's connected to the router should let you configure it. It's too complex to explain here, but you need to enter the router through it's IP address and find the configuration.
Find the manual for the router you have and go from there.
I'll try to look into that, any idea as to wtf happened? This is beyond an inconvenience..
I'm having much the same problem. After entering the passphrase it says 'obtaining ip address from....' and thats all. It never connects??? I have tried 'forget' several times and no luck.
I have been able to connect to unsecured wifi with no problems.
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
jcampbell037 said:
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
OK, tried it. NO GO! After entering the passphrase it STILL says 'obtaining ip address from....' I may be doing something wrong with the app since it comes with absolutely NO directions. If this is going to be an issue average folks will take it back!
Have any of you with this issue verified that the DHCP scope on the wireless network is not full or that DHCP is even allowed? The fact it works one place but not another tells me the issue may be with the network and not the device.
Dave
Sent from my Xoom using XDA App
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
je2345 said:
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I also had this issue, I ended up fixing it by upgrading my router BIOS. the version that was on there was dated 2004 (yikes), and though the most current update was only 2006, it seems to have fixed the problem.
That or the reboot after the update as previous poster said and the update didn't really have anything to do with it, but either way it got fixed.
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?
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Asovse1 said:
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Click to expand...
Click to collapse
I don't have access to the PC. It is owned by the hotel. I need a solution that I can apply client (Nexus) side.
Solution
I found a solution. I asked the guy to reset the router and both my Nexus and S3 immediately connected. Someone advised me to do this. I have no idea why it worked. Not really a solution since i cant go round cafes asking people to reset their routers for me.
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
I sometimes have this Problem when starting my accesspoint after enabeling wifi on my N7.
I have to reboot my N7 in that case to get an IP.
Happened to me quite a few times when I went out with it to a restaurant or something. It just loops and loops.
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Embraced with this problem
bobbyelliott said:
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Click to expand...
Click to collapse
Resetting the modem solves the problem if you don't make any change to the router settings. I don't understand why the hell google is not solving the problem yet...
many users are found to face the same problem..
eve I can connect with my Nokia E72 but not with my N7...
I can get the IP from my cell phone. But come on, what's the point of doing so?? Are you gonna assign the IP for each and every WiFi you connect?? Or if the IP changes everyday??
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
gcd0318 said:
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
Click to expand...
Click to collapse
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
What was the solution?
bobbyelliott said:
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
Click to expand...
Click to collapse
For a simple display of the values look at something like Network Signal Info of Wifi Analyser (both free)
jet1000 said:
What was the solution?
Click to expand...
Click to collapse
Use a static IP .
Sent from my Nexus 7 using xda app-developers app
You can only get internet access when you'll be using the correct IP, DNS etc. So try to find out what is the working IP setting...
Sent from my Nexus 7 using xda app-developers app
Deleted
I just started having a similar problem. I have a samsung galaxy tab with Sprint. I've had it for a year and this is the first time I've had this trouble.
The only difference is, I cannot connect to any wifi network at all. It keeps hanging on "obtaining IP address" and then disconnects. It doesn't matter if it's my home wifi or school or free wifi in a restaurant.
The only possible connection I can make is that I downloaded Lookout to check it out as a possible security app, I have since uninstalled it but that did not fix my problem.
Continuing to research this but any ideas on how to fix this would be fantastic.
I'm having this problem on my HTC One S. It happened yesterday without warning and it's really annoying. I went to a nearby cafe and the wifi worked perfectly, so it's something wrong here.
Static IP solution connects to me to the network but I can't actually use the internet, so I'm stumped.
i'm getting the same error with AOKP 4.2.2, and also know people with stock 4.2.2 with it.
the only way i found to fix it is to reboot the phone..... and wait for it to happen again and reboot it again
i cannot use static IP since in my university (and some other public places) it is not possible to connect it like that :S
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
How did you solve this? I Need help with my tf 300
bobbyelliott said:
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Click to expand...
Click to collapse
Note: You Must have root.
Go to
/data/misc/dhcp/
and delete all 3 / 4 files there.
And voila it should work.
I just bought a nexus 7, came home and spent 3 hours trying to connect this to wifi and it doesn't work... meanwhile i have 9 devices connected wireless that never had problems... -_-
when i first start my NEW nexus 7 and get to select wifi page.. i select my wifi (which shows 3 bars) i enter my correct password and it just loops from "connecting.." to "obtaining ip address" over and over after hour of that i got fed up and tried connecting manually .. i tried using ip/dns from ipconfig in cmd didn't work.. i went to my iphone and copied the wifi adress settings to my nexus 7 and it said connected
but when i went to next i logged into my gmail account and i get this
"Couldn't sign in
Can't establish reliable connection to the server.
This could be a temporary problem. Try again or connect to another Wi-Fi network."
i have no idea what to do ARGGGG HELP PLZ!
MxZeal said:
I just bought a nexus 7, came home and spent 3 hours trying to connect this to wifi and it doesn't work... meanwhile i have 9 devices connected wireless that never had problems... -_-
when i first start my NEW nexus 7 and get to select wifi page.. i select my wifi (which shows 3 bars) i enter my correct password and it just loops from "connecting.." to "obtaining ip address" over and over after hour of that i got fed up and tried connecting manually .. i tried using ip/dns from ipconfig in cmd didn't work.. i went to my iphone and copied the wifi adress settings to my nexus 7 and it said connected
but when i went to next i logged into my gmail account and i get this
"Couldn't sign in
Can't establish reliable connection to the server.
This could be a temporary problem. Try again or connect to another Wi-Fi network."
i have no idea what to do ARGGGG HELP PLZ!
Click to expand...
Click to collapse
Expected it is not any Hardware issue, it seems your pb is related to your PW. try desabling it from your router (just a short time for test) or go to a free wifi place to check.
Also keyboard issue, do you use the standard one?
good luck
lolo9393 said:
Expected it is not any Hardware issue, it seems your pb is related to your PW. try desabling it from your router (just a short time for test) or go to a free wifi place to check.
Also keyboard issue, do you use the standard one?
good luck
Click to expand...
Click to collapse
Had this issue before with a bunch of Samsung phones turns out I had so many devices trying to use the same IP address set up by my router. I had to reset my router and assign each device its own IP address.
Sent from my Nexus 7 using xda premium
May also need to check the routers settings for maximum allowed wireless devices, or maximum dhcp users.
Sent from my Nexus 7 using xda premium
The obvious thing in your router configuration is that connections are being restricted to a list of hardware mac addresses.
peterk-1 said:
The obvious thing in your router configuration is that connections are being restricted to a list of hardware mac addresses.
Click to expand...
Click to collapse
The obvious is that jour Nexus 7 is not working properly, I had exactly the same behaviour tested many changes on my wifi settings, teathering from my phone...=> went back to the shop for an exchange and the new one was working perfectly