Related
Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.
Wow. Am I the only one on here who's having this problem?? Lucky me, I guess... :S
Anyway, I just tried connecting to a public and open wifi network here in SF, but my Kaiser still wouldn't connect. Guess that confirms it: my WiFi adapter is defective.
Anyone know if I can get it replaced in a different store from where I purchased it, and what I need to take (hope it's just the phone)?
d0ubl3_d1zzl3 said:
Wow. Am I the only one on here who's having this problem?? Lucky me, I guess... :S
Anyway, I just tried connecting to a public and open wifi network here in SF, but my Kaiser still wouldn't connect. Guess that confirms it: my WiFi adapter is defective.
Anyone know if I can get it replaced in a different store from where I purchased it, and what I need to take (hope it's just the phone)?
Click to expand...
Click to collapse
just tried my wifi on the tilt ... works fine out of the box (to my home secured wireless network)
d0ubl3_d1zzl3 said:
Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.
Click to expand...
Click to collapse
This is what I did. Start->settings->connections tab->WiFI. Now you should see your routers name there with the signal bar next to it. Tap AND Hold the name, then go to settings or edit(I forget), then click NEXT, uncheck the box that says "the key is automatically provided"(thats for open access routers/networks that dont require codes). Then type in your code & make sure you specify what key # it is. click next and youre done. You should be able to connect.
silly question here. is your router broadcasting 802.11b or g? the wifi won't connect to anything else.
You might also check your AP to see if it's not broadcasting its SSID to the world (a common security setting). I couldn't connect until I enabled broadcast on my AP, set the network up, and then went back and disabled SSID broadcast.
Why in the hell this is a problem in the first place is beyond me, but this is the third smartphone/PDA with wireless that I've had to do that for. And every time, once the device found the network once, it never had a problem finding it again.
Believe me. I tried everything in the WiFi settings page. I edited the settings, removed them and added them again, and like I said before I even went and changed my security settings on my router (which to answer your question, zeta, it broadcasts in: n, g, and b. Same router worked with my Apache/XV6700).
Anyway, I stopped by the store where I bought it today and they told me that as far as he can tell, that does qualify for a replacement. The problem is they don't have any in stock to replace it with, and he has no idea when they'll be getting more in. They only received 2 on launch day, and I bought one of those. He did mention that I can get it replaced at any store, however, but they all might be in the same boat.
Guess I'll try another store tomorrow, but if not I guess I'll have to go through AT&T's tech support (don't like the sound of that) and get it replaced through them. So I guess this means I might have a few days to mess around with the phone and even try some risky thangs.
So if any of you developers and hackers, er, I mean tweakers need some1 to test something, I can be that guinea pig (for a while at least)... Just give me a shout.
To troubleshoot your wireless connection always try ruling out as many other factors as possible. So put your router to NO security (temporarily ofcourse) and have it broadcast 802.11g. Also make sure you add the mac address of your device to the list in your router, if it uses mac address filtering. Try connecting to it with a laptop and see if that goes fine. Work systematically...
PerfAlbion said:
You might also check your AP to see if it's not broadcasting its SSID to the world (a common security setting). I couldn't connect until I enabled broadcast on my AP, set the network up, and then went back and disabled SSID broadcast.
Why in the hell this is a problem in the first place is beyond me, but this is the third smartphone/PDA with wireless that I've had to do that for. And every time, once the device found the network once, it never had a problem finding it again.
Click to expand...
Click to collapse
I have a similar Problem, your solution works partly for me:
As soon as I enable the AP to broadcast it's ID, Kaiser connects.
But as soon as the ID is hidden, it does not connect.
Weird.
Is it a security problem if the ID is broadcasted, provided I use WPA2-PSK/AES?
Thanks
V
No. Hiding the SSID really only protects you from folks that are wandering around without any tools. Open up a more fully featured scanner, and it'll pull the SSID out of the air. The encryption is much, much more important.
And I also wouldn't bother with MAC filtering. Changing the MAC address is usually a software setting, so it's not all that much additional security. WPA/WPA2 are much better solutions.
Yeah, the hidden SSID is not an issue with me, since I don't mind broadcasting it at home. Not too paranoid about it. If someone *really* wanted to sniff and break into my network, they could. Don't do much important and highly confidential stuff at home anyway.
Plus, like Perf mentioned, there's software out there, even for PocketPCs, that will find so-called "hidden" SSIDs. Thanks for your suggestions, anyway.
d0ubl3_d1zzl3 said:
Yeah, the hidden SSID is not an issue with me, since I don't mind broadcasting it at home. Not too paranoid about it. If someone *really* wanted to sniff and break into my network, they could. Don't do much important and highly confidential stuff at home anyway.
Plus, like Perf mentioned, there's software out there, even for PocketPCs, that will find so-called "hidden" SSIDs. Thanks for your suggestions, anyway.
Click to expand...
Click to collapse
i had no issue connecting to my wrt54g running DD-WRT v23 SP2 with my SSID hidden with WEP enabled. when setting up a new connection, i just entered the name of the connection and then the WEP hex, and it connected flawlessly. Have fun hacking your phone until you can swap?
Mine is not working either. I exchanged the phone and found out that I was the 3rd person with the same problem.
BiPolarXpress said:
Mine is not working either. I exchanged the phone and found out that I was the 3rd person with the same problem.
Click to expand...
Click to collapse
Glad to hear, I'm not the only one.
I exchanged my phone this morning, and I just tried connecting to my wireless network and guess what??
I'm getting the SAME RESULTS.
Now, before anyone goes and tells me that my router is the problem or that it's user error, then tell me: why does my laptop, PS3 and my Wii connect just fine?? I even changed the SSID and WPA key last night and they all connected w/o a problem as well. All except my freaking Tilt.
Can be it a coincidence that I got 2 bad phones? I don't know if I should call the store and tell them to hold up on sending the other phone to HTC.
Which reminds me, I probably should try calling HTC today, but I doubt they'll be much help...
I don't think you're nuts, and I doubt you got two bad phones. But if you want to double-check, take the phone to your local Starbucks or other shop with WiFi and see if it can detect that AP.
But at this point, I'd be inclined to look for a firmware upgrade for your AP. I could be that it's not supporting long or short preambles right (a problem for some devices in the past), doesn't like seeing more than XXX different devices, or just doesn't like your phone much.
Either way, I'm smelling an issue with your AP. I had a US Robotics AP/Router that drove me nuts because it would spontaneously reboot after a random period any time an IPSec VPN was present.
try setting the power mode on best performance. when i do that i stay connected to wifi.
I took both my old I730 and my tilt to the coffee shop before I returned my first tilt. I was able to connect my I730 at the coffee shop and home, but couldn't connect the tilt at either place. I also tried some open AP's in my neighborhood that I have been able to connect to in the past with the same results. Picky phone or bad wifi radios maybe.
Jesus... like the bloke said:
1) Turn off wpa and see if it will connect (it will unless you have set your N router to only use "n") If it won't then send it back.
2) If it does... then turn on WEP 128bit on your router... and use that instead.
WM devices have always had problems with WPA...
Hi all.
I have tried my HTC TyTN II with one Wifi LinkSys WAG54GS Router using WPA and not hidding the SSID and works fine, no problem at all.
Test with one AP from DLink at the office, using hidden SSID and WEP 64 and 128 Bits and no problem at all, works as fine as my LinkSys.
I'm going to try hidde the SSID at home with WPA and WPA2 and post the results later to know if there is a common issue with Kaiser or some freaky coincidence.
Regards.
d0ubl3_d1zzl3 said:
Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.
Click to expand...
Click to collapse
I found that I couldn't get my Kaiser to connect to my WPA encrypted LAN - open access and WEP (64 and 128 bit) work fine.
Not sure what the problem is - maybe some incompatibility between the Kaiser and my Netgear router. I've downgraded the security to 128bit WEP for the time being but I'm hoping that there's a fix soon.
Well I've had my Captivate for 3 months, and up until now it's been smooth sailing. Two days ago I came home and my power was off, and when it came back on I tried connecting to my router like usual, but now it won't connect. On the "wifi settings" menu it just says "obtaining ip address from..." for a few seconds then it says "disconnected" and goes back into "scanning..." mode. Also, under the "wifi networks" section it shows my network as "Disabled, secured with WPA/WPA2 PSK". (I am using a Linksys WRT54G with WPA2 security f.y.i.)
I've tried "forgetting" the network, I've deleted the whole file that remembers your networks, I've tried connecting via WPS button, I've double checked my password, I've power cycled my router, I've reset my router back to default and re-configured it...still nothing. It connects to the wifi on campus with no problems (in 4 different buildings), so obviously there is something wrong with my router setup.
If anyone has any advice on how to resolve this problem, it would be much appreciated!
**Also, I forgot to mention I am running Cognition v2.2 Beta 6
Bump for hope
Does anything else connect to your router
Sent from my SAMSUNG-SGH-I897 using XDA App
M3MPH1S said:
Well I've had my Captivate for 3 months, and up until now it's been smooth sailing. Two days ago I came home and my power was off, and when it came back on I tried connecting to my router like usual, but now it won't connect. On the "wifi settings" menu it just says "obtaining ip address from..." for a few seconds then it says "disconnected" and goes back into "scanning..." mode. Also, under the "wifi networks" section it shows my network as "Disabled, secured with WPA/WPA2 PSK". (I am using a Linksys WRT54G with WPA2 security f.y.i.)
I've tried "forgetting" the network, I've deleted the whole file that remembers your networks, I've tried connecting via WPS button, I've double checked my password, I've power cycled my router, I've reset my router back to default and re-configured it...still nothing. It connects to the wifi on campus with no problems (in 4 different buildings), so obviously there is something wrong with my router setup.
If anyone has any advice on how to resolve this problem, it would be much appreciated!
**Also, I forgot to mention I am running Cognition v2.2 Beta 6
Click to expand...
Click to collapse
Happened to me a few times. Only way I could get out of this was to restore to a previous backup, or install fresh again. By the way, I experienced this problem only on 2.2. Never happened on 2.1.
fatttire said:
Does anything else connect to your router
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Unfortunately I don't have anything else with wireless to test.
Elaborating on the issue
I've encounter exactly the same problem described here.
Samsung Galaxy S I9000. Froyo (official version). Not rooted.
Now it is the first time it has happened, and still I have not found a solution (restarted the router, restarted the phone and made more tests).
Before the upgrade to Froyo it has never happened. After the upgrade it worked ok for several days untill now.
Several other deviced at home are well connected to the router.
Its just s stupid suggestion maybe... but have you tried to change channels with your router?
Sometimes is just a stupid channel issue....
I found out the answer to this problem. I had to connect using static addressing. It seems at some point, the captivate 2.2 roms get confused for some of us and it starts trying to assign an IP address already used.
In my case, I tried everything... rebooting phone, router, ect.
Laptop connects fine, Wii connects fine...
But, I decided to connect via static addressing... BAM connected perfectly and instantly.
Connecting to other DHCP networks seems to be hit and miss as well.
So, I'd suggest reflashing might be the overall fix. But if you're like me and cannot reflash right away, try static addressing till you can get around to it.
yukinok25 said:
Its just s stupid suggestion maybe... but have you tried to change channels with your router?
Sometimes is just a stupid channel issue....
Click to expand...
Click to collapse
Not stupid at all, but unfortunately yes, I tried a couple different channels and still nothing.
DigitalEagle said:
I found out the answer to this problem. I had to connect using static addressing. It seems at some point, the captivate 2.2 roms get confused for some of us and it starts trying to assign an IP address already used.
In my case, I tried everything... rebooting phone, router, ect.
Laptop connects fine, Wii connects fine...
But, I decided to connect via static addressing... BAM connected perfectly and instantly.
Connecting to other DHCP networks seems to be hit and miss as well.
So, I'd suggest reflashing might be the overall fix. But if you're like me and cannot reflash right away, try static addressing till you can get around to it.
Click to expand...
Click to collapse
Awesome! This sounds like a promising solution, thanks. Yeah I need to reflash soon anyway seeing as how Cognition is up to 2.4.x already...
Probably won't be tonight, but I will do this soon and let you know my results.
Alright, I have typed just about every keyword into google relating to setting up my router/phone to use a static IP and for some amazing reason there are ZERO results that have any information whatsoever about setting up a static ip on a phone. This is really frustrating, so if anyone would be kind enough to explain how to do this or link me somewhere that does, that would be awesome
go to your wi-fi settings and click the menu button.
it should pop with a "scan" and "advance"
click on advance and scroll down to "use static ip address"
then i guess you have to put in your network details, not sure on the details there cause i have done it but experiencing same problem with my galaxy s
power went out and now can't connect to my network
Edit : Possible fix
I just managed to connect to my network.
I put the device in flight mode and restarted my modem at the same time
put it out flight mode and pluged in the modem again and now works.
Hopefully that works for you to guys.
Yea, works perfectly. I have my laptop connected to it right now. I usually have to reset the phone to get wifi again.
edit: I set it to static ip, but then i got the same problem. Except now google search engine works No webpage opens, youtube app didnt work either.. only the search engine worked.
Well my phone must be in a good mood today because it just decided to start working again all on its own! I don't know what caused it...I have actually had both my phone and computer constantly on since this started happening. So for now I'm keeping my fingers crossed and hoping it doesn't mess up again.
This is probably just for me, but this isn't a viable solution.
The ONLY router I seem to have this issue with is the one that Verizon gives all it's FiOs customers. It's the Actiontec M1424WR Router/Modem. I know my WEP key is correct because it works just fine on all the laptops and other phones (a Palm Pre and another Captivate on 2.1). It tries to obtain an IP address for about 5 minutes and then just sits and says disabled. Does anyone know if there's a way to dump the DNS cache or whatever like you can on Windows?
Add me to the list of ones having this problem...guess I'll try to reflash everything in a bit to see if that fixes the problem.
Just an update I backed up everything using Tibu and then just restored it and my WiFi problem went away.
Mine is stock and just started having this problem....will connect to other wireless routers except mine, really pissing me off!
I've tried many times having the the phone "forget" me, then put in my password(which is correct)...same thing over and over.
Same problem here
I have a galaxy s and the recent update to froyo brought me the same problem already described here.
And the "funny" thing is that my router doesn't have an Static IP option, it's a simpler router from the cable provider.
So i'm trying also to find a solution to this. Two days ago i changed the wifi channel and it worked. But today i have again the same problem and changing the channel don't work anymore.
Each time i find a possible solution, it only works one time.
This is really annoying me. This must be a froyo bug, 2.1 never gave me this problem
pedroc2009 said:
I have a galaxy s and the recent update to froyo brought me the same problem already described here.
And the "funny" thing is that my router doesn't have an Static IP option, it's a simpler router from the cable provider.
So i'm trying also to find a solution to this. Two days ago i changed the wifi channel and it worked. But today i have again the same problem and changing the channel don't work anymore.
Each time i find a possible solution, it only works one time.
This is really annoying me. This must be a froyo bug, 2.1 never gave me this problem
Click to expand...
Click to collapse
It must be a froyo beta bug. Remember we don't have a final version of this firmware for the Galaxy S family.
Sent from my Captivate
Hi I think this is probably my first post on here
Just got a galaxy note in UK on three network
Netflix is working fine on 3G connection
but as soon as I try to use it on wifi it won't even log in, let alone stream anything
which sounds completely the wrong way round to me (if anything i'd expect more problems on 3g/data than wifi)
I have contacted netflix once about this already - being new also to netflix in the UK, I was impressed with the freephone help line number and bright happy service I was given but the suggestions did not work (I had already tried many of them myself)
I have tried rebooting device
logging in on 3g work and streams then while playing it seems to continue streaming if i turn on wifi (but thats not a good workaround)
If i log in on wifi I don't get past the netflix app login screen
Have reinstalled the netflix app
no luck
Have fixed the ip of the phone and set it in DMZ on router - still no luck
Have forwarded ports 80 and 443 to ip of phone - no luck (on advice from call to netflix)
So any suggestions are welcome please
Wifi works fine for all other apps, web browsing etc
(My galaxy note is unlocked and was not bought on three.)
ok have now done a complete factory reset of phone
only updated gmail
not installed any other apps
setup wifi - tried 2 diffent access points I have by different manufacturers
try netfix app on wifi - login timeout
on 3g only - still fine and ok
i have an archos 80 g9 device here also and get the same problem
tried the ipad (original ipad) app and all fine on wifi on that
have tried clearing app's data and cache
still not chnage - still will not work on wifi (only 3g)
starting to think this is a problem with the app as get same issue on archos
timosmusic said:
starting to think this is a problem with the app as get same issue on archos
Click to expand...
Click to collapse
Just an FYI, but Netflix works fine on all my Android devices over WIFI (and 3g where applicable), so I suspect it is probably something to do with your router.
Regards,
Dave
Sent from my GT-P7510 using Tapatalk
thanks for the reply
I had thought either the same or that maybe being a fairly new device
the app had a problem with the galaxy note
but as i get the same problem on the archos I'm now thinking it must be settings on the router - even though I have never had any other problems with any other device/app (as i say the ipad works fine)
Any one any ideas what on the router may be the cause of this?
I have another router I will test with as I have tested on a neighbours connection and all was OK (different ISP and router manufacterer)
but would like to know what the problem is
rather than just blindly buy new routers until the problem is fixed.
just to update with what has happened on this
in case anyone else is watching the thread...
I have now setup another router
and all is working
so obviously there is either minor flaw in the buffalo router firmware i was using
(although it is a model with no updates at this time)
or there was a setting somewhere causing the problem
If anyone has any clues as to the setting it may have been causing the issue
can you please post as I would like to know the answer rather than just move on and forget that i ever had the other router.
thanks
Hi all.
I had the same problem with my SGS II on my Netgear router (from Orange UK).
All was OK with Netflix, until I was re-configuring my network after my TP Link range extender started playing up. The network was originally on Wireless G, but I changed the security settings, the network ran Wireless N. Everything seemed OK, but it seems that my PS3 had a little trouble connecting to the internet, and definitely Netflix, and on the SGS II I couldn't connect to Netflix at all, either via web or via the app.
I change back to wireless G tonight and all seems OK.
Hope this helps someone out, as I was trawling the web searching for answers myself.
I plugged in the Chromecast and put in all the information and waited while it tried to connect to my Actiontec router. (Verizon FIOS) I waited, and waited and waited. After about 10 minutes it goes back to the beginning. The help button says I need to turn off the Access Point Isolation on my router. Unfortunately there's no such setting. I'm not happy because I have 3 more of these coming tomorrow and if I can't connect to my network I'm shot. Panic starts to set in.
Luckily, I have a cheap $30 Fry's wifi router on my network. I switched the Chromecast to the Fry's router and, bam, it connected immediately.
So, if your cable company's router doesn't work, just go out and buy a cheapo wifi router and you'll be fine.
The joy that is reading Verizon FiOS/Actiontec entrails
Deep voodoo Actiontec solution: You need to disable the IGMP Proxy.
The exact location of this checkbox changes between Actiontec revs but a good start is "Advanced/Routing/Routing Protocols/Internet Group Management Protocol (IGMP)."
Once this is off network devices typically can discover & connect to eachother.
Another strategy is, on the latest revs, enabling IPv6 (no, after years of promises Verizon still hasn't rolled IPv6 out yet, but at least the latest routers might be ready.) Anyhow, this is often reported to resolve local connectivity issues.
Just for reference, I have the newest Fios Actiontec router, and had no problems. Just so everyone with that router doesn't think they'll necessarily need to do this.
Sent from my SGH-T889 using Tapatalk 2
Evo4gLI said:
Just for reference, I have the newest Fios Actiontec router, and had no problems. Just so everyone with that router doesn't think they'll necessarily need to do this.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Good point. Mine's about 6 years old, maybe I should get them to replace it.
I had the same problem. Turned off NAT, connected, then turned NAT on
Guess this is reason #153 why I'm glad I have a Linksys router piggy-backed off of the crappy FIOS unit for the majority of my networking needs
A tip if upgrading to a newer Actiontec router: The settings backup files are *not* compatible between versions.
I upgraded to the latest router version six months ago; I'd done a lot of customizing (assigning addresses, ports, etc) and assumed it'd be an easy switch. I ended up having to temporarily return my newer router to get back my old, screenshot many pages of settings, return the old for new, then re-enter settings. A hassle, but it does run better now.
Assuming the local depot/storefront has 'em in stock it's a few minutes to swap out for a newer or newest revision.
Coincidentally I had a visit a week later to replace a burnt-out-again ONT & the tech reported he'd changed things around a bit in it for even better service. I've no idea what that involved but if it's been a long time you might want to look into a service call.
Sent from my SGH-T999 using Tapatalk 4 Beta
Some Help
I also picked up a Chromecast yesterday and am on Verizon Fios with the new Actiontec MI424WR router. I cannot get my Chromecast to connect. Sometimes I see it on the network, but it will not connect. Verizon, Actiontec, and so far Google have not been able to help me. I tried the tricks in this posting, but no luck.
I have a Buffalo Air Station wireless router, but have not had success operating this in conjunction with the Fios service (I have tried to bridge it, and run it just off ActionTec). Can someone help? I am okay at digging into this stuff, but you guys know so much more than me!
HELP!
success
The instructions below worked for me. Found it in an Apple Forum out of all places.
log in to your router(192.168.1.1), go to Wireless Settings then Advanced Security Settings. At the bottom of the screen, click "Other Advanced Wireless Options". On the next screen change Network from "Network (Home/Office)" to "Broadband". Click Apply
Just curious but it could be that you have multicasting disabled on the router.
It could also be that the router does not support multicasting in general, but this is a feature that allows devices to discover each other on a private network.
spm139 said:
I also picked up a Chromecast yesterday and am on Verizon Fios with the new Actiontec MI424WR router. I cannot get my Chromecast to connect. Sometimes I see it on the network, but it will not connect. Verizon, Actiontec, and so far Google have not been able to help me. I tried the tricks in this posting, but no luck.
I have a Buffalo Air Station wireless router, but have not had success operating this in conjunction with the Fios service (I have tried to bridge it, and run it just off ActionTec). Can someone help? I am okay at digging into this stuff, but you guys know so much more than me!
HELP!
Click to expand...
Click to collapse
I am having the same issue with DIR 655 router. Tried all the suggestion in this thread. But still no luck. Anyone having similar problem with DIR 655?
I'm having a similar problem. I've got a Linksys router that is happily supplying WiFi to my laptop, mobile phone, Kindle Fire, and XBox, but I can't get Chromecast to work properly. I get partially into the setup and then get the following message -- "Chromecast connected to [Name of Network], but can't connect to the internet." I've fiddled with countless settings to no avail. AP/Isolation mode is disabled, I've only got 2.4 GHz bands, the router is 20 ft away, etc. All the suggestions the Google Help guy gave me have had zero effect, so I thought I'd post here to see if anyone else ran into this error message and had a solution.
mowgle said:
I am having the same issue with DIR 655 router. Tried all the suggestion in this thread. But still no luck. Anyone having similar problem with DIR 655?
Click to expand...
Click to collapse
OK! finally found the issue. If your wifi password is too long(auto generated for WPA2) then chromecast cannot handle it. Reducing the length of router password fixed it. I reduced it to ~20 characters. Have not tested the pw length limit of cast.
mowgle said:
OK! finally found the issue. If your wifi password is too long(auto generated for WPA2) then chromecast cannot handle it. Reducing the length of router password fixed it. I reduced it to ~20 characters. Have not tested the pw length limit of cast.
Click to expand...
Click to collapse
My password is only 9 characters, and I have tried everything else suggested here. Anyone else have any ideas on how to get it to work?
I'm also having a similar issue with my DIR-601. I am able to detect my Chromecast but after the screen that asks for the WiFi info /renaming the Chromecast, I get an error stating that we were unable to find Chromecast on your network. I have checked that UPnP and have Enable IPv4 Multicast Streams selected (tried both ways.) I don't have any special firewall rules or anything like that. My pass is only 8 characters.
Wish Google had better support for this, all they have is a little questionnaire on their support page.If anyone finds a solution, please share. Thanks
Out of curiosity where is the enable multicast option at? I didn't see one.
Sent from my HTC One X using Tapatalk 2
axdela said:
log in to your router(192.168.1.1), go to Wireless Settings then Advanced Security Settings. At the bottom of the screen, click "Other Advanced Wireless Options". On the next screen change Network from "Network (Home/Office)" to "Broadband". Click Apply
Click to expand...
Click to collapse
Thanks! This is the only solution that fixed it for me.
axdela said:
The instructions below worked for me. Found it in an Apple Forum out of all places.
log in to your router(192.168.1.1), go to Wireless Settings then Advanced Security Settings. At the bottom of the screen, click "Other Advanced Wireless Options". On the next screen change Network from "Network (Home/Office)" to "Broadband". Click Apply
Click to expand...
Click to collapse
Worked for me as well. Thank you! :good:
None of the suggestions in this thread worked for me. I have the Actiontec Gen 3, rev I router (MI424WR-GEN3I), with firmware v. 40.20.7.
Apparently, the UPnP page is hidden, but can be accessed after logging in to the router using: 192.168.1.1/index.cgi?active_page=900. Changing the settings on this page didn't work either.
After a quick Google, I found an IGMP hidden page at 192.168.1.1/index.cgi?active_page=6059. I looked at these settings yet.
Calling Verizon's Expert Care, I was told that they don't support UPnP, since they only provide access to the Internet.
Fix found ... at least for me
AJL-Hates-Verizon said:
None of the suggestions in this thread worked for me. I have the Actiontec Gen 3, rev I router (MI424WR-GEN3I), with firmware v. 40.20.7.
Apparently, the UPnP page is hidden, but can be accessed after logging in to the router using: 192.168.1.1/index.cgi?active_page=900. Changing the settings on this page didn't work either.
After a quick Google, I found an IGMP hidden page at 192.168.1.1/index.cgi?active_page=6059. I looked at these settings yet.
Calling Verizon's Expert Care, I was told that they don't support UPnP, since they only provide access to the Internet.
Click to expand...
Click to collapse
I had the same issues as everyone else at both my office and my house. At home, I changed the IGMP settings, the UPnP settings, the security settings, etc. I finally figured out a way to make it work by simply trying to complete the setup from my laptop instead of my Droid 4. It worked on the first try at my house, and now all of my phones, tablets and computers can cast to the big tv. I immediately brought my laptop to the office and changed the IGMP setting -- and it immediately worked after that.
So maybe a solution is to try setting it up from your computer instead of your phone/tablet? It worked for me twice that way!
I got my parents a Chromecast for xmas after getting one myself and being impressed with how simple it was to set up and use with Youtube, Plex, etc. Unfortunately I haven't been able to get it up and running with their BT Home Hub 4 router and keep getting an "unable to connect to internet message". I've seen various posts on other forums mentioning the following as possible solutions, none of which worked in my case:
disable UPNP (also disable UPNP extended security)
disable "Smart" setup
disable parental restrictions (already done)
split the 2.4GHz and 5GHz bands into 2 separate SSIDs and only connect to the 2.4GHz one
I'm no expert on routers and networking so would be grateful if anyone else who's with BT in the UK has had similar issues and managed to find a solution they could share. I'd also like to move away from my current ISP whose recent service has been a joke and out of the few providers who offer high speed fibre in my area BT seem like the best of the bunch although not being able to use my Chromecast would be a real pain.
Any advice would be much appreciated!
aldo79 said:
I got my parents a Chromecast for xmas after getting one myself and being impressed with how simple it was to set up and use with Youtube, Plex, etc. Unfortunately I haven't been able to get it up and running with their BT Home Hub 4 router and keep getting an "unable to connect to internet message".
Click to expand...
Click to collapse
What firmware build is that Chromecast on? The "Unable to connect to Internet" message means it's successfully connected to WiFi, and at least for me, earlier firmware builds kept showing that. I left it alone for a few days, then power-cycled it and it had managed to download an update (build 13300) that fixed things.
If you haven't already tried power-cycling Chromecast, try that - it might have connected long enough to get an update.