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.
I rooted my 4G, installed the MobileAP app via clockwork or whatever. It works and it will share my 3g connection, but it when I switch the phone to 4g, my laptop and ps3 say something about a DNS error. My phone will say that it is connected to the sprint 4g network, so I'm wondering if this is a problem with MobileAP or maybe the 4G coverage where I live.
Any Ideas?
edit I was wrong
Is there a way to get my phone to share the connection with a router? Maybe through my laptop somehow?
Skimp Killah said:
Is there a way to get my phone to share the connection with a router? Maybe through my laptop somehow?
Click to expand...
Click to collapse
If your router supports it, such as a DD-WRT enabled router.
4g works
Restart your phone, turn on 4g, make sure is connected and start the mobileAP, it works with my stock rooted 2.1
the only thing is that if you get disconnected from 4g, it wont tether from 3g and vice versa
I bet that MobileAP just hands over the DNS resolver addresses it gets from the 3G or 4G connection, and that if your connection switches to the other, the old servers are no longer accessible. If you can force a DHCP renew from the tethered-device end, the addresses might update. But if MobileAP caches the DNS resolver addresses once on startup, even that won't work. Makes sense though, MobileAP wasn't intended for phones that have dual network connectivity.
I'm not sure if the Sprint Hotspot application is any better about this. I do know that android-wifi-tether uses dnsmasq as a forwarder and gives that address to tethered-devices, so it will continue to work on a connection change. Supports ad-hoc wifi only though.
Alternatively, if you can manually set the DNS resolver address your tethered-devices to something like 8.8.8.8, they'll continue to work with MobileAP that way.
Leviuqse said:
4g works
Restart your phone, turn on 4g, make sure is connected and start the mobileAP, it works with my stock rooted 2.1
the only thing is that if you get disconnected from 4g, it wont tether from 3g and vice versa
Click to expand...
Click to collapse
wait so can we use wifi teather and 4g? Didnt think it was possible?
quik99 said:
wait so can we use wifi teather and 4g? Didnt think it was possible?
Click to expand...
Click to collapse
I am using wifi tether and 4G right now.
Jayavarman said:
I am using wifi tether and 4G right now.
Click to expand...
Click to collapse
I use Wireless tether and 4G on a regular basis, and was just using it for a couple hours in NYC with 3 devices connecting to it. You can ABSOLUTLY use WIFI and 4G at the same time when using the phone as a access point. (shows up as a ad-hoc network just in case you were wondering).
I was hoping to have the phone broadcast an infastructure network so my ps3 can connect to it. MobileAP works with 3g, i changed my dns addresses to 8.8.8.8., so when i switch to 4g i dont get dns errors, but it still wont connect or load anything.
Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?
This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?
C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7
Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).
I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.
Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?
Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence
First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app
bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.
strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.
Bump.
Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app
Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.
Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!
its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know
bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).
For some reason I'm having trouble acessing google search/store while using my wi-fi connection, they just keep trying and eventually fails, the weird part is, this is only happening on our smartphones, google is working just fine on the PC(wired).
Anyone got any idea what this could be ?
PS: It also works just fine if on the 3G+
Hmm could be DNS being weird. When you get to WiFi try using terminal emulator and ping Google and try on 3g.
Sent from my Nexus 5 using xda app-developers app
change DNS address of your Router
I was having the same problem last month. I just changed my DNS servers entry to GOOGLE DNS servers address, and the issue was resolved.
Just go to your Router's configuration page, change your ISP (internet service provider) DNS entries to Google DNS addresses (8.8.8.8 and 8.8.4.4), and reboot your Router/Wifi hotspot. and voila, you will get the access.
AliRavian said:
I was having the same problem last month. I just changed my DNS servers entry to GOOGLE DNS servers address, and the issue was resolved.
Just go to your Router's configuration page, change your ISP (internet service provider) DNS entries to Google DNS addresses (8.8.8.8 and 8.8.4.4), and reboot your Router/Wifi hotspot. and voila, you will get the access.
Click to expand...
Click to collapse
That was actually one of the first things I tried heh, unfortunately that didn't seem to help much.
Anyway, I apologize for not giving an update earlier but it seems that as of today the problem somehow vanished...dunno why, but hopefuly it was temporary, maybe my ISP being weird ? Who knows.
That being said, thanks for the help MrObvious and Ali I appreciate it
I had similar problems. Only thing that cleared it up was a factory reset.
Sent from my SM-N900T using XDA Premium HD app
Yes, I think it was some temporary problem at your ISP end.
Is anyone else having tethering issues on MetroPCS or Tmobile with the MXP? I have tried applying various apn tweaks but I always experience DNS issues on the tethered devices. My device is bootloader unlocked and rooted if that even matters.
jovan123 said:
Is anyone else having tethering issues on MetroPCS or Tmobile with the MXP? I have tried applying various apn tweaks but I always experience DNS issues on the tethered devices. My device is bootloader unlocked and rooted if that even matters.
Click to expand...
Click to collapse
I am in the same situation and it sucks not being able to tether on metroPCS specially since my service plan of $60 offers free mobile hotspot up to 6GB to teher. The phone has potential but in the end I might have to return it if no tethering options are available.
Not even with root ? Just wondering
Sent from my XT1575 using Tapatalk
patt2k said:
Not even with root ? Just wondering
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Not even with Root and Bootloader unlocked.
That sucks maybe metro is blocking it somehow ?
Sent from my XT1575 using Tapatalk
Have you tried going to the store to get their information on this? I'm about to get this phone on t-mobile amd I hope this can be fixed, did you buy the phone at motorolas site? Because I seen the option to add your carrier sim with the phone if that even makes a difference as im assuming it doesn't, but maybe it has something to do with the imei not being registered to the network so I think you should stop by a store
I have not had any issues tethering with T-Mobile. Not rooted and bootloader is virgin locked.
Sent from my Nexus 10 using Tapatalk
Are you getting an error when turning on Hotspot, or just when a device connects it cant hit the internet. Its 2 different issues, but both are fixable.
Fix for Tethering
InfiniDroid said:
I am in the same situation and it sucks not being able to tether on metroPCS specially since my service plan of $60 offers free mobile hotspot up to 6GB to teher. The phone has potential but in the end I might have to return it if no tethering options are available.
Click to expand...
Click to collapse
Had to dig deep in the adb logcat to find the issue, the problem is DNS routing when using tethering . For tethering to work I had to use Wifi Tether Router.
Change the following for tethering to work:
Interface: wlan0
Method: Native tether
DHCP Settings : DNS Redirect checked
Redirect DNS to 8.8.8.8 and 8.8.8.4
SalTNutz said:
Are you getting an error when turning on Hotspot, or just when a device connects it cant hit the internet. Its 2 different issues, but both are fixable.
Click to expand...
Click to collapse
No problem on turning on Hotspot, other devices connect but no Internet connection. Hopefully some Devs show interest in MXP and pump out a fix or maybe even some ROM's.
Sent from my XT1575 using Tapatalk
InfiniDroid said:
No problem on turning on Hotspot, other devices connect but no Internet connection. Hopefully some Devs show interest in MXP and pump out a fix or maybe even some ROM's.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Also you may need to change your APN to use IPv4 and not IPv6.
The issue is the hidden tethering APN. T-Mobile is the only one that does this that I know of.
http://forum.xda-developers.com/showthread.php?t=1962752
jovan123 said:
Had to dig deep in the adb logcat to find the issue, the problem is DNS routing when using tethering . For tethering to work I had to use Wifi Tether Router.
Change the following for tethering to work:
Interface: wlan0
Method: Native tether
DHCP Settings : DNS Redirect checked
Redirect DNS to 8.8.8.8 and 8.8.8.4
Click to expand...
Click to collapse
@jovan123 Thanks for your help. I bought the Wifi Tether Router from the play store and followed your instructions at first it didn't work but I went over it a second time and shazam! right on the money.
InfiniDroid said:
@jovan123 Thanks for your help. I bought the Wifi Tether Router from the play store and followed your instructions at first it didn't work but I went over it a second time and shazam! right on the money.
Click to expand...
Click to collapse
No problem man. Can you let me know if your tether data is showing up in your data usage. Mine doesnt show up at all , maybe since its bypassing tmobile's DNS servers.
In case this helps any Metro PCS (who else does Hotspot for free?? Nice). I was so upset that I couldn't hotspot that I rooted and tried the WiFi Tether Router app and settings above (had used before on Sprint with success). Nothing worked.. I uninstalled and tried a few simpler things: I just modified the APN by adding 'dun' to the APN type line, and changed APN protocol to IPv4. Works great at LTE speeds. I don't think using then deleting WiFi Tether Router left some beneficial settings somewhere deeper; anyone know?
I have the same issue. A reboot fixes it for a short time only. I posted this on Moto forum and other people have having an issue. I know it's the phone because I put the sim back to my OPO and I can tether fine with it. I call t-mobile to verify that Hotspot feature is turn on. It's very annoying having to reboot again and again to use hotspot.
MetroPCS blocks ALL tethering for non-MetroPCS devices. That said, I have been tethering with MetroPCS since Day 1 using this guide:
http://pocketnow.com/2015/01/01/nexus-6-tethering
Summary:
Add tether_dun_required=0 to /data/data/com.android.providers.settings/databases/settings.db using a SQL Editor.
Change APN to IPv4
jovan123 said:
No problem man. Can you let me know if your tether data is showing up in your data usage. Mine doesnt show up at all , maybe since its bypassing tmobile's DNS servers.
Click to expand...
Click to collapse
I use the app but my WiFi is messed up after I turn off the tether. Have to reboot to resolve issue.
same problem here,i use simple mobile and computer connect to wifi but data is not transfering,i found that happens when lte when i have h+ or 2g tether ok...anybody know how to fix this ,i have no problem with asus zenfone 2
with 3 different roms, all I've needed to get fast LTE tethering is basically using IPv4 and adding 'dun'...
(all others "Not set")...
APN: fast.metropcs.com
MMSC: http://metropcs.mmsmvno.com/mms/wapenc
MMC: 310
MNC: 260
APN type: default,supl,mms,dun
APN protocol: IPv4
APN roaming protocol: IPv4