It appears the Evo 3D has issues staying connected to these networks, whereas the 4G on both Sense and AOSP worked fine.
Here is my network at work:
802.1x EAP
Enterprise(802.1x)
EAP method - PEAP
Phase 2 authentication - MSCHAPV2
then enter identity, skip anony identity, then enter password. Then I should be gold, but after a reboot, it can no longer stay connected.
Anyone else having this issue?
I'm having a similar issue. The wifi setup is pretty much the same as yours. Users with a Nexus S are able to roam around just fine and their wifi stays connected and automatically reconnects when the SSID is in range. I have an Evo 3D and even though it says it remembers the SSID, I have to re-enter my password whenever the device needs to re-establish connectivity (after a restart, coming into the office in the morning, etc). I am able to reauthenticate without any problems though.
Email HTC or call, notify them..its clearly a bug/glitch that's needs to be addressed
Bussin Caps from my 3D shooter
Is there a reason that an open wifi netword that has you login from a web page would run so slow. It suppose to be a 100Mb/s speed and on the computer it gets 80+/9+ but on my phone, with it saying its connected. It gets .4/.4 from the speedtest app. My home network is 20/2 and i get like 14/1+ on the phone. Sometimes I get less.
I can give it a try here and let you know what happens.
While I haven't tried the wifi yet, I did try syncing to my work exchange account, and it gave me an error saying 2 policies were not supported (installing unsigned app packages and smime soft certificates). My hero could sync with the exchange account just fine, so I'm wondering what's different. I may have to get in touch with our IT group........
This morning, my WIFI connected no problem, but I haven't rebooted it since yesterday. I seriously think it has to do with rebooting. It's a bit bizarre.
Related
I am having difficulties connecting my Amaze to my corporate WiFi. It gets stuck in the endless "authentication" loop. Authenticating, disconnecting. Authenticating, disconnecting. And so on and so forth. It simply won't connect even though my IT department has verified that my login credentials are correct.
Has any one else run into this issue? This is very annoying.
Thanks in advance!
Tedy...
Most corporate WiFi use MAC filtering as well. Since you looped in your IT department I wouldn't think they'd consider that, but it's something to try if not.
Settings > About > Hardware info > Wi-Fi MAC Address
The next thing to consider is that the ports used for wifi calling may also be blocked by default, as well as UDP, too.
Good luck regardless...
tedya said:
I am having difficulties connecting my Amaze to my corporate WiFi. It gets stuck in the endless "authentication" loop. Authenticating, disconnecting. Authenticating, disconnecting. And so on and so forth. It simply won't connect even though my IT department has verified that my login credentials are correct.
Has any one else run into this issue? This is very annoying.
Thanks in advance!
Tedy...
Click to expand...
Click to collapse
I had the same problem until I updated my phone by going to settings/ about/ htc updates. After the update it connected first time and stayed connected.
PGMMA said:
I had the same problem until I updated my phone by going to settings/ about/ htc updates. After the update it connected first time and stayed connected.
Click to expand...
Click to collapse
I OTA updated to .6 from .5 but still experience the same Authenticating loop the OP posted connecting to the WPA2 Enterprise Wi-fi. It seems like it's experiencing a timeout after 30 -50 minutes of inactivity. Typically, after turning wifi off then back on resolved this but it becomes a pita.
Also, when it's stuck authenticating (and not connected), TMO data is not enabled as well - the end result is no data connection at all and no synching is achieved. That's my experience any ways...
Just wanted to add - My home wifi (WPA2 Personal) is flawless!
I use WiFi Advanced Configuration Editor free app from the market works great when it comes to corporate wifi.
lester1 said:
I OTA updated to .6 from .5 but still experience the same Authenticating loop the OP posted connecting to the WPA2 Enterprise Wi-fi. It seems like it's experiencing a timeout after 30 -50 minutes of inactivity. Typically, after turning wifi off then back on resolved this but it becomes a pita.
Also, when it's stuck authenticating (and not connected), TMO data is not enabled as well - the end result is no data connection at all and no synching is achieved. That's my experience any ways...
Just wanted to add - My home wifi (WPA2 Personal) is flawless!
Click to expand...
Click to collapse
Yes, this is exactly what is happening. Even after the update, it won't connect.
Now, if we could just get the update for WiFi Calling.
Hi
I'm not sure if it's Android or Transformer prime thing.
My google data (gmail, gcal) syncs properly and immediate when i'm @home with my wifi network, but refuses to automatically sync at the office wi-fi network.
The office network is freely available to the device, i can browse the net without any problems.
Can figure it out why the sync doesn't work.
I have noticed the same issue on mine except my home network sometimes has the issue too. I have resolve it by disabling the sync and then enabling it again. This method works for a little while then it seems to go into the no new notification mode. I have to manually refresh in gmail to get my new mail to show up. It is annoying. I even send test emails to both my phone and tablet, but it will not ccome through until it feels like it or unless I manually update. My xoom does not do that.
I have a sort of similar thing. All I know is that I'll be delivering pizzas while tethered. As soon as I get home, and turn off the tethering, my tablet connects to the home WiFi and gets one or more notification noises as it if wasn't syncing the same way when tethered. The oddity is that it doesn't know I'm on a mobile connection so it isn't trying to save bandwidth. I suspect there is something in the security or ports that makes it's connections to the home network different than when tethering, or when you are at work.
I can't speak to the issue regarding tethering, but for those of you having issues at the office, this is most likely due to firewall rules. I work for a cybersecurity software company, and have been fighting for them to address this as both my phone and prime suffer from the same thing.
If you have a good relationship with your IT/Corporate security people, try bringing it up with them.
tdrussell said:
this is most likely due to firewall rules
Click to expand...
Click to collapse
do you know if google sync services uses other than 80/443 port numbers?
Not only did I notice this same thing happening I also noticed emails I had are disappearing when not on home network and Wi-Fi tethering with my phone this is weird...... they disappear from my gmail application......
So I know wifi in android is buggy, this isn't a question about that.
My Touchpad won't connect to my wireless network at work. (in webOS or android) It always fails the IP configuration part. My android phone connects fine, and my laptop, and my iPad.
Kind of kills the usefulness of the tablet for me. Wondering if I should call up HP before my 90days are up.
Thanks in advance
I have had no issues with webOS 3.0.2 or 3.0.4 at work or home (and I run a number of access points at both locations). Always connects by itself everytime. Too early to tell with 3.0.5 but no issues so far.
Have you tried other routers? It could be just some issue with your router. Have you tried to manually assign an IP, I know you can in android.
spunker88 said:
Have you tried other routers? It could be just some issue with your router. Have you tried to manually assign an IP, I know you can in android.
Click to expand...
Click to collapse
It connects to my home network fine, just not the work one. Tried manually assigning an IP and that didn't work in either OS. Going to install the update to webOS and see if that fixes things.
As poster above mentioned, corporate/work networks seem to be the only thing that webOS MIGHT not play well with occasionally. I've gotten it to successfully connect to my work's 802.1x EAP network. It actually worked quite well, but then sometimes it stumbles a bit before connecting.
For the most part though, webOS wifi works just fine. Of course, this is because HP dev'd it with the drivers they have, that we DONT have, and most likely will never have.
Wifi now connects on both OS's after updating webOS to 3.05
Lol go figure
R1ptide said:
Wifi now connects on both OS's after updating webOS to 3.05
Lol go figure
Click to expand...
Click to collapse
It hasn't before for you? I'm curious about your experience.
The deal with Wifi in android is multi-faceted:
1. Accessing the wifi options sometimes crashes the thing, and you have to force close the settings app and try again.
2. With Wifi on, the wifi menu can be quite sluggish
3. A lot of times, it wont even scan for networks. It just says disconnected for ages, or will eventually scan, then try to connect, but never get past "Acquiring IP address".
4. A lot of times it will randomly lose its connection, yet still indicate that it's connected just fine. A toggling of the wifi usually fixes this, but also starts you at square 1 with attempting to connect to an AP. For some people, this process can be a nightmare.
5. Some people simply cannot connected to their secured network at all. Period.
Are you experiencing any of these issues still?
nickmv said:
It hasn't before for you? I'm curious about your experience.
The deal with Wifi in android is multi-faceted:
1. Accessing the wifi options sometimes crashes the thing, and you have to force close the settings app and try again.
2. With Wifi on, the wifi menu can be quite sluggish
3. A lot of times, it wont even scan for networks. It just says disconnected for ages, or will eventually scan, then try to connect, but never get past "Acquiring IP address".
4. A lot of times it will randomly lose its connection, yet still indicate that it's connected just fine. A toggling of the wifi usually fixes this, but also starts you at square 1 with attempting to connect to an AP. For some people, this process can be a nightmare.
5. Some people simply cannot connected to their secured network at all. Period.
Are you experiencing any of these issues still?
Click to expand...
Click to collapse
Before update:
never had any problems with wifi at all, except it just wouldn't connect to either of my two networks at work in either OS. Neither OS could get past the IP config stage. Tried manually assigning IPs in both OS's but that accomplished nothing. Home 5ghz network zero issues.
After update:
Instant connection, no issues.
Hey all,
I've had my Galaxy S II GT-i9100M for a bit more than two months now. It's been on ICS 4.0.3 since the first day I got it, and is unrooted.
Wifi was working fine the first month or so that I've had it. However, in the last month, while trying to connect to my university's networks from the wifi settings screen, it will display "connecting" for a long time, then change to "saved", without successfully connecting to the network. Odd thing is, if I turn the wifi on and off repeatedly, it may connect eventually, with around a 5-15% success rate each try. However, there's also a relatively high chance it will automatically disconnect itself within a few minutes.
The school has three main wifi networks: one is unsecured, while two are secured with exactly the same authentication methods (PEAP + MSCHAPv2) and takes the same login credentials. All three have the same problem when I try connecting. It's not a problem with signal strength, either, since my friends nearby can connect using their phone or laptop without any problems.
Here's what I've already tried to do to fix this:
Asked the school's IT helpdesk
Forget both secured networks so the phone can autoconnect to the unsecured one
Tried wifi diagnostic tools, such as Wifi Analyzer and Wifi Fixer, and tried changing to a better channel
Deselected "back up my data" in the Back Up and Reset settings screen, deleting existing wifi settings from Google's servers
Connect using a static IP address rather than DHCP. Either it has the same Connecting->Saved issue, or says something about "avoided a poor connection"
Did a factory reset, including wiping all user data
The wifi has no problems connecting to my home wireless network, and to most, though not all, other public networks I've tried (same problem as above if it doesn't work).
On a somewhat different note: there are two networks (each of which I've only connected to once at most) that are permanently saved on the list of access points; there's actually no way to forget/delete the network. They even survived the hard resets, and are listed before I link the phone to my Google account. Could this be related to the main issue above?
Is there a fix for this issue? Thanks in advance for any suggestions!
Hello - Have been running XtreStoLite rooted for months now on my SM-G900T. About a week ago all of my known Wi-Fi connections would stop working sporadically. When I take a look at whats going on, my phone says there is authentication issue (password is wrong). It would seem obvious that this is the problem but I know this is not the case when connected to the few Wifi networks I consistently use, because I would have to be the one that would change the Wifi password to connect (I haven't changed it). Also, it may work normally anywhere between a few seconds to a few hours, then bam, out of nowhere I'm disconnected due to authentication problems. Where I'm at now is that there is something wrong with my S5, causing it to send the wrong password credentials. Even if I forget the connection and re-enter credentials it will fail, no other devices have this problem on these Wifi networks. Does anyone have an idea where to start troubleshooting now?