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.
My wifi is not working at all after I upgrade the firmware. It kept connecting and then get disconnected. Anyone got this problem?
Sent from my GT-P1000 using XDA App
bubblebob said:
My wifi is not working at all after I upgrade the firmware. It kept connecting and then get disconnected. Anyone got this problem?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
If it was me, I'd check to make sure you're broadcasting SSID on your router. For some reason, at least this is the way it is for me and I would be really baffled if it wasn't happening to everyone else as well, these android devices (I have an EVO and a GT), have a problem with connecting without it being able to see the SSID broadcast. All of my other devices (laptops, desktops, etc...) have absolutely no problems either way (broadcasting SSID or otherwise) connecting to my WiFi setup. Just the adndroid devices.
I had same problem not sure how i fixed it. But i reflashed everything like 1st time
I think it will b the modem file.
BUT check your wireless setting first
Sent from my GT-P1000 using Tapatalk
So I have noticed that as of late, when connecting to some access points, my xoom takes an excessivly long time scanning and authenticating the network, and will not connect. Other times it will connect in the correct fashion. I have verified pass code and IP settings. Anyone have advice?
Sent from my Xoom using XDA Premium App
I have seen the same thing on exactly one other wifi hotspot, while traveling. I thought it might be something in the way that the AP was configured due to the fact that my 1.6 phone would not connect either while my wife's Win7 netbook connected immediately. I thought that they must not ike Android.
Its possible the routers were out of IPs to assign. A common problem I find in hotels is that they set really long, or indefinate lease times and people come and go and they run out of IPs to assign.
Sent from my HTC Desire using Tapatalk
I think you may be on to it there.... the times I notice odd behavior is when a significant number of devices are connected...
Sent from my Xoom using XDA Premium App
So, I'm deployed right now and I got the N7 3G specifically so I could tether to my computer and phone. After getting the device and realizing that it did not have native tether I rooted it and flashed it with the image(?) I found here.
http://forum.xda-developers.com/showthread.php?t=1995737
Everything went smoothly and I thought I was good 2 go. When I attempt to log on with my devices I get a IP address conflict. My computer (WIN7) is smart enough to manually assign itself an IP and connect to the internet but nothing else will. It's driving me nuts. Obviously, I can only imagine that it is something to do with the DHCP. I would have posed this question on that thread but based on not having posted before I did not have the permissions. Thank anyone ahead of time for any help.
Still no luck. I've reapplied everything multiple times and nothing. I've also flashed the monoco(?) rom hoping that their tether would work but nothing. Only thing I haven't done is factory restore and start from scratch. This is really sucking. I'm looking for any suggestions. I'm sure 90% are more experienced then I am with this. I have absolutely no programing knowledge.
Sent from my Nexus 7 using xda app-developers app
Hmmm. Yea its DHCP from your Nexus handing out IPs. I'm not sure what your DHCP RANGE is but it should be a pool of about 10 IPs. If your Range is only set to 1, then it will only hand out one.
Oddly there aren't any options on my Galaxy Nexus (I don't have a 3G N7).
What I would do is take your other devices and tap and hold on your tethered WiFi network and select forget. Disconnect everything completely and forget all settings. Change your WiFi Tethered name.
Try to connect one at a time before moving to the next. The devices keep the connection settings in memory and will try to use the old IP address they used before.
This could also be a bug with the tether section also. Most roms share the same development features.
Sent from my Nexus 7 using XDA Premium HD app
No luck
Sent from my Nexus 7 using xda app-developers app
hi, I just got a Galaxy note 4, I can connect to wifi everwhere but not at work. I get error that password is incorrect, I have the same password so I know my password. My stepson has a galaxy s5 and has no problem connection. I actually just returned my first phone after trying 5 days to get it connect at work. Both Comcast box and firewall have been reset. So I am not sure where to go stepson suggest change to developer operating system. I have tried safe mode, soft reset and factory reset to no luck.
This is last resort - before I return and get a different brand/model phone
if you can connect everywhere except work its your work problem. some workplaces use cisco and proprietary protocols to login to wifi after connection. if your workplace does that you will not be able to connect. no phone will. ask your work wifi to use WPA2 with AES instead of some proprietary protocol for wifi. if your son has installed some non standard rom to get his s5 to connect you will need to buy an s5 and do the same.
snowmmk said:
hi, I just got a Galaxy note 4, I can connect to wifi everwhere but not at work. I get error that password is incorrect, I have the same password so I know my password. My stepson has a galaxy s5 and has no problem connection. I actually just returned my first phone after trying 5 days to get it connect at work. Both Comcast box and firewall have been reset. So I am not sure where to go stepson suggest change to developer operating system. I have tried safe mode, soft reset and factory reset to no luck.
This is last resort - before I return and get a different brand/model phone
Click to expand...
Click to collapse
It is very likely that your work uses wifi protected setup. You need access to router or access point to finish setup. Ask your IT guys to help you. It needs to be done once only.
Sent from my SM-N910T using XDA Free mobile app
response from IT
darekz said:
It is very likely that your work uses wifi protected setup. You need access to router or access point to finish setup. Ask your IT guys to help you. It needs to be done once only.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Response from my IT guys - -they are very helpful since this is a personal phone and not company issued.
I don't have a good reason for this one device to have a problem connecting to this one network. I believe we have eliminated common errors such as mistyped or incorrect password, since you have personally been able to connect other devices without issue. This also eliminates the possibility of a 1-time setup or authorization requirement, as you did not need that for the other devices. I will need to look into whether there could be a technological incompatibility between the two devices.
We will look into this further and have to get back to you.
response
zurkx said:
if you can connect everywhere except work its your work problem. some workplaces use cisco and proprietary protocols to login to wifi after connection. if your workplace does that you will not be able to connect. no phone will. ask your work wifi to use WPA2 with AES instead of some proprietary protocol for wifi. if your son has installed some non standard rom to get his s5 to connect you will need to buy an s5 and do the same.
Click to expand...
Click to collapse
We have a WPA2. We have people come visit all the time and have them connect.
I am just wondering in there is something in this phone operating system that is more technological updated than the systems we are using and could be the problem
I still would try to use Wifi Protected Setup. It is software depended and Note 4 is capable of using WPS while many others not. It is possible that software in Note 4 sensing that access point has that feature and requesting it. Im not network specialist but I setup few laptops for my friends. They were using Dell Vostro laptops and by default they required using WPS to connect to home network. Once that feature was disabled they connected with no problem using user password.
Sent from my SM-N910T using XDA Free mobile app
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Maybe that be any help for you.
http://www.samsung.com/us/support/faq/FAQ00057286/74370/SM-N900VZKEVZW
Sent from my SM-N910T using XDA Free mobile app
snowmmk said:
We have a WPA2. We have people come visit all the time and have them connect.
I am just wondering in there is something in this phone operating system that is more technological updated than the systems we are using and could be the problem
Click to expand...
Click to collapse
not possible since i have connected to both WPA2-PSK AES and WPA2-EAP AES systems. EAP requires a username/password instead of just a password.
the only system i have not been able to connect to is a WPA-CKIP and WPA2-CKIP which is a cisco proprietary protocol.
connection made
darekz said:
I still would try to use Wifi Protected Setup. It is software depended and Note 4 is capable of using WPS while many others not. It is possible that software in Note 4 sensing that access point has that feature and requesting it. Im not network specialist but I setup few laptops for my friends. They were using Dell Vostro laptops and by default they required using WPS to connect to home network. Once that feature was disabled they connected with no problem using user password.
Sent from my SM-N910T using XDA Free mobile app
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Hi all,
My Phone has connected to the company wifi. I was searching for an infinity hot spot since I am an infinity customer and was scanning and then I am connected to the company wifi. Then it began to do all these updates and I did nothing to prompt this. (weird since it can connect at home and this did not happen) I have been in contact with Samsung and have been explaining my issue - part of their process is you need to enter model and serial number- is it possible for them to track my phone - I am wondering as when I have called HP for service they can find my laptop. Very weird, but I am happy, Hopefully it will continue to work like this and I can begin to use this phone to its full potential.
yes samsung and google can both track your phone.