Hi, everyone,
I've met a strange problem these days.
I'm always following the CyanogenMod ROM and it's really nice, however, I met this "wifi cannot obtain IP address" issue on CM4.0.4 and some experimental CM builds(using donut 1.6 core)
I'm using D-link at office and TP-Link at home.
TP-Link works fine, D-Link worked fine and i cannot specify from which version of CM Build, the G1's WiFi met the "Cannot obtain IP address" under D-Link Router.
Here's the information of my G1.
T-Mobile G1, Rooted. using CyanogenMod CM4.0.4 ROM, radio and SPL are all updated.
Is there anyone who has solved this?
Thanx!
Delete and try again. I had that once at my folks place on vacation. Just had the wrong freaking password.
nope, im sure about that i entered the right password.
thank u anyway
nope, im sure about that i entered the right password.
thank u anyway
Might be the security on the router. You need to set to "WPA2 Only" on some routers. Some will work with WPA/WPA2, but others will only work with WPA2 so give that a try.
h.nocturna said:
Might be the security on the router. You need to set to "WPA2 Only" on some routers. Some will work with WPA/WPA2, but others will only work with WPA2 so give that a try.
Click to expand...
Click to collapse
now both of the TP-Link and the D-Link routers are under WEP mode...
Will WPA/WPA2 works?
I'll give it a try.
thanx.
Related
I don't know if anyone uses the open source DD-WRT firmware for their router, but it does not appear to work with WLAN on the wing. The wing recognizes it correctly, but, if I try to connect, it just attempts to connect for a little bit then gives up. It thinks I have a bad password but I've triple and quadruple checked that the password and encryption is right. Any ideas on a work around or a fix?
I am running DD-WRT V23SP2. Not having any problems with my Wing and WLAN.
However I am not using any encryption. I am just using MAC address athentication.
alben said:
I am running DD-WRT V23SP2. Not having any problems with my Wing and WLAN.
However I am not using any encryption. I am just using MAC address athentication.
Click to expand...
Click to collapse
It probably does have to do with the encryption then. We decided to put the old linksys firmware back on but thanks for the response.
I have also used my Wing with a Linksys WRT-54GL router running DD-WRT V23SP2 that uses WPA with a preshared key. No problem. Wing connected immediately once the key was put in.
my brother gets Artemis (p3300) with an official WM5, and when we turned WEP on on our router, his Wifi doesnt want to connect.... even when entering pass.... so we have it on Mac adres and works perfectly
I've been running 6.1 ROM (Official) now for a month or so and am using a program on my Tilt that uses a lot of data...so while I'm at home I thought I would allow it to use my WiFi router instead of my 3G connection.
I turned on the WiFi and it can "see" my router's SSID. I enter the WPA-TKIP passcode and tell it to connect. It just sits there saying "connecting to network" but never completes the connection to acquire it's IP.
I have even gone as far as setting the IP configuration manually (Static IP) and the TILT keeps trying to connect to the network.
I have a DLink DI-624 that I have had no problems connecting the WiFi when I was running ROM 6.0.
I have done the following in trying to troubleshoot:
- Turned OFF Turbo on the Router
- Configured router for AutoChannel
- Configured TILT for Best Performance
- Rebooted Router AND TILT.
Still no go...Ideas?
I sometimes get this after flashing a new rom. It seems to affect the way it connects to WPA networks but not WEP or unsecured.
You can try changing your security to WEP and see if that works.
But when I need to solve this I usually have to do a Hard Reset and then connect the WIFI first. When it does this the phone seems to be able to auto-detect the network type (i.e without me needing to select it as WPA) and after entering the passcode it can connect.
Yep, go to WEP, this should be enough for most people and has never given me a problem.
martythebrit said:
Yep, go to WEP, this should be enough for most people and has never given me a problem.
Click to expand...
Click to collapse
Unfortunately I can't change my network to WEP. My network is not only my home network but also used for my wife's business...so for security reasons I have to keep the security up.
Drop the security just for a test and see what happens.
I am using the official ATT 6.1 ROM and it works just fine on my wifi, first with WPA-PSK then with WPA2-PSK. You could set your WAP to WEP (say that fast 3 times!) for a 5 minute test and see if it connects. Does your phone connect to other Wifi hot spots? What does ministumbler say about wifi in your area? You may have some interference with a neighbors wifi.
Well...I know that my issue is not limited to my router at home (DLink DI-624). I'm experiencing the SAME issues at work as well.
At work I'm using a NetGear WGT624 v3.
- The security is WPA-PSK (TKIP)...just like at home.
- Broadcasting SSID on Channel 11 (Fixed). There are no routers in nearby offices (I've checked using a wifi scanner on my laptop).
- I've configured a static IP in my Tilt and it just sits there at Connecting...again same as what happens at my house.
- I have also tried using DHCP with no joy.
I'll try the WEP at home to see if it's a WEP/WPA issue.
Unfortunately if it IS an issue...I don't think I'm going to get much joy from HTC on releasing a fix. Maybe there will be some way around it though...I hope!
Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine
brynwall said:
Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine
Click to expand...
Click to collapse
Here is what I have set in my TILT...
Connects to: The Internet
Hidden network: NOT checked
Ad-Hoc: Unselectable (Grey)
Auth: WPA-PSK
Encry: TKIP
Use IEEE: Grey (Non-Selectable)
EAP: Grey (Non-Selectable...but Smartcard or Certificate IS in the box)
(Still at work...will test WEP when I get home)
(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?
At least you know
And Knowing Is Half The Battle
clstan said:
(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?
Click to expand...
Click to collapse
Is a backing up everything and doing a hard reset too much hassle? Make sure you connect to a WPA Wifi first before installing any other programs. Its the only way I could fix it... =/ As recommended I always do another hard reset straight after flashing a new rom now.
Hey...someone...somewhere has mentioned that there might be a WPA issue in relation to removing the AT&T Bloat. Is there anything to this? I HAVE removed my bloat on my Tilt.
I don't want to have to re-Hard my Tilt...but will if I have to...but only as last resort.
What fixed with my DI-624
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.
segaza said:
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.
Click to expand...
Click to collapse
My home router is a DI-624 Rev E. The ONLY Firmware for the E Rev is 5.00 and I'm running it.
Even though not completely secure...my WPA password is a 20 character, lower case entry...no strange characters or whatever.
*Well folks...I had just installed the 6.1 Rom onto my Tilt about a month ago...so I don't have that much installed...and I can always reload it. So I HardReset and followed by removing bloat. WPA WORKS NOW! (Insert "Twilight Zone" theme music here.)
All in all...it just seems strange to have to HARD Reset my phone to get something like this to work again.
I am having problem accessing my internet connection through my wireless router. Everytime, i tried to connect my G1 to my SSID, it says obtaining IP address then it says unsuccessful.My wireless router is a LinkSys 802.11N with WPA encryption. I did some research and the G1 only accepts 802.11b/g routers? Is that true?
that could be true since it runs on 3G network... just go buy a new routher. i use my FiOS and there is 802.11g router
A N router should be able to trasmit to G adapters. At least thats how it is with linksys routers. No need to even go get a new router . Look under the settings and see if its just broadcasting N or if can Do N and G.
Had this problem. Change your security to WPA2 Personal Only, not WPA1. Should fix it.
h.nocturna said:
Had this problem. Change your security to WPA2 Personal Only, not WPA1. Should fix it.
Click to expand...
Click to collapse
x2
Thats what I had to do. Please specify more information on what ROM your using. Different ROM's have different Wifi drivers
hi folks, im running cm6 with wildmonks 2.6.34.4-925mv cfs svs aix 720p kernel with the 5.08.00.04 korean radio.
my work has a wpa2 aes encrypted wireless network setup. phone sees the network, and even accepts the password, but never gets an IP address. it hangs at obtaining IP address for a few seconds, and then goes to remembered, not connected, and back to obtaining IP address. it will cycle like this if i leave wifi on all day, and it never connects.
thoughts? the IT guy says its the phone... as he hasnt had trouble with other wpa2 spec'd devices. something im doing wrong, or is he wrong, or should i go back to frf to see if that works, or try a different radio?
assistance greatly appreciated.
thanks.
By the looks of it, it never actually connects. Double-check that you enter the correct password.
I have WPA2-AES set up at home, and it works fine.
Sounds exactly like the issue I had with the router in my parents house. My phone just didn't get on with that particular router. They upgraded recently and all is well.
pw is good. still wont connect. not sure why. i have no troubles connecting to cisco equipment in other places, and so im not sure thats the issue either. other suggestions?
Jack_R1 said:
I have WPA2-AES set up at home, and it works fine.
Click to expand...
Click to collapse
what rom, kernel, and radio are you using?
WPA2 Enterprise was broken when Froyo hit, currently some of the roms fix it, the latest CM6 fixed it I think (kinda). Other roms are planning to have fixes in the near future.
nexusonemeover said:
what rom, kernel, and radio are you using?
Click to expand...
Click to collapse
Enomther's 2.11.3 with its 720p AudioMod kernel, radio 4.06.
One router is Linksys WRT54GL, the other is WRT54G2 (2 places - mine and parents'), both are converted to DD-WRT firmware.
have you tried using the kernel that comes with CM6 to see if it works with that?
figured it out... i had the wrong gateway address entered... d'oh! :-(
good now. thanks for the thoughts on what to try though.
hello.
i have an adhoc with aes security at home.my laptop connects to internet via wireless. but the X1 phone cant.
rom 1.05.931.10
radio 1.14.25.55
kernel:i cant find kernel
when i am setting the wireless on the phone:
1.authentication:wpa-none
2.data encryption:aes
3.set password
4.click next
5.in the next page(configure network authentication) every thing is disabled
6.click finish.
7.does not connect
please help me
Hi All,
I have a weird problem with my captivate of not connecting to my home network. Let me start by telling that I have searched the solutions and tried doing everything except full factory reset. I have rebooted the phone, done reset on my router (Wifi was working just fine earlier.. so I think settings was not an issue. But I still did it), I removed the file data/wifi/bcm_supp.conf and let it regenerate it. Captivate displays "Obtaining IP Address" and it just stays there. I also see that IP address is being assigned to captivate in my router
Captivate is rooted stock Froyo
Router security: WEP
form the Wifi list, I found one unsecured network and captivate connects to that router just fine (signals are very week though...). I tried removing the security on my router but it still stuck on "Obtaining IP address".
Can you please please help me?? As I mentioned earlier, It was working just fine and suddenly stopped working two days back.
These all app updates are eating away my limited data of 200M.
Thanks a millian.
What's your router model ?
What channel are you running on ?
Are others routers close to you running on the same channel ?
Have you tried another channel ?
Did you try WPA2 ?
Could be incompatibility with your router. That happened to me before with my old router. It didn't work with some cell phone wifi devices.
Sent using XDA App
Try using the app "FXR." I had the same issue a couple times and this app seemed to fix it. It took a few tries though. I think it might be a router problem. I use the Linksys wrt54g.
You could also try assigning a static IP address to your device on the router side, and then telling your phone to use that address. I've used that in the past to some success.
As a test, have you tried (temporarily) disabling the security on your router to see if it connects?
I have a similar problem since upgrading to the past 3 nightlies. My phone sees and connects to my home network and says it has strong signal, but when I try to access Market or Internet it says there's a network error and I can't get thru. My two computers (one hard wired and one wi-fi) don't seem to have any problem hooking in to the internet, just my SGS1
Moozh1 said:
Try using the app "FXR." I had the same issue a couple times and this app seemed to fix it. It took a few tries though. I think it might be a router problem. I use the Linksys wrt54g.
Click to expand...
Click to collapse
Does the 'FXR' app set up IP addresses?
The App didn't work for me. I tried that yesterday. I was reading the similar problems on some other site yesterday and I found the following that solved my issue. In case someone like me still struggling with the WiFi problem.
Delete file data/wifi/bcm_supp.conf
Delete file /data/misc/dhcp/dhcp_list
reboot the device and it will create these files again and you will have to enter your WiFi password again in order to connect.
I am really glad that my WiFi is working back again.
FYI, I'd change the WEP to WPA.
cappysw10 said:
FYI, I'd change the WEP to WPA.
Click to expand...
Click to collapse
Where do you go to change that setting? I've been all thru the wi-fi settings and advanced settings, but didn't see anything that referred to WEP or WPA.
Just realized we're talking now about the router, not the phone, duh!
Yes, I certainly need to bump up the security settings on my router.
cappysw10 said:
FYI, I'd change the WEP to WPA.
Click to expand...
Click to collapse
22andy2 said:
The App didn't work for me. I tried that yesterday. I was reading the similar problems on some other site yesterday and I found the following that solved my issue. In case someone like me still struggling with the WiFi problem.
Delete file data/wifi/bcm_supp.conf
Delete file /data/misc/dhcp/dhcp_list
reboot the device and it will create these files again and you will have to enter your WiFi password again in order to connect.
I am really glad that my WiFi is working back again.
Click to expand...
Click to collapse
I used root explorer, but could not locate the files you mentioned. Directories were there just not files. I'm still exploring the router side. Thanks for the info tho.