Database Users

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] Weird wifi dns issue under CM

I should note I am running CM6.1 RC2
So, I had the strangest thing happen this morning. I went to my in-laws for thanksgiving dinner and put my G2 on their wifi. It worked fine last night, but this morning after a few moments I am having very bizzare behavior over the wifi connection.
What seems to be happen is that the DNS lookup requests seem to fail when using the android apps. Now, for some reason, the wifi calling app connects, and I can place calls over wifi, but I can't use any other applications for data.
Here is where it gets weirder. If I ping an address, it works just fine, and then, since the dns resolution is cached, I can go to that domain in the browser, however any links that leave that domain do not work.
I have tried several things, setting a static ip address, using different DNS addresses (the router, and then google's dns addresses). Nothing seems to be working. I have also rebooted the router. Other device on the network are able to connect just fine.
The funny thing is that data works fine over the cellular network, of course there is only edge out here, and somewhat spotty coverage at that, but things seem to work just fine.
Any thoughts on what the issue might be?
Thanks!

Well, I ended up fixing it by doing a nandroid backup, restoring and clearing the dvalik cache. Weird.
Sent from my HTC Vision using XDA App

[Q] Wifi Connectivity Issues

I picked up a NC over the weekend and followed the steps to get CWM on SD and ran manualnooter to root then I installed CM7. everything seemed fine except after connecting to WiFi it never seems to actually connect very long and when it does connect its very slow. The most success I have had is when I connect to my hotspot running on my Inspire 4G. Is there a fix for WiFi or should I just start the process over and format the system, data and cache under mounts and storage. When it works its great but the fact is it does not work a lot more than it does. I have not even successfully opened twitter or facebook but I have gotten my gmail 2 times but the rest of the time it times out loading conversations.

I'm having an issue with recent CM7 nightlies in that redirecting hotspots (hotels, restaurants, trains) don't work anymore. On first access, I used to get the "Don't misbehave" click-through, but now I don't get anything, just the "web page is unavailable".
Anybody else seeing this?

Try going into wifi settings and click "never" sleep. Go to wifi settings, hit the menu button then sleep policies and click never. Worked for me.
Sent from my Nexus S using XDA Premium App

chefdave12118 said:
Try going into wifi settings and click "never" sleep. Go to wifi settings, hit the menu button then sleep policies and click never. Worked for me.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I will give this a shot once I get home this evening, Thanks.

Just a thought, are you connecting to a real router or an adhoc network?? if its to an ad hoc network there is some patches you need to look for

There is a know issue with CM7 stable and nightly builds ( based on 2.6.29 kernel) where using WPA2 AES encryption causes drops. The obvious workaround is to switch to WPA TKIP encryption if possible. The bug is said to be fixed in the CM7 beta 3.1 with the 2.6.32 kernel.

[Q] Upgraded MS2 Froyo to Gingerbread, now Mobile Hotspot doesn't work any more?

Has anyone got Mobile Hotspot to work on their MS2 after the upgrade to Gingerbread?
I've been having problems - Tte MS2 properly assigns an IP address to PCs that try to connect to it over WiFi, but the connection doesn't seem to go past my MS2 to the Internet. Same thing whether USB or WiFi.
I'm on T-mobile on the USA - could that have something to do with it, some kind of authentication is being performed now (that wasn't being performed on Froyo?)

I had this problem too.
Now I use the app "barnacle wifi tether" and it works fine.
I'm from Brazil...
Sent from my MotoA953 using XDA App

Thanks for the suggestion. If I root my phone I'll consider that option. Has anyone found any other fixes? I tried playing with the APN settings as suggested by some online, but it doesn't seem to help.

beestar said:
Has anyone got Mobile Hotspot to work on their MS2 after the upgrade to Gingerbread?
Click to expand...
Click to collapse
Usb sharing is f*d up - dnsmasq does not launches properly and phone gives no IP in response to dhcp req from pc. I don't remember, if setting an IP and gw manually solves the problem.
However launching _both_ sharing method at once helped. DHCP worked fine. Maybe launching wifi hotspot alone generates similar problem?

Did a factory reset and now Mobile Hotspot works!
Haven't tried USB tethering yet, will report back when I do.

Great! I also had this problem and this tip helped me.

Mobile Hotspot works but haven't got USB tethering to work properly yet. The computer can get an IP address from the phone, but no connection through to the Internet. This is after the factory reset.

Same with me here.. Already did FR but still no go..

Old thread I know but anyone sorted this yet, as its doing my head in, I even changed to a tethering plan in case i was being blocked.
Barnacle Tether doesn't work either same symptoms also says DHCP:Could not bind to DHCP port Address already in use

Use PDA Net, it's available in the Play Store

Caesarivs said:
Use PDA Net, it's available in the Play Store
Click to expand...
Click to collapse
Thanks Caesarivs I have tried that as well, just says obtaining ip address and then disconnects and says remembered

commanderaj said:
Thanks Caesarivs I have tried that as well, just says obtaining ip address and then disconnects and says remembered
Click to expand...
Click to collapse
Could it be your carrier blocking 3G tethering?

Hi
3G tethering is not blocked by carrier as I am on a tethering plan and have spent a long time on the phone to an Indian call centre to sort it.
But joy of joys after trying everything I could think of including re-flashing and wiping all data etc. I have managed to get it working using wifi tether for root user
Result

[Q] wifi not working on any rom

i've used about 4 different roms and can not get wifi to work correctly on fresh roms with wipe.
they all allow the connection and give the phone an IP address but none let the phone to the internet.
has any one any suggestions?

txt3rob said:
i've used about 4 different roms and can not get wifi to work correctly on fresh roms with wipe.
they all allow the connection and give the phone an IP address but none let the phone to the internet.
has any one any suggestions?
Click to expand...
Click to collapse
well dude, before we say it's a hardware matter, have you tried to connect with different WIFI? office, home.... you tried ROMs, but afterall connection is about 2-way.

This is very weird. 4 ROMs!? I've had issues regarding wifi with Gsf. But,this should be some problem concerning your wifi router.Check the settings and try.
Hey,another thing,just check the MAC addresses in your wifi after your phone connects.
Sent from my Blade using XDA app

Did you restore any wifi passwords using titanium backup while switching between the roms?

long time ago, i have the same problem as you...
i was reinstalling a hundred time a new rom and everytime, i restore app and data from backup titanium... and wifi doesn't work...

There is a issue with blade on wifi n network..it actually connects to wifi g,b networks...we need wifi n drivers to connect to the usual wifi n
-------------------
@vijaykirann