Related
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!
Hey all. New poster long time lurker. I just wanna thank everyone in advance for all the help I've gotten over the years.
Anyway. I own a chromecast and am attempting to connect it to my home wifi network. I'm using a mi424wr-gen3i router with the latest firmware. I disabled IGMP and UPNP is enabled. I turned on IPv6 like some other posters mentioned. My phone (Bionic) gets to the set up page, sees the chromecast but fails at one of two points. Either it says it cannot communicate with the device or it gets to the point of connecting the chromecast to the network and fails. My network is using a WPA2 security key. As far as I can tell my router is not a dual band and only transmits at 2.4ghz. The chrome support mentions something about Access Point/ Client Isolation, but I have no idea what that is or how to configure it. I called both Verizon and Google. Google said check upnp and 2.4 ghz. Verizon said its not their problem.
I was following this thread which seemed to be point on, on my issue. However where other people seemed to make it work, mine still fails.
http://forum.xda-developers.com/showthread.php?p=44018888
drstrangelove5 said:
Hey all. New poster long time lurker. I just wanna thank everyone in advance for all the help I've gotten over the years.
Anyway. I own a chromecast and am attempting to connect it to my home wifi network. I'm using a mi424wr-gen3i router with the latest firmware. I disabled IGMP and UPNP is enabled. I turned on IPv6 like some other posters mentioned. My phone (Bionic) gets to the set up page, sees the chromecast but fails at one of two points. Either it says it cannot communicate with the device or it gets to the point of connecting the chromecast to the network and fails. My network is using a WPA2 security key. As far as I can tell my router is not a dual band and only transmits at 2.4ghz. The chrome support mentions something about Access Point/ Client Isolation, but I have no idea what that is or how to configure it. I called both Verizon and Google. Google said check upnp and 2.4 ghz. Verizon said its not their problem.
I was following this thread which seemed to be point on, on my issue. However where other people seemed to make it work, mine still fails.
http://forum.xda-developers.com/showthread.php?p=44018888
Click to expand...
Click to collapse
Have you tried rebooting your router, disable MAC address filtering if it is enabled, and/or reset the router's settings back to default
supernova_00 said:
Have you tried rebooting your router, disable MAC address filtering if it is enabled, and/or reset the router's settings back to default
Click to expand...
Click to collapse
Yeah. I rebooted to the factory reset. Unfortunately its a verizon issued modem/router combo and its to their specs. MAC filtering is disabled and its been rebooted.
Get the latest router from Verizon & turn off IGMP. Swapping out the router should be free.
Sent from my SGH-T999 using Tapatalk 4
I was having a similar problem but I realized that Chromecast only needs the network name and it's password to work. After the step were you put in the password and it fails, I should work..Also, if you are getting stuck renaming chromecast, leave it the way it is for now. Before you start over, check to see if you can see chromecast on you network using Fing or a similar program.
drstrangelove5 said:
Hey all. New poster long time lurker. I just wanna thank everyone in advance for all the help I've gotten over the years.
Anyway. I own a chromecast and am attempting to connect it to my home wifi network. I'm using a mi424wr-gen3i router with the latest firmware. I disabled IGMP and UPNP is enabled. I turned on IPv6 like some other posters mentioned. My phone (Bionic) gets to the set up page, sees the chromecast but fails at one of two points. Either it says it cannot communicate with the device or it gets to the point of connecting the chromecast to the network and fails. My network is using a WPA2 security key. As far as I can tell my router is not a dual band and only transmits at 2.4ghz. The chrome support mentions something about Access Point/ Client Isolation, but I have no idea what that is or how to configure it. I called both Verizon and Google. Google said check upnp and 2.4 ghz. Verizon said its not their problem.
I was following this thread which seemed to be point on, on my issue. However where other people seemed to make it work, mine still fails.
http://forum.xda-developers.com/showthread.php?p=44018888
Click to expand...
Click to collapse
I have had same issue and fixed it by doing a MANUAL entry of all wireless connection to your router... type in SSID, pick WPA2, and enter passcode.
Well after several hours of talking with Google and Verizon again. Verizon hung up on me and Google solved the problem. Apparantly my phone (Droid Bionic) is not communicating with the device properly. Off all things i was able to set it up with my buddies IPAD. Ironic right? Now I just need to figure out what the heck is wrong with my phone. I read somewhere that the razrs were having problems. The Bionic and Razr are one in the same so i guess ill head that way. Anyway thanks guys.
drstrangelove5 said:
Well after several hours of talking with Google and Verizon again. Verizon hung up on me and Google solved the problem. Apparantly my phone (Droid Bionic) is not communicating with the device properly. Off all things i was able to set it up with my buddies IPAD. Ironic right? Now I just need to figure out what the heck is wrong with my phone. I read somewhere that the razrs were having problems. The Bionic and Razr are one in the same so i guess ill head that way. Anyway thanks guys.
Click to expand...
Click to collapse
It's always a good idea to try different devices when possible. Adding the Google Cast extension on Chrome for the PC may be the easiest to work with since you're using a full keyboard.
I had to manuilly allow my chromecasts Mac address... Then it worked no problem.
Sent from my SCH-I535 using Tapatalk 2
drstrangelove5 said:
Well after several hours of talking with Google and Verizon again. Verizon hung up on me and Google solved the problem. Apparantly my phone (Droid Bionic) is not communicating with the device properly. Off all things i was able to set it up with my buddies IPAD. Ironic right? Now I just need to figure out what the heck is wrong with my phone. I read somewhere that the razrs were having problems. The Bionic and Razr are one in the same so i guess ill head that way. Anyway thanks guys.
Click to expand...
Click to collapse
My wife's razr had the same issue. You could have also used your PC to set it up.
Here is the thread on the Razr / Bionic issue: groups.google.com/d/msgid/chromebook-central/1280fb6a-d063-4d77-993d-dbec4fc6cdb6%40googlegroups.com (sorry, you have to copy/paste it, I have less than 10 posts so I can't post links yet).
Play Music and Play Movies/TV probably won't work for you either.
Just hit Try Again and it will work. It fails the first time, and hitting Try Again did the trick.
Not sure if it was luck or what not.
Hi guys,
I was extremely happy with my shiny new Moto X (2nd Gen) (UK), which arrived on Monday, however I am since less pleased as I cannot connect to my office WiFi!
All other WiFi's are fine, but for whatever reason I CANNOT seem to connect to my office WiFi.
I have tried every single setting and the only conclusion I can rationalise is that it's because the SSID is hidden and the Moto X (at least my one) has a problem with this. I've tried restarting the phone, factory restored the phone, asked sysadmin to reset the router, tried changing WiFI Direct name, turned on "WiFI Optimisation" etc.
Nothing works. It just says "Saved, secured with WPA2". Every other device in the office works fine.
There is no MAC filtering and plenty of DHCP licenses available.
What kinda odf crap phone can't handle hidden SSID's? Also, Motorola support is a pile of crap! Been waiting to speak to one of them for 1 hour.
Anyone have any ideas?
Thanks,
TD
I'm connected to my office WiFi with hidden ssid...
So why can't I?!?
Apparently someone told me that hidden SSID's is a violation of the Wi-Fi protocol and hence is not supported in Android/Motorola devices. Guessing that's the reason why apps like: https://play.google.com/store/apps/details?id=jp.sourceforge.soopy.hidden.ssid.enabler&hl=en_GB exist..?
On the other hand, it seems like bullcrap if you and other can connect to hidden networks just fine?
No one know or have any advice on this issue?
Thanks,
Z
I don't now where you're problem is coming from but I swear I'm connected each work day on a Wi-Fi network with hidden SSID. But : when I have configured it for the first time my moto x was telling me that WiFi network was not reachable. Just waiting 5 minutes and voila, moto x was connected. It was exactly same situation with a nexus 5 on same WiFi network.
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
So configure it, and then wait 5 minutes and see if it is now connected. Put your WiFi in always on mode even when idle.
Mine just says "Saved Secured with WPA/WPA2".
Just won't connect!!
Go to wifi settings scroll down and hit
ADD NETWORK
Next enter the ssid exactly it is case sensitive.
Next enter password.
If it doesn't connect then your works wifi may have Mac address filtering on.
In that case you have to have the I. T. guy manually allow you in.
Hope that helps
Nd8 deodexed Rooted and modded
As mentioned there is no Mac filtering and thus isn't a dhcp capacity issue. Everything is fine. All other devices including other 4.4.4 devices are connecting without issue.
Any other ideas..
Is it 2.4 or 5 GHz WiFi? Have you enabled both?
Not sure what band, but doubt that's the issue as works on both bands at home.
Using a great tool called "WiFi Connection Manager" from the Play Store, you can see the following network settings:
Interesting to see what the alert says when clicking into it:
Any ideas? Thinking it could be a Cisco hardware related issue!
Z
Interesting... Using google I can found a lot of people that have same problem as you. But... Hidden ssid is only for bad admins that still think this will protect them
Yeah but it's no excuse for Android and/or Motorola to not play nice with hidden SSIDs. This in my opinion is VERY poor.
It's not moto but android. But since 802.11 have never been designed to work with hidden ssid I don't know if we can complain about android. But I'm not an expert on this subject, so maybe and hopefully someone can explain us in a more detailed manner.
That would make sense if I hadn't been able to use other Android 4.4.x devices and versions to successfully connect to the same network..
I missed that point... You're right if other android devices are able to connect to the same network then it is probably a moto problem... But mine is working good with hidden ssid but the router is not a Cisco one. I suggest to contact moto support by chat ( not by phone ), you should have an answer.
Cisco router? Make sure it is on the latest firmware. There appears to be an issue with older Cisco firmware and the X, independent of broadcasting of SSID.
https://supportforums.cisco.com/dis...isco-controllers-and-pmf-enabled-moto-x-gen-2
I just updated my Nexus 6 from T-Mobile and now the WiFi won't turn on. Any one else with this issue?
It will just show this
Sits on this screen also. WiFi is broken
Bump
jprovan1 said:
Bump
Click to expand...
Click to collapse
Might be defective, might be a bug you should try a factory reset. I suspect I have a WIFI problem as well (not the same) as mine will absolutely not connect to my work network even though it should and I've tried everything.
youareme7 said:
Might be defective, might be a bug you should try a factory reset. I suspect I have a WIFI problem as well (not the same) as mine will absolutely not connect to my work network even though it should and I've tried everything.
Click to expand...
Click to collapse
Same here. I had the problem on the Nexus 5 and hoped the Nexus 6 would solve this but I cannot connect to my work wifi either.
I am having the same problem at work too. Never had it on any other devices (m8, nexus 5, note 4, etc.) Wondering of they did something new with WiFi or if its the router settings or outdated routers.
Android devices have had a history of issues with some older Wireless Access points. The problem isn't that they won't connect, but that they won't get an IP address. You may be able to work around the issue, by finding an unused IP address, and manually setting it for that wifi connection. Contact your IT person if you don't know what all this means, and ask him/her for the following:
IP Address
Subnet Mask
Default Gateway
DNS Server
You'll need those to set things up manually. If you can connect after setting it up manually, then the issue is incompatibility with the WiFi access point (or the DHCP server, which gives out IP Addresses), not with your phone.
jt3 said:
Android devices have had a history of issues with some older Wireless Access points. The problem isn't that they won't connect, but that they won't get an IP address. You may be able to work around the issue, by finding an unused IP address, and manually setting it for that wifi connection. Contact your IT person if you don't know what all this means, and ask him/her for the following:
IP Address
Subnet Mask
Default Gateway
DNS Server
You'll need those to set things up manually. If you can connect after setting it up manually, then the issue is incompatibility with the WiFi access point (or the DHCP server, which gives out IP Addresses), not with your phone.
Click to expand...
Click to collapse
I will give that a try. I just confirmed that it's ONLY my nexus 6, I brought in my nexus 7 2013 with lollipop to work (which I have never done) and it was able to connect with no problem so now I'm sure it's a problem with the nexus 6.
EDIT: I tried manually connecting to the router and that didn't do it as well. I wish there was a way to submit the bug because it's a pain in the ass to not have wifi on my phone at work, poor signal in the building means it kinda chews on the battery.
If anyone else tries manual and succeeds please let us know!
https://code.google.com/p/android/i...fi&colspec=ID Type Status Owner Summary Stars
Add feedback to escalate the issue. I get no cellular signal inside my office at work so WiFi is A MUST for me.
HCdroid said:
https://code.google.com/p/android/i...fi&colspec=ID Type Status Owner Summary Stars
Add feedback to escalate the issue. I get no cellular signal inside my office at work so WiFi is A MUST for me.
Click to expand...
Click to collapse
Yep exactly, it's not just a nexus 6 issue, it also affects the nexus 5 on LXR210. Sounds like it's actually cisco's fault for incorrectly using the wrong EAPOL-Key descriptor version (3 instead of 2). Hopefully google fixes the issue quickly.
I had a defective unit. Took it back to T-Mobile and they had one Nexus left and swapped it out now everything is great. Now the damn X Where it says NEXUS on the back of the phone fell off . Oh well
I have the AT&T Nexus 6 and now I'm having WiFi issues. Keeps dropping connection or says poor than disconnects. No issue on any other device and it will not even show my 5ghz band.
Sent from my Nexus 6
I have been doing research on this and it turns out that the Nexus 6 had issues with corporate wifi on 5.0. Corporate wifi is just wifi that requires a username and password to access if you do not know and this is the kind of wifi my college uses. Well hoping this problem would be fixed with 5.1 update I got the update and am still having the same issue it verifies the network but only says saved never connects however many tries it does its just a huge loop and this is getting very annoying. I dont know if there is something I should try to resolve this problem or will just have to stick it out until google addresses it. If anyone knows more about this issue please inform me because I have reached a wall with my research on this issue.
Yeah, ever since I updated to 5.1 I haven't been able to connect either, and I try through the Xpress Connect app like and it never works. I had been able to connect normally when I was on 5.0.1 before.
ItsRhody said:
I have been doing research on this and it turns out that the Nexus 6 had issues with corporate wifi on 5.0. Corporate wifi is just wifi that requires a username and password to access if you do not know and this is the kind of wifi my college uses. Well hoping this problem would be fixed with 5.1 update I got the update and am still having the same issue it verifies the network but only says saved never connects however many tries it does its just a huge loop and this is getting very annoying. I dont know if there is something I should try to resolve this problem or will just have to stick it out until google addresses it. If anyone knows more about this issue please inform me because I have reached a wall with my research on this issue.
Click to expand...
Click to collapse
Hm, my cable company offers local WiFi and I've been able to connect to their userid/password-required routers, then use their network. Did this just a couple days ago when signal in a particular store was really hampered.
Maybe it depends on the particular router and/or configuration they use?
- ooofest
We had to update firmware on our corporate router for the problem to go away.
See my post here for more details: http://forum.xda-developers.com/showpost.php?p=59682044&postcount=12
LEAP authentication.
Try installing the hydra kernel.
I use it along with meanpop and have no problems connecting to LEAP
ooofest said:
Hm, my cable company offers local WiFi and I've been able to connect to their userid/password-required routers, then use their network. Did this just a couple days ago when signal in a particular store was really hampered.
Maybe it depends on the particular router and/or configuration they use?
- ooofest
Click to expand...
Click to collapse
By username and password I meant one that the company or school gives you individually its not the kind of regular router login because at home I connect no issues but its the school wifi they even checked my account to make sure I wasnt blocked out of it and I was not. My fault for not being specific in the original post.
In my case N6 was able to connect to one password protected SSID without an issue, the subnet associated with this SSID is dedicated to provide internet access only.
The SSID N6 was having problem to authenticate with, was another SSID, whose subnet is bridged to provide access to both internet, and to corporate network.
According to Dell support, the Sonicwall router was failing to authenticate a connection coming through a bridged interface. I guess, N6 and/or Android 5.1 implements something new vis-a-vis authentication, that an older SonicWall firmware was not designed to deal with.
Immediately after SonicWall firmware update the problem was resolved.
Just wanted to chime in on this one... We have a corporate Wi-Fi as you describe (each user has a separate logon to the network) and I've not had any problems with Lollipop, 5.0 or 5.1. Not very helpful for you, but at least now you know it can work...