[Q] 802.1x WiFi - Epic 4G General

Hi after having no luck with Sprint customerservice I am hoping somebody here can help. I am using a rooted Epic 4G running Froyo. WiFi works great for me at home connecting to my WPA secured network but at work I am unable to connect to the 802.1x EAP secured network. It just keeps telling me its trying to connect and then finally gives up. Any help would be greatly appreciated.

Mac filter maybe???
Sent from my MyFrankenstein E=Bee13² ROM using XDAP App...

I dont really think so. There are a few people with EVOs that have had no problem connecting. I have tried using all the same settings they are using and still no connection for my epic.

are you sure you have it configured correctly? ask your work IT dept what security they have set up. We use AD to authenticate wireless clients, I had to manually specify MSCHAPV2 in phase 2 authentication

I have attempted with all of the different phase 2 authentifications. For what it is worth some of the people here are successfully using the none setting for phase 2 on EVOs.

Related

Captivate & 802.1x

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.

[Q] Wifi problem

i'm having trouble connecting my dhd to wifi. it can connect but i cant surf to any pages?
can someone help me?
any error message available?
have you tried restarting the router and then try again?
if fails, could you use an terminal emulator to type in ifconfig and check the IP address assigned?
wich encryption are you using to secure the connection?
no the only message i get is when i open a page it says it cannot load it
i tried restarting the router but nothing helps
lets start at the basics and work our way up,
go to settings, wireless en network, and wi-fi settings.
check if Wi-Fi is turned on. if so, look a little bit below this in the wi-fi networks section, does your network SSID show up? any info listed if you check that?
if nothing show's up, try add Wi-FI network.
if all this is working properly. and you still can't go on the internet, we'll move on.
Is this the first time you have used your router?
Try with the security off if that works turn it back on and try again had to do this a few times with some of my old routers.
Sent from my Desire HD using XDA App
i'm not totally a noob
i activated wifi and saw my ssid, i entered my wep-key and tried to connect. it receives my ipadress (it says it) and then says its connected...
i use this router more then a year and with other phones it was never a problem.
only with this phone.
last phones were SGS and dell streak now this one and problem.
tried to change channels of my router but standard its channel 6 and change or no change always problems
nielsvg said:
i use this router more then a year and with other phones it was never a problem.
only with this phone.
last phones were SGS and dell streak now this one and problem.
tried to change channels of my router but standard its channel 6 and change or no change always problems
Click to expand...
Click to collapse
Have you tried turning off security?
Sent from my Desire HD using XDA App
yes i tried it without security but still nothing
do you use DHCP? if so, a change in lease time doesn't help? if not, enable DHCP
what about other networks? do they work?
(switch bands to another supported wifi band, if you use N, try G???)
a friend said that dhcp should be disabled?
It gives out the up address to all your equipment and should be on
Sent from my Desire HD using XDA App
i tried turning it on but still nothing
Does your router filter out unrecognised MAC addresses. I set my router to allow access to only recognised MAC's. Try looking for a MAC Address Filter on your router.
no mac filtering is turned off
Have you assigned manual IP's?
no manualy ip
Check what ip address your phone has should be the same as your router except the last bit eg.
Router 192.168.1.1
Phone 192.168.1.3
If not they can't talk as on different domains.
If they are ok try pinging your phone from your router (if you can) or use your computer
Sent from my Desire HD using XDA App
What router are you using?

Wifi problem

Hi there!
Im on Froyobread v023b by dx. The thing is that the wifi connection (to wireless routers) isnt working quite well. It works okay at my home, but when i want to connect on a caffe wifi area, or at my school, i cant.
At my school, under the name of the connection it says "protected with WPA/WPA2 PSK" I dont know if it changes anything, but well.
Its always the same, i connect to the router, put the password, wait, and it keeps saying disconnected, or out of range even when i am on the range of the router.
Any help?
Goodbye!
I'm having the same problem with gingerDX. I use WEP security in my house and it works ok. But can't connect to any other wifi protected with WPA/WPA2 PSK =/
Try a full wipe
Sent from my X8 using XDA App
I already did a full wipe but it didnt change. It happened the same when i was with gingerdx.
And it seems to be the connections with WPA/WPA2 PSK
Goodbye!
It's a problem with configuration and compatibility. Different routers/ap's use different configurations, and configurations can have different settings.
I can only connect to my router with modded roms if i disable N draft on it or it gets on a "connecting loop". Does it mean the phone cannot connect with N routers? No.. I have no probs with my girlfriend router and it has N enabled.
You seem to have problems using WPA.. I use it also use WPA and have no probs.
The modded wifi libs must have an incompatibility with some settings.
Some routers allow you to tweak them alot, maybe changing some values can do the trick, or even changing the WPA encryption type..
Sent from my E15i using XDA App
Nikkopt said:
It's a problem with configuration and compatibility. Different routers/ap's use different configurations, and configurations can have different settings.
I can only connect to my router with modded roms if i disable N draft on it or it gets on a "connecting loop". Does it mean the phone cannot connect with N routers? No.. I have no probs with my girlfriend router and it has N enabled.
You seem to have problems using WPA.. I use it also use WPA and have no probs.
The modded wifi libs must have an incompatibility with some settings.
Some routers allow you to tweak them alot, maybe changing some values can do the trick, or even changing the WPA encryption type..
Sent from my E15i using XDA App
Click to expand...
Click to collapse
Is it possible to change the wifi libs of a custom rom for another one "more stable"?
Goodbye!
Lobialkon said:
Is it possible to change the wifi libs of a custom rom for another one "more stable"?
Goodbye!
Click to expand...
Click to collapse
DX already tried different libs but they all work incorrectly in some cases
My university uses 802.1x EAP with mschapv2 authentication. I don't have a problem if I go back to the stock eclair rom on my x8, but with froyobread and ginger dx, i get occasional connections, followed by drops, and then the scanning-connecting-disconnecting problem. Usually, I have to forget and re-enter the network details to connect. With Ginger DX v12, I can't connect at all.
i updated to DX v12 and connected today to my univ. wifi with no problem. i wasn't able to connect with the earlier version.
Sent from my X8 using XDA App
v2milk said:
i updated to DX v12 and connected today to my univ. wifi with no problem. i wasn't able to connect with the earlier version.
Sent from my X8 using XDA App
Click to expand...
Click to collapse
I updated today to gdx v012 and it connected in "some" places with WPA/WPA2 PSK, not all of them (my school for example).
It just keeps saying disconnected, searching, connecting to, disconnected, and so on.
Goodbye!
best for wifi?
Are there any custom roms for the x8 that work well in general and also don't have wifi problems?
I think "protected with WPA/WPA2 PSK"is the problem, my phone can't connect to this kind of net work, WEP and OPEND is Ok.
i can conect to any router with any security but... in gingerbread it auto disconect after 2min

Unable to connect - Wifi w/ certificate, IEEE8021X, PEAP, MSCHAP

I can't connect to my corporate wifi. The following process worked on my Kindle Fire, and dozens of phones of others in the office:
Add a new connection with hidden SSID
EAP = PEAP
Phase 2 = MSCHAP (not MSCHAPv2)
CA Certificate (got it, installed it, not expired)
domain\usr
pwd
Run WiFi Advanced Configuration Editor
Key Mgmt, uncheck WPA-EAP (IEEE8021X checked)
Enterprise Configuration, re-enter pwd.
Turn WiFi off, back on.
Ignore the SSID secured with WEP.
Done.
This process does not work on my 8GB Nexus 7. I've done the process enough times on my KF and other people's phones to know I'm not doing it differently on the N7. Yet, it doesn't connect. Ever. I sit right across from the AP. Also, I had someone else who's done this a dozen times before also try. No dice there either.
Any idea why I can't get connected?
<noob_shield>I found no (meaningful) results searching this forum for "wifi certificate" and a few other searches.</noob_shield>
Are you in a domain and running through a proxy server? If so try just joining the network normally using your domain\uname letting the cert install automatically then long holding the wifi connection modify connection check advanced then add the proxy settings, worked for me...
Sent from my Nexus 7 using xda app-developers app
_DrG_ said:
Are you in a domain
Click to expand...
Click to collapse
Yes, there's a domain. I'm using my domain acct as the identity/password
and running through a proxy server?
Click to expand...
Click to collapse
No proxy server.
If so try just joining the network normally using your domain\uname letting the cert install automatically
Click to expand...
Click to collapse
The SSID is hidden. I have to start by manually adding the network. Considering that I can't get to connect to that network at all, I'm not sure how to go about "joining the network normally." I'll try it without specifying/bringing my own certificate, and see if one is installed automagically. IIRC, iPad users don't have to manually copy the cert onto their tablet.
I'm having the same issue connecting a Nexus 7" on Jelly Bean to our wifi using a cert. I'm using the exact same settings I use on my Droid Razr Maxx (running ICS) and it connects no problem. If I figure it out I'll post up, but I have a feeling it's a Jelly Bean issue. On ICS when I install a cert it no longer shows in storage, however on Jelly Bean after installing it leaves the cert in storage. Not sure if maybe its not installing it completely, or if that's just how Jelly Bean will do it on all devices. Another thing I noticed is it strips the name of cert, whereas in ICS it leaves the cert name assigned. I'm going to mess around with it now.
This has been discussed and determined to be most likely a jelly bean issue.
Sent from my Nexus 7 using xda app-developers app
Lame answers from Google and ASUS
I tried to get the corporate network connectivity issue resolved through support at Google and ASUS. Google's response was to ask my IT guys to, "use mac filtering on the router". ASUS's response was to reset the tablet, when that did not work, Russell on their support line said that, "the Android OS does NOT support 802.1x EAP on the Nexus 7". This seems like a deal-breaker for the Nexus 7, buyer beware.

Help Connecting android to wep secured router

No one at work with an android phone/tablet can connect to the WiFi. IPhone/pad Windows p8 and laptops. Connect fine. It gets stuck at authentication error or can't authenticate at least on my phones/tablets. I don't know if there is an firewall issue but I find it hard to believe as other devices can. Is it an android issue? We have like 10 or so access points or extenders all under the same name. I don't know if maybe I need to find the main router and try connecting to that... any ideas?
Sent from my SCH-I605 using Tapatalk 2
Are you sure it's WEP? It sounds like you're using a flavor of 802.1x WPA like EAP-FAST which isn't really supported on Androids.
It shows up as WEP secured.
From what I've gathered. Some android phones used to work but there was a lot of people that couldn't connect. So they called our IT guy and he called our network guy and they got it opened up so everyone was able to connect. Then a short time later android stopped connecting
Sent from my SCH-I605 using Tapatalk 2
Long time ago but still an issue. Anyone know the issue?
Sent from my SCH-I545 using Tapatalk 2
First of all, WEP is highly insecure, but I don't know why you would have problems. I would upgrade the security to WPA/WPA2 to prevent people from "stealing" your internet.
Sent from my LePanII using xda app-developers app
Usually it's an issue with the router/AP, not the phone. No idea why either.
Normally the security protocol is WEP ,its ok..the problem is not with your phone maybe they adopted for MAC filtering..you should try to check with the network admin..or try connecting a laptop and see if it works with the same protocol..or try to check with the network admin to move on to wpa or wpa2..maybe things can sort out

Categories

Resources