Has anyone managed to connect to a WPA2 Enterprise protected network? Using PEAP and MSCHAPV2, I haven't been successful. There seems to a bug in Froyo that was fixed after whatever build the Elocity is using: hxxp://code.google.com/p/android/issues/detail?id=8804 (I'm not yet allowed to post links).
I haven't had a chance to try the latest firmware yet.
Thanks,
..Mel
Thanks for logging this. I have the same issue. I was beating my brains trying to figure out why my Galaxy S would connect, but my A7 would not with the exact same settings.
Damn it
Noooooooooooo. I am waiting on mine being delivered and the sole purpose was to hook up to my work network which is WPA2 enterprise.
I hope someone out there has a fix for this. Donations a plenty for the person who does I tell ye.
I was able to connect to our network via PEAP just fine however this tablet does not have a proxy setting for wireless (this option is reportedly only available on models with 3g). All of my attempts at 3rd party addons to access the proxy settings screen have been unsuccessful as well.
hi everyone, some days ago I installed the virtuous 1.6, than replaced with a rooted stock 3.1. Since then, when I disconnect from my wifi for a while, getting far away from my router, it happens that coming back into the wifi field the tablet tries to reconnect but after 4 or 5 times it stops trying and tells me the connection is disabled. I see the dhcp service bouncing, no ip assigned. The only solution I've found googlin' around is to rename/delete the file dhcpcd-wlan0.lease in /data/misc/dhcp. It worked. but the issue got back again and again. I wanted to find out the cause and solve the problem once and forever, if possible. It's a pain in the... you know
Here is my topic. There is also one solution to it apart from the one you've found in google (which was probably my topic anyway ).
You're right, it'was your post. I've read it againg but I can't find out which could be the alternatrive solution. Keep in mind that when I got this wrong behaviour the first time obviously I invesitgated the possible causes, and I discovered the inability to retrieve a dhcp IP address either with my wifi router, with my wifi access point 3g and with a tethered connection via Iphone (all of them I normally use when I'm not at office). None of these would work until the uplisted file deletion). Would you be so kind as to suggest me, if you can, the possible solution in more detail (apart from performing a global reset that would be as annoying than deleting the file)
In any case, many tnx for your answer
Currently the common solution is to abandon the leaked 3.1 rom or put up with the bug.
Manually setting DHCP also works but it's usefull only if you'll use the tablet on one wifi. Else it's just a big pain in the arse.
I have same issue with the stock 3.1 rom.
At the end what I did was manually assign IP address for my iPhone's MyWi connection.
It seems mine has no trouble to connect to my home wi-fi network as well as work...
I also get that problem. But now, seems to have fixed it. I have done the followings:
- delete the dhcp lease file
- change the channel of my wifi router to 9 or below
- download the ad-hoc supported wpa_supplicant
Please try if above help you
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.
Hi,
I am facing the follow issue: my VPN connects and indicates it is connected: however when VPN shows as connected, I seems to lose all trafic and local internet connection (via my router).
Had this also on 3.01 but still persistent in 3.1 (4.010.42) as well.
I am rooted and have looked in the Market for VPN tools/apps. Tried a bunch but no solution.
Any suggestions?
Thanks. Marcher
Can it be that the VPN server is forcing you to tunnel all traffic through itself?
An easy way to test this is, does the same thing happen if you connect to the VPN server via your laptop/desktop pc?
Marcher said:
Hi,
I am facing the follow issue: my VPN connects and indicates it is connected: however when VPN shows as connected, I seems to lose all trafic and local internet connection (via my router).
Had this also on 3.01 but still persistent in 3.1 (4.010.42) as well.
I am rooted and have looked in the Market for VPN tools/apps. Tried a bunch but no solution.
Any suggestions?
Thanks. Marcher
Click to expand...
Click to collapse
It has never worked on this. Was broken in 3.0.1 and still broken in 3.1.
I heard that it is finally working on 3.2 on xoom. So it might work when we get the next update.
Sent from my A500 using Tapatalk
Thanks Guys
Thanks for the feedback. The VPN is working fine on my (Acer) netbooks and desktops. It would be great if 3.2 fixes this (if and when we get the update from Acer )
Marcher
To my understanding the 3.2 update was pulled for the dhcp issue with wifi. it seems though I'm having the same problem with the overcome rom. The can anyone confirm if hey are having the same problem?
PHP:
anrichp said:
To my understanding the 3.2 update was pulled for the dhcp issue with wifi. it seems though I'm having the same problem with the overcome rom. The can anyone confirm if hey are having the same problem?
PHP:
Click to expand...
Click to collapse
This issue happend to me as well with the official OTA update. The main story is pretty much like this:
The tab updated over the air, to 3.2 stopped being able to connect to a DHCP WiFi network. Basicly this is a network that gives your tablet the IP configurations automatically. This goes for almost all modems and routers out there.
To "Fix" this problem, you have to manually setup your connection from your tablet, putting in the right IP adress numbers to match your router, etc. And I also belive that I had do remove the DHCP function from my router.
I couldn't handle this and basicly wanted to "save" my tablet, instead of downloading yet another update from Samsung, that might be currupt. So I Flashed "Task650" 3.2 ROM, it's really quite nice and I didn't have any issues since then. It might be that the overcome ROM failed to fix this part, or that you got a bad flash?
Greetings.
I had the same problem and then did a restock and reflashed 3.2 and it solved the problem.
Sent from my GT-P7500 using xda premium