Related
Chromecast wont connect to my telus router (Actiontec V1000H). I can't see any option to enable/disable AP Isolation. Is there any solution for this?
fixed:laugh:
2237 9525694
mydrl said:
Chromecast wont connect to my telus router (Actiontec V1000H). I can't see any option to enable/disable AP Isolation. Is there any solution for this?
fixed:laugh:
Click to expand...
Click to collapse
How?
try changing the wifi channel the router uses
mydrl said:
Chromecast wont connect to my telus router (Actiontec V1000H). I can't see any option to enable/disable AP Isolation. Is there any solution for this?
fixed:laugh:
Click to expand...
Click to collapse
How did you fix this?
MadBob said:
try changing the wifi channel the router uses
Click to expand...
Click to collapse
Good advice.
Remember that the WiFi bands (channels) are not exactly the same between countries. So if you're in a non-US country and your router happens to choose a channel that is not available in the US, Chromecast may not detect your wireless AP.
But Telus is Canadian, and Canada has the same WiFi channels as the U.S. (Canada and the U.S. necessarily share identical radio spectrum allocation).
DJames1 said:
But Telus is Canadian, and Canada has the same WiFi channels as the U.S. (Canada and the U.S. necessarily share identical radio spectrum allocation).
Click to expand...
Click to collapse
Didn't know that. Thanks! Still applies to other countries though. I think Channel 13 is one of the channels that applies to Europe but not US. I should put it in the FAQ...
EDIT: Seems there's far less exclusion than I thought... but added a note in the FAQ just in case.
http://en.wikipedia.org/wiki/List_of_WLAN_channels
So I can get through the setup phase up until the Chromecast tries to connect to my wifi network. I get a message saying it couldn't connect, and when I click the link in the message it brings me to a page that mentions AP filtering, UPNP enabling and .NET 3.5. I checked and UPNP is enabled, and I can't find an option for AP filtering (I have the Actiontech V1000h). I am using a Macbook pro.
Kipp34 said:
So I can get through the setup phase up until the Chromecast tries to connect to my wifi network. I get a message saying it couldn't connect, and when I click the link in the message it brings me to a page that mentions AP filtering, UPNP enabling and .NET 3.5. I checked and UPNP is enabled, and I can't find an option for AP filtering (I have the Actiontech V1000h). I am using a Macbook pro.
Click to expand...
Click to collapse
In some cases you have to go through a couple of times. I just reset my Chromecast to test a few things and had to go through the setup twice before it connected to my WiFi.
Chromecast in Canada, on Telus
A friend lent me his chromecast. He uses an iphone and Shaw cable. I use a Nexus 4, and have Telus as my internet provider.
It was a bear trying to get chromecast to work. Tried 5 separate days. Got it to work and i could watch netflix/youtube on it about 3 times and played with it for a couple of hours each. That's the success.
The fail is that I had to trouble shoot more then 4+ hours to get it to work those 3 times. Reboot the chromecast. Reboot the router. Reboot my Nexus 4. Try my wife's Nexus 4. Try the Nexus 7 tablet. It was a horrible experience. I got the AP recommendation like the earlier post in this thread. I tried that. Tried calling telus and signed into my router to check that those settings were correct. As far as I understand it's a gateway 11n wireless router.
So my conclusion is change my internet provider to Shaw unless someone has a smart solution to this problem. The router says it's a 50ghz signal? So it isn't the 2.4vs 5.0 ghz signal problem that I've googled and read about.
Please provide some brains to my situation. I've used all of mine up.
bhiga said:
In some cases you have to go through a couple of times. I just reset my Chromecast to test a few things and had to go through the setup twice before it connected to my WiFi.
Click to expand...
Click to collapse
Still not fixed.
So I took the plunge and bought one. Maybe it'd be different than my friends. Looks like this is a me problem. The chromecast still doesn't work. I thought it might be the tv that it's plugged into? Maybe shielding the chromecast from the wifi? I don't know. Will trouble shoot with a different tv or a long hdmi cable that will get the chromecast out from behind the tv. Maybe that'll help.
johnson2423 said:
So I took the plunge and bought one. Maybe it'd be different than my friends. Looks like this is a me problem. The chromecast still doesn't work. I thought it might be the tv that it's plugged into? Maybe shielding the chromecast from the wifi? I don't know. Will trouble shoot with a different tv or a long hdmi cable that will get the chromecast out from behind the tv. Maybe that'll help.
Click to expand...
Click to collapse
TVs are great at blocking/scrambling radio signals.
Use the included HDMI extender. If that doesn't help (enough), get an HDMI extension and move Chromecast away from the TV. One of mine is on a 10-foot HDMI extension. The other is connected upstream of a another device that connects to my TV, so both of my Chromecasts are at least a foot away from its associated TV.
johnson2423 said:
So I took the plunge and bought one. Maybe it'd be different than my friends. Looks like this is a me problem. The chromecast still doesn't work. I thought it might be the tv that it's plugged into? Maybe shielding the chromecast from the wifi? I don't know. Will trouble shoot with a different tv or a long hdmi cable that will get the chromecast out from behind the tv. Maybe that'll help.
Click to expand...
Click to collapse
It could be a few things not related to the router directly but related in how the Router connects to your ISP.
So a couple of questions...
What kind of service is your ISP? (DSL, CABLE, OTHER)
What Public IP does your router report? (Usually found on the status page that shows connection data) If it starts off 192.168 then your Modem is doing a double nat translation and you need to call your ISP and tell them you want the Modem to be put into gateway mode and just pass a public IP to your router.
Does the CCast actually connect to the Router but not work or will it not connect at all period? If it doesn't connect at all it is possible you need to change the Security method used to WPA or WEP. To test shut off security alltogether and try to connect the CCast. If there is currently NO security try putting WPA on and trying again (but it should work on an open AP)
fixed...
Asphyx said:
It could be a few things not related to the router directly but related in how the Router connects to your ISP.
So a couple of questions...
What kind of service is your ISP? (DSL, CABLE, OTHER)
What Public IP does your router report? (Usually found on the status page that shows connection data) If it starts off 192.168 then your Modem is doing a double nat translation and you need to call your ISP and tell them you want the Modem to be put into gateway mode and just pass a public IP to your router.
Does the CCast actually connect to the Router but not work or will it not connect at all period? If it doesn't connect at all it is possible you need to change the Security method used to WPA or WEP. To test shut off security alltogether and try to connect the CCast. If there is currently NO security try putting WPA on and trying again (but it should work on an open AP)
Click to expand...
Click to collapse
Service is Telus DSL.
Solution: I changed the security settings. It still tries to stop the CCast from talking to my phone once in a while, but I just log into my router and log into the firewall settings. The firewall settings are "high, medium, low, NAT". It started working once I started turning it off of NAT and onto Medium or High.
I don't know why this is the solution, but it is a solution. I suspect that either Telus will fix the prolbem for everyone else or this thread will become popular. Now CCast is coming to Canada. So either Telus fixes it or there'll be a lot of searching leading to this post.
As a reminder, a friend of mine on telus never toughed his firewall settings and never had a problem with using his CCast. Go figure.
johnson2423 said:
Service is Telus DSL.
Solution: I changed the security settings. It still tries to stop the CCast from talking to my phone once in a while, but I just log into my router and log into the firewall settings. The firewall settings are "high, medium, low, NAT". It started working once I started turning it off of NAT and onto Medium or High.
I don't know why this is the solution, but it is a solution. I suspect that either Telus will fix the prolbem for everyone else or this thread will become popular. Now CCast is coming to Canada. So either Telus fixes it or there'll be a lot of searching leading to this post.
As a reminder, a friend of mine on telus never toughed his firewall settings and never had a problem with using his CCast. Go figure.
Click to expand...
Click to collapse
Well if the Telus was set to NAT perhaps Double Nat Translation was the issue.
DO you have another router connected to your modem or is this one of those all in one Hybrids supplied by the ISP?
Asphyx said:
Well if the Telus was set to NAT perhaps Double Nat Translation was the issue.
DO you have another router connected to your modem or is this one of those all in one Hybrids supplied by the ISP?
Click to expand...
Click to collapse
I have a friend that is struggling with this as well. While setting up the WiFi connection between the chromecast and the router (the Actiontec V1000H - which is a modem/router combo if that helps). The chromecast will see the WiFi, but it seems to time out while trying to connect to the router.
I did find a comment on a blog somewhere (sorry, I forget where) that suggests unchecking the "IGMP snooping enabled" option in the router (Advanced Settings>IGMP Setting). Once this was done, the chromecast connected to the WiFi without any issues and we were able to stream it without any issues.
However after going out for dinner we had major issues trying to connect to the WiFi on our phones and his laptop (laptop would try to connect to the WiFi but continually fail). It seems like this is a temporary fix at best.
The only permanent solution I can think of at the moment is to go buy a new router that is listed as having no issues on the chromecast compatibility list... Which kind of defeats the whole purpose of having the chromecast as an economic way to stream content to your big screen.
Buy a better router
I don't see why IGMP should have any affect on being able to login and connect.
I Can see it being a problem with streaming but not connection.
IS this an ISP provided Modem/Router? How many devices are connecting wirelessly?
Check settings for IGMP Proxy, Try changing that setting whatever it is but it should probably be disabled (Still don't think this would affect connection but it's worth checking)
Check if UPnP Is enabled (again not really connection related but it does need to be enabled for CCast)
I personally prefer to use a two device setup with separate Modem (in Bridge Mode) and Router....This way the Modem protects the router from the outside world and even if the Modem goes bad the Network still functions properly.
And I pretty much stay away from anything that isn't a Linksys or Netgear product as far as Routers are concerned.
There are a bunch of Actiontec models that are listed as incompatible with CCast on the google site so it's obvious that something about their firmware is not CCast friendly.
So the the previous poster may actually have made a good suggestion in the long run! LOL
I'm using the telus actiontech router with chromcast with no issues....
its a pretty crappy router though and it seems telus disabled the ability for bridge mode in the latest firmware... has anyone found a solution to this so i can buy a better router?
Sent from my Nexus 7 using Tapatalk
nolook said:
I'm using the telus actiontech router with chromcast with no issues....
its a pretty crappy router though and it seems telus disabled the ability for bridge mode in the latest firmware... has anyone found a solution to this so i can buy a better router?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
As long as double NAT doesn't cause you problems, you can
Assign the new router's WAN port to an address in the ISP router's LAN range
Set the new router's gateway to the ISP router's LAN address
Connect the two routers LAN port to LAN port
Have all your wired and wireless clients connect to the new router.
Why Google you no like college students?
Hmmm this probably raises a good point, it's a bit hard to implement something like 802.1x though on a streamer device (where authentication is required per login of network prior to you having the ability to control the device).
I don't see this coming for awhile to be honest unless someone manages to hack it in - I just can't see Google releasing the ability to cache 802.1x network credential sets unfortunately due to the security implications.
Friend of mine had to buy his own router to plug in to the colleges ethernet ports in the dorm. Solved a variety of issues they were having.
Sent from my Nexus 5 using Tapatalk
fchowd0696 said:
Why Google you no like college students?
Click to expand...
Click to collapse
Beyond the lack of keyboard/interface, large networks in general fear multicast and UPnP because they have potential to easily clog the network.
Also remember that Chromecast in its current state has little security - it's designed for use within a trusted environment.
You probably don't want to be in the middle of Twilight with your girlfriend and suddenly your Chromecast switches over to SpongeBob SquarePants because someone else in the dorm decided BobsChromecast obviously wants to show SpongeBob...
Having your own router and local network will isolate your Chromecast to just your little piece of the campus network, though double-NAT might be an issue, and you should check with campus policy on use of personal WiFi router/AP hardware.
I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Sent from my LG-D802 using Tapatalk
ninepoint said:
I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Click to expand...
Click to collapse
First question is whether you can use a different DNS at all (or whether your ISP is blocking somehow).
Try doing a DNS lookup from another server on your phone/tablet via Ping & DNS or another app that lets you do that.
If that's successful, then it might work - go to the Eureka-ROM web panel at http://Chromecast_IP_addresss/ and turn off DHCP-supplied DNS, Apply, then select another DNS.
You will also need to force your phone/tablet to use the same DNS - otherwise your phone/tablet may be making requests from Mars, while Chromecast tries to retrieve stuff from Venus.
Everytime I try to stream a movie to my Chromecast with Netflix, after a few seconds of watching I get this error ""we're having trouble playing this title right now. Please try again later or select a different title." I will typically get this error 5+ times after restarting over and over before finally being able to watch the movie/show uninterrupted. This happens with every video, and with any device I use to stream to the chromecast (Samsung S4, iPhone 5S, Dell laptop computer, ASUS TF700).
I've tried the following to remedy it:
1. Sign out all devices on Netflix
2. Factory reset the chromecast
3. Uninstall and reinstall the Netflix app on my Samsung S4
4. Updating to the newest version of Netflix app on my Samsung S4
Is anyone else having an issue, or has been able to fix it with steps in addition to what I've tried myself?
Thanks so much!
nsharma2 said:
Everytime I try to stream a movie to my Chromecast with Netflix, after a few seconds of watching I get this error ""we're having trouble playing this title right now. Please try again later or select a different title." I will typically get this error 5+ times after restarting over and over before finally being able to watch the movie/show uninterrupted. This happens with every video, and with any device I use to stream to the chromecast (Samsung S4, iPhone 5S, Dell laptop computer, ASUS TF700).
Click to expand...
Click to collapse
Are you having trouble with any other services like YouTube?
It might be something as simple as Chromecast having a marginal WiFi connection and not getting consistent streaming throughput. Try the HDMI extender.
bhiga said:
Are you having trouble with any other services like YouTube?
It might be something as simple as Chromecast having a marginal WiFi connection and not getting consistent streaming throughput. Try the HDMI extender.
Click to expand...
Click to collapse
I haven't had any issues with any other service: youtube, casting tabs from chrome, avia. It's only netflix which gives the issue. I don't have the HDMI extender on, so I can see if I can find it. It's worth a shot.
I also wonder if a defective chromecast could be the cause?
nsharma2 said:
I haven't had any issues with any other service: youtube, casting tabs from chrome, avia. It's only netflix which gives the issue. I don't have the HDMI extender on, so I can see if I can find it. It's worth a shot.
I also wonder if a defective chromecast could be the cause?
Click to expand...
Click to collapse
Given that your other services are working okay it's highly unlikely that a defective Chromecast is to blame. A defective Chromecast would show other problems, especially in other applications that use significant bandwidth, like Avia can.
You aren't using an alternate DNS, are you?
bhiga said:
Given that your other services are working okay it's highly unlikely that a defective Chromecast is to blame. A defective Chromecast would show other problems, especially in other applications that use significant bandwidth, like Avia can.
You aren't using an alternate DNS, are you?
Click to expand...
Click to collapse
Not that I know of. I live in California so I haven't had a need to mess with any advanced settings to get things to work.
nsharma2 said:
Not that I know of. I live in California so I haven't had a need to mess with any advanced settings to get things to work.
Click to expand...
Click to collapse
Okay that eliminates one possibility.
If you play it on your device (not casting to Chromecast), do you get the same problem?
bhiga said:
Okay that eliminates one possibility.
If you play it on your device (not casting to Chromecast), do you get the same problem?
Click to expand...
Click to collapse
Works fine on all other devices. Only gives the issue when I push the stream to the Chromecast.
nsharma2 said:
Works fine on all other devices. Only gives the issue when I push the stream to the Chromecast.
Click to expand...
Click to collapse
Just for fun, can you shut down (or turn off WiFi) on all devices that can talk to Chromecast, then try with just one Chromecast-controlling device?
Beyond that I'm stumped.
bhiga said:
Just for fun, can you shut down (or turn off WiFi) on all devices that can talk to Chromecast, then try with just one Chromecast-controlling device?
Beyond that I'm stumped.
Click to expand...
Click to collapse
I can try that when I get home today, but I'm pretty sure that won't do anything. The only other device I use to typically cast is my laptop, which is usually off in the evenings when I'm trying to watch.
Maybe its an issue with my cisco router.
nsharma2 said:
I can try that when I get home today, but I'm pretty sure that won't do anything. The only other device I use to typically cast is my laptop, which is usually off in the evenings when I'm trying to watch.
Maybe its an issue with my cisco router.
Click to expand...
Click to collapse
Me too, just trying to cover all bases.
How "smart" is your router? If it's smart (or thinks it is) it might be denying the initial Chromecast traffic for some reason (looks like someone hogging 2.4 GHz bandwidth?). Possible checks - QoS, STP/loop detection, storm detection, IGMP-related features, parental control, bandwidth throttling.
bhiga said:
Me too, just trying to cover all bases.
How "smart" is your router? If it's smart (or thinks it is) it might be denying the initial Chromecast traffic for some reason (looks like someone hogging 2.4 GHz bandwidth?). Possible checks - QoS, STP/loop detection, storm detection, IGMP-related features, parental control, bandwidth throttling.
Click to expand...
Click to collapse
While I consider myself fairly technically savy, about everything you mentioned in "possible checks" is well beyond my expertise. I have the most basic of cisco routers since I was being fairly cheap. Bought it for $50 a few months ago. No idea how smart it is, but for $50 I can't imagine it is. Can you point me to some specific checks I can run to narrow down the issue?
nsharma2 said:
While I consider myself fairly technically savy, about everything you mentioned in "possible checks" is well beyond my expertise. I have the most basic of cisco routers since I was being fairly cheap. Bought it for $50 a few months ago. No idea how smart it is, but for $50 I can't imagine it is. Can you point me to some specific checks I can run to narrow down the issue?
Click to expand...
Click to collapse
I should try running it at my friend's place with a different router to see if the router is really a problem.
nsharma2 said:
I should try running it at my friend's place with a different router to see if the router is really a problem.
Click to expand...
Click to collapse
That's a great test to try if you can. Also, if you tell me the model number of your router I can probably check online to see if there are any obvious "problem" settings.
bhiga said:
That's a great test to try if you can. Also, if you tell me the model number of your router I can probably check online to see if there are any obvious "problem" settings.
Click to expand...
Click to collapse
I think I have this one:
Linksys - Wireless-N Router with 4-Port Ethernet Switch
Model: E1200-NP SKU: 6571476
I can definitely check when I get home to make sure.
nsharma2 said:
I think I have this one:
Linksys - Wireless-N Router with 4-Port Ethernet Switch
Model: E1200-NP SKU: 6571476
I can definitely check when I get home to make sure.
Click to expand...
Click to collapse
If your router is like the E2400, it may allow using the same SSID name on 5GHz and 2.4GHz APs.
While I don't necessarily think that's your issue, it is good practice to have different names for the two AP bands.
You may want to try disabling WMM, based on what some folks reported as a fault in the Cisco WMM or conflict with Xfinity.
WMM is enabled by default, according to page 33 of the E-series manual.
If disabling WMM solves things, you could try enabling WMM and enable No Acknowledgement (this is disabled by default).
Just as a side note, the cheaper routers that have Fast Ethernet ports (such as the E1200) usually have little hope of achieving advertised 802.11n throughput, though most people don't have 150 Mbps Internet connections to begin with.
bhiga said:
If your router is like the E2400, it may allow using the same SSID name on 5GHz and 2.4GHz APs.
While I don't necessarily think that's your issue, it is good practice to have different names for the two AP bands.
You may want to try disabling WMM, based on what some folks reported as a fault in the Cisco WMM or conflict with Xfinity.
WMM is enabled by default, according to page 33 of the E-series manual.
If disabling WMM solves things, you could try enabling WMM and enable No Acknowledgement (this is disabled by default).
Just as a side note, the cheaper routers that have Fast Ethernet ports (such as the E1200) usually have little hope of achieving advertised 802.11n throughput, though most people don't have 150 Mbps Internet connections to begin with.
Click to expand...
Click to collapse
I will give this a shot tonight. Fingers crossed! Thanks so much for your help, I very much appreciate it.
OTA build 15250 is rolling out starting today that address's some Netflix issues.
bhiga said:
If your router is like the E2400, it may allow using the same SSID name on 5GHz and 2.4GHz APs.
While I don't necessarily think that's your issue, it is good practice to have different names for the two AP bands.
You may want to try disabling WMM, based on what some folks reported as a fault in the Cisco WMM or conflict with Xfinity.
WMM is enabled by default, according to page 33 of the E-series manual.
If disabling WMM solves things, you could try enabling WMM and enable No Acknowledgement (this is disabled by default).
Just as a side note, the cheaper routers that have Fast Ethernet ports (such as the E1200) usually have little hope of achieving advertised 802.11n throughput, though most people don't have 150 Mbps Internet connections to begin with.
Click to expand...
Click to collapse
UPDATE: I disabled WMM and did not have the problem after that. Watched a few videos without seeing the error once. That being said, I then re-enabled the option and the error did not reappear, so I'm unsure whether or not this was the fix. I don't think the new build was downloaded on my chromecast yet, so that wasn't the fix. In either case, I'm happy the problem is gone (for now). Will come back to update if I learn anything else.
nsharma2 said:
UPDATE: I disabled WMM and did not have the problem after that. Watched a few videos without seeing the error once. That being said, I then re-enabled the option and the error did not reappear, so I'm unsure whether or not this was the fix. I don't think the new build was downloaded on my chromecast yet, so that wasn't the fix. In either case, I'm happy the problem is gone (for now). Will come back to update if I learn anything else.
Click to expand...
Click to collapse
Cool. Might be a weird thing like something is "floating" (like an uninitialized variable) so toggling the option fixes it by setting it to a good state.
I'm living in Panama City, so I'm natively in the Mexico Netflix region. On my apple TV I'm using unblock-us to change regions. Obviously for chromecast I've removed all DNS settings from my S3, TF700 and MBP. I can watch Netflix fine on all three devices. On Chromecast I only get a few minutes, maybe 5, before I get "We're having trouble playing this title right now. Please try again later or select a different title."
This happens with all my devices. Netflix plays fine on those devices.
Google Play Movies plays perfect, Youtube has no problems.
Looking at internet traffic as the message appears, I dont see a drop in traffic at all. However in recent weeks, watching Hulu on our apple tv can sometimes take 20 minutes longer thanks to lots of pauses.
I purchased this so I didnt have to keep moving my ATV up and down stairs. I like that it's cheap, I like using a phone or chrome to control it - but I wonder if Google ever plan to add manual IP settings. How much will they add to it in the future?
I'm very tech savy, have been in IT for 13 years. The cable modem and router I have are completely foreign to me, I dont know the username and password to login and even look at the firmware. All I know is it's a motorola something. But I did miss the window for rooting it and I was thinking if I could roll the firmware back to allow rooting, but I doubt it.
Anyone have any suggesting?
If Netflix is working on other devices I would suspect your Chromecast is not getting a good/stable WiFi signal.
Use the HDMI extender, try a different (side/front) HDMI port if your TV has one and make sure it has line-of-sight to your router with as few obstructions as possible.
bhiga said:
If Netflix is working on other devices I would suspect your Chromecast is not getting a good/stable WiFi signal.
Use the HDMI extender, try a different (side/front) HDMI port if your TV has one and make sure it has line-of-sight to your router with as few obstructions as possible.
Click to expand...
Click to collapse
Sadly this doesnt work either Why would the unstable wifi signal be problem with Netflix and not Google Play? Better connection to Google's own servers?
I tried this and still no luck :crying:
FL00DY said:
Sadly this doesnt work either Why would the unstable wifi signal be problem with Netflix and not Google Play? Better connection to Google's own servers?
I tried this and still no luck :crying:
Click to expand...
Click to collapse
Differences in encoding rate can make one service work while another has problems, so really depends.
Has Netflix on Chromecast ever worked okay in this configuration?
bhiga said:
Differences in encoding rate can make one service work while another has problems, so really depends.
Has Netflix on Chromecast ever worked okay in this configuration?
Click to expand...
Click to collapse
Nope, I'm yet to finish a program without interruption, I keep switching to my ATV after the 4-5 attempt.
My wife is a apple faithful, I cant show her my new google toy and have it not work 100%. Netflix works fine most of the time on the ATV, maybe a few times the video freezes and the audio keeps playing. I think maybe the ATV handles the little dropouts better, Hulu will pause for 10-15 seconds and keep playing.
Speedtest only records 4.5-5Mb
I think I know what your problem is since I've encountered it myself.
You're using a different dns configuration to watch Netflix from a different region, let's take the USA as an example. When you configure the unblock-us setting into your router or your mobile devices they'll work and play the USA Netflix content just fine. But these settings will never work for the chromecast since it will always use google's dns which is 8.8.8.8. Or 8.8.4.4 since this is baked into the chromecast and cannot be changed.
Once you start streaming us based Netflix content to your chromecast... It's going to see that that content is not available in your region and it'll time out and show you the message you've mentioned.
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Sent from the dark side of the moon
scandalousk said:
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Click to expand...
Click to collapse
Root and iptables (which is supported by open/hacked router firmwares other than DD-WRT as well) are not the only ways:
You can also try adding a static route to an unresponsive local address
Or if your router supports blocking access to specific IPs, you can block 8.8.8.8 and 8.8.4.4
Depending on your router one or both may work.
If Chromecast times out in trying to reach Google DNS, it will fall back to the DHCP-supplied DNS.
It has to try and fail timeout, rather than get immediately refused though. Immediate refusal will make it nag about not being able to reach the Internet.
bhiga said:
Root and iptables (which is supported by open/hacked router firmwares other than DD-WRT as well) are not the only ways:
You can also try adding a static route to an unresponsive local address
Or if your router supports blocking access to specific IPs, you can block 8.8.8.8 and 8.8.4.4
Depending on your router one or both may work.
If Chromecast times out in trying to reach Google DNS, it will fall back to the DHCP-supplied DNS.
It has to try and fail timeout, rather than get immediately refused though. Immediate refusal will make it nag about not being able to reach the Internet.
Click to expand...
Click to collapse
Correct. Silly of me to not even mention this since this is the method I use lol. Thanks for pointing it out mate!
Sent from the dark side of the moon
scandalousk said:
Correct. Silly of me to not even mention this since this is the method I use lol. Thanks for pointing it out mate!
Click to expand...
Click to collapse
There are so many little details, even I forget from time to time. Just wanted to make sure people didn't think it's hopeless, at least not on the DNS front.
scandalousk said:
I think I know what your problem is since I've encountered it myself.
You're using a different dns configuration to watch Netflix from a different region, let's take the USA as an example. When you configure the unblock-us setting into your router or your mobile devices they'll work and play the USA Netflix content just fine. But these settings will never work for the chromecast since it will always use google's dns which is 8.8.8.8. Or 8.8.4.4 since this is baked into the chromecast and cannot be changed.
Once you start streaming us based Netflix content to your chromecast... It's going to see that that content is not available in your region and it'll time out and show you the message you've mentioned.
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Sent from the dark side of the moon
Click to expand...
Click to collapse
scandalousk thanks for the advice. However like I said, I'm not running any unblock-us service on my devices or routers. It's running on my ATV but it was switched off while I was trying all this...
Any method that means changing my Router config is useless as it was equipment provided by the cable company in Panama and while I can hide my device from my wife, I cant very well hide a new router. I dont know the username and password to even checkout the firmware and features. When I google the part numbers and model numbers I'm lucky to get 3-4 search results.
FL00DY said:
scandalousk thanks for the advice. However like I said, I'm not running any unblock-us service on my devices or routers. It's running on my ATV but it was switched off while I was trying all this...
Any method that means changing my Router config is useless as it was equipment provided by the cable company in Panama and while I can hide my device from my wife, I cant very well hide a new router. I dont know the username and password to even checkout the firmware and features. When I google the part numbers and model numbers I'm lucky to get 3-4 search results.
Click to expand...
Click to collapse
Why would you need to hide it from your wife?
If your Chromecast is unrooted, the *only* ways to view out of region content are by modification of the router. If necessary you could add a second more customizable router on top of the cable company's equipment, and use that network for all your casting needs.
Sent from my Nexus 5 using Tapatalk
Same problem here
Living in Panama City, same problems as OP, the difference is that it used to work when I first got it. I'm on build 16664 with no VPN or anything else to change regions. Netflix works fine on PS3, nexus 5, nexus 7, windows PC, Ouya, 3DS and Macbook. I've tried reseting the CC (holding button, and through the android app) and reinstalling the Netflix apps on my android devices (even though I knew that wasn't the problem since I can't cast from my PC either). Any ideas on router configuration we could try?
Since my Chromecast updated to 16664 (official) last week, I have had a bear of a time having any device see the Chromecast. Prior to the upgrade, I didn't have any issues with connectivity. Now the only way I can get the device to work is to do a reset to defaults and go through the setup procedure. The CC will generally work until the next power-up, then the same thing.
When this happens, the ChromeCast's home screen indicates it's connected to my WiFi network, however no Chromecast enabled program, including the Chromecast app on my phone, sees the device.
There have been no changes to my wireless network settings since it worked last. Given that I've not seen anyone else post about this, I must be the only one seeing the problem. Anyone?
I've seen some similar reports over at Plex but not here...
I myself am on 16664 and have no issues seeing my device.
try a Factory reset and see if reconnecting helps at all.
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
SFDave said:
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
Click to expand...
Click to collapse
TiVos use mDNS advertising for their services.
Recent Chromecast firmware also seems to be using mDNS as well.
Try running Bonjour Browser and see if Chromecast is visible before/after reset or reboot.
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
kishke said:
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
Click to expand...
Click to collapse
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
bhiga said:
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
Click to expand...
Click to collapse
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Thanks for your reply tho!
kishke said:
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Click to expand...
Click to collapse
Weird... Might also be a more general network thing like a rogue device with a static IP causing a collision that Chromecast doesn't gracefully recover from, or a multi-interfaced device causing some kind of loop
But yeah, since you have 5 GHz, best to use that and keep your 2.4 GHz usage to a minimum to maximize available bandwidth for Chromecast..
Let me try a few of the suggestions here. I've not had any luck using 2.4 or 5GHz bands on my network...behavior is the same. Also, my router is an ASUS router with Merlin firmware. There is a new thread I've only glanced over, but I'll try some of the things there as well:
http://forum.xda-developers.com/showthread.php?t=2599515
I had to do the factory reset trick again last night so we could watch video on the Chromecast...it obviously hasn't gotten annoying to the point where I'm stopping all other activity until I get it fixed, though. Strange this only started happening after the Chromecast update, but I can no longer remember the sequence of events that go me here (chromecast update, router update, wireless AP added for better wireless coverage, etc).
I've seen similar behavior when there are just too many devices connected to the WiFi at once.
My router maxes out at around 9-10 devices...
Doesn't matter which band they are on either.
But to be sure it isn't an IP conflict I suggest setting DHCP reservations for all your regularly connecting devices to ensure they never get a different IP (especially important to do for servers like Plex) and remove that possibility from the equation.
Just to Add I believe the new 802.11AC Standards solve this problem, But you will need to buy a new router to get it.
Using a bonjour browser, I can see the entry for the Chromecast :
_googlecast._tcp.local.
Bedroom.local.:8009
/192.168.254.193
st = 0
ve = 02
md = Chromecast
ic = /setup/icon.png
id = [a very long number]
fn = Bedroom
ca = 5
Click to expand...
Click to collapse
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
EDIT: I've tried the factory default recovery method a number of times now. I see the bonjour record go away, then come back after the setup app says I'm ready to cast. All apps can see the Chromecast at that time, then after 3 to 5 minutes, they no longer see the Chromecast. I don't see any difference in the bonjour record when it working from when it's not working.
troycarpenter said:
Using a bonjour browser, I can see the entry for the Chromecast :
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
Click to expand...
Click to collapse
Just a longshot....But do you have any security software that could be blocking some Apps from communicating with the Network?
It sounds an awful lot like what happens when an AntiVirus Application Monitor has denied access.
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can). I'm looking for my iPad (I don't use it enough to keep track of it as close as I should) to see if it sees the Chromecast or not.
troycarpenter said:
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can).
Click to expand...
Click to collapse
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
bhiga said:
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
Click to expand...
Click to collapse
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
troycarpenter said:
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
Click to expand...
Click to collapse
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
bhiga said:
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
Click to expand...
Click to collapse
Looks like I switched off TKIP and just went AES on that network at some time. I went back and turned on AES+TKIP and now the Chromecast shows up on my mobile devices again. I'll keep an eye out in case that theory doesn't hold out.