can see chromecast not on network? - Google Chromecast

So the weirdest thing happened. Lost power randomly. Power came back on and I detected my neighbors chromecast.. so I changed the name of it lol has anyone else had that happen before? I thought you could only detect ones on your own network? I double checked my network to make sure they werent stealing internet and they are not.

ajac said:
So the weirdest thing happened. Lost power randomly. Power came back on and I detected my neighbors chromecast.. so I changed the name of it lol has anyone else had that happen before? I thought you could only detect ones on your own network? I double checked my network to make sure they werent stealing internet and they are not.
Click to expand...
Click to collapse
That just means your neighbor's Chromecast lost connection to their network and went into setup mode (where it is an open Access Point).
If you completed the setup, their Chromecast should have been lost to you unless you set it up on your network, in which case their Chromecast is not only inaccessible to them, but also sitting on your network... not very useful aside from pranking them by playing random videos. Chromecast rickrolling?

Lol
sent via tapatalk

Don't you need to see the access code on the TV screen? Or is that in the SSID that the Chromecast broadcasts? (forgetting now how the setup went)

DJames1 said:
Don't you need to see the access code on the TV screen? Or is that in the SSID that the Chromecast broadcasts? (forgetting now how the setup went)
Click to expand...
Click to collapse
Because of the silly way Chromecast setup works, no, not really.
Chromecast goes into Setup mode
Chromecast becomes an open AP, broadcasting an SSID of Chromecastnnnn (where nnnn is some randomly-generated number)
Chromecast outputs to TV "Set me up" along with a 4-character hex code (which seems to be specific to the device, but does not directly correspond to the serial number)
Chromecast setup app
Searches for available Chromecasts (open APs named Chromecastnnnn)
Once selected, asks "Is this the code you see the screen?" showing the 4-character hex code associated with that Chromecast
Queries user for SSID (drop-down generated from visible networks) and passkey if necessary.
Since the setup app shows you the 4-character ID, it's essentially like going to an ATM, sticking a stolen card in, then the ATM says "Hello Joe. Is your PIN 1234?" Press Yes and you're in!
I've never seen it display an incorrect/bogus code so far. Frankly I find it very odd that it operates this way. Maybe it's just wishful thinking but, it feels like it was meant to be something more and they ran out of time.

I had two rooted CC's, two TV's but only had one installed on my main upstairs TV. I decided to throw in the second one in my basement TV yesterday.
It just wouldn't connect to my network. After half dozen tries, I tried the extender for another bunch of tries. Pulled it out and took it to my other TV where I tried a bunch more times with no luck. This might be an issue with a second CC but it worked right away after clearing the data/cache on the CC app. Installed it in the basement TV and it works with no problem so far anyway.
They sure can be a PITA to setup and I know that I'm not alone with my results.

Related

WiFi DoA on my Tilt/Kaiser?

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.

Chromecast Unable to Connect to Network

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.

'No Cast Devices Found' (Am I missing something?)

I'm really not seeing any threads with workarounds for this error message.
I know I haven't been around in quite a while, am I just missing them? If I am, please point me in the correct direction.
If not, I can update this thread with some workarounds I have found (May also help Google in helping their customers, can't explain any further than that). Seems like it would make sense to have a thread dedicated to that.
mattykinsx said:
I'm really not seeing any threads with workarounds for this error message.
I know I haven't been around in quite a while, am I just missing them? If I am, please point me in the correct direction.
If not, I can update this thread with some workarounds I have found (May also help Google in helping their customers, can't explain any further than that). Seems like it would make sense to have a thread dedicated to that.
Click to expand...
Click to collapse
These are a list of things that can be at play...Most are Router related
No Multicast capability, Multicast Disabled or Filtering On
2.4 Ghz band disabled or not supported by the router (CCast only has 2.4Ghz WiFi)
IGMP Enabled or Proxied
AP Isolation on
UPnP settings
IPv6 Disabled
MAC Filtering Enabled
Firewall and Security Programs blocking ports
Incompatible Routers
Check here for possible solutions
https://support.google.com/chromecast/table/3477832?hl=en&ref_topic=3447927
and make sure your CCast has a Solid White Light cause if not then you need to use the setup program to configure it
What if it works seemingly fine, but then proceeds to intermittently drop off and display the 'No cast devices found' error.
zcace said:
What if it works seemingly fine, but then proceeds to intermittently drop off and display the 'No cast devices found' error.
Click to expand...
Click to collapse
How is the WiFi signal at the Chromecast? The HDMI Extender can help a lot in some cases.
bhiga said:
How is the WiFi signal at the Chromecast? The HDMI Extender can help a lot in some cases.
Click to expand...
Click to collapse
WiFi is strong. It works fine from all my other devices, it's just Chrome. I'm on a Windows 8 PC. Sometimes it'll work perfectly for hours on end. I have everything except my LAN turned off (or so I think), checked binding orders, my windows firewall is off, and it just keeps happening.
Actually I will report back, I thought I had IGMP disabled. I didn't, so I just turned it off.
zcace said:
WiFi is strong. It works fine from all my other devices, it's just Chrome. I'm on a Windows 8 PC. Sometimes it'll work perfectly for hours on end. I have everything except my LAN turned off (or so I think), checked binding orders, my windows firewall is off, and it just keeps happening.
Actually I will report back, I thought I had IGMP disabled. I didn't, so I just turned it off.
Click to expand...
Click to collapse
If that doesn't change things, check if you can adjust your router's UPnP Advertisement time and see if that correlates with your dropoffs.
Beyond that you can try the Wireless Portable Devices setting in the Firewall and enabling IPv6 as described by folks in this thread.
I had similar issues when I first played with the Chromecast which were being caused by Wifi signal - it appears that due to the location of my Chromecast (in a media cabinet) the signal was severely degraded. I tried it in the TV directly (as opposed to the home theatre) and this increased the performance for me as it was out of the cabinet and ended up buying a hdmi extender to run it up into a higher location so it would get better signal.
Not sure if you're getting the same but that's what I'd look at.
zcace said:
What if it works seemingly fine, but then proceeds to intermittently drop off and display the 'No cast devices found' error.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443288
And the second thread is linked from that one.
Anyone who is using this in a Home Entertainment environment would be wise to get a Wireless AP extender to place near the Home Entertainment cabinet because all those devices throw off so much RF that can easily interfere with the CCast connection.
It's one of the reasons I wish they had a USB Cable similar to the one used for Flashcast that you could put a wired USB ETH dongle in and wire it up.
Thats something I would expect @Kyonz and Team Eureka to be adding to their ROM at some point. That would be a damn good upgrade to the Unit for those with Reception and Network issues. We might even get a sense of exactly what Bitrate the CCast Hardware can handle when the Network isn't getting in the way.
bhiga said:
If that doesn't change things, check if you can adjust your router's UPnP Advertisement time and see if that correlates with your dropoffs.
Beyond that you can try the Wireless Portable Devices setting in the Firewall and enabling IPv6 as described by folks in this thread.
Click to expand...
Click to collapse
This is getting weirder, IGMP disabled. It worked solidly for over a week, and now it's dropping off again. I can't help but think that wi-fi signal is strong as all my other devices work fine, and the CC is in the same room as the router, a month old Netgear R6200v2. I played with uPnP advertisement time and nothing changed, its still dropping off. Restarting the router fixes it. I feel like the problem is on the Windows side though, because every other device works perfectly fine, including Chrome on my Macbook, and all mobile devices.
zcace said:
This is getting weirder, IGMP disabled. It worked solidly for over a week, and now it's dropping off again. I can't help but think that wi-fi signal is strong as all my other devices work fine, and the CC is in the same room as the router, a month old Netgear R6200v2. I played with uPnP advertisement time and nothing changed, its still dropping off. Restarting the router fixes it. I feel like the problem is on the Windows side though, because every other device works perfectly fine, including Chrome on my Macbook, and all mobile devices.
Click to expand...
Click to collapse
Since rebooting the router seems to help it feels like it's some advertisement or multicast related thing. It "registers" at router start but eventually the client is ignoring it. Does the Windows machine go to sleep, turn off its network connection, or auto connect to VPN or another virtual network adapter?
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
zcace said:
This is getting weirder, IGMP disabled. It worked solidly for over a week, and now it's dropping off again. I can't help but think that wi-fi signal is strong as all my other devices work fine, and the CC is in the same room as the router, a month old Netgear R6200v2. I played with uPnP advertisement time and nothing changed, its still dropping off. Restarting the router fixes it. I feel like the problem is on the Windows side though, because every other device works perfectly fine, including Chrome on my Macbook, and all mobile devices.
Click to expand...
Click to collapse
You mentioned Windows 8...
Make sure IPv6 is enabled on both the Computer and the Router.
If your router does not support IPv6 that may be the cause of your problem.
But it is on the list of Compatible routers which leads me to believe you have IPv6 disabled on the Windows8 machine.
bhiga said:
Since rebooting the router seems to help it feels like it's some advertisement or multicast related thing. It "registers" at router start but eventually the client is ignoring it. Does the Windows machine go to sleep, turn off its network connection, or auto connect to VPN or another virtual network adapter?
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Again let's keep in mind that the CC works perfectly fine from every other device. Been watching Breaking Bad on Netflix through my phone and it goes for hours and hours without a hitch.
With that said you're on to something with the sleep idea. My sleep for displays is set to 2 hours, and my hard drives is set to 3 hours, so I don't think that's it. All VPNs or extra LAN connections are off afaik. But turning off my network connection, that's a possibility. I found the 'Allow the computer to turn off this device to save power' option under Control Panel -> Network Connections -> Ethernet -> Properties -> Configure -> Power Management tab. Now, I tried this both allowing the computer to idle (dropped off) and while typing this very message (also dropped off). So it's not that particular setting. Also IPv6 is enabled in the Ethernet Properties. This is crazy, why doesn't this work out of the box!? Everything else did.
Google Chrome Canary is seemingly fixing a lot of people's issues.
https://www.google.com/intl/en/chrome/browser/canary.html
zcace said:
Again let's keep in mind that the CC works perfectly fine from every other device. Been watching Breaking Bad on Netflix through my phone and it goes for hours and hours without a hitch.
With that said you're on to something with the sleep idea. My sleep for displays is set to 2 hours, and my hard drives is set to 3 hours, so I don't think that's it. All VPNs or extra LAN connections are off afaik. But turning off my network connection, that's a possibility. I found the 'Allow the computer to turn off this device to save power' option under Control Panel -> Network Connections -> Ethernet -> Properties -> Configure -> Power Management tab. Now, I tried this both allowing the computer to idle (dropped off) and while typing this very message (also dropped off). So it's not that particular setting. Also IPv6 is enabled in the Ethernet Properties. This is crazy, why doesn't this work out of the box!? Everything else did.
Click to expand...
Click to collapse
Hmm, can't find it but I remember running across a mention of Chromecast discovery not working properly in some cases when there were multiple network interfaces installed (regardless of whether they're active). Windows also has some trouble with the network filter driver layer if there are two many filters installed (again, VPN adapters and firewalls).
Actually... maybe I'm overthinking things as I often do...
It's just that particular computer, right?
Can you try disabling all other Chrome extensions? I recall someone else ran into a conflict with another Chrome extension.
bhiga said:
Hmm, can't find it but I remember running across a mention of Chromecast discovery not working properly in some cases when there were multiple network interfaces installed (regardless of whether they're active). Windows also has some trouble with the network filter driver layer if there are two many filters installed (again, VPN adapters and firewalls).
Actually... maybe I'm overthinking things as I often do...
It's just that particular computer, right?
Can you try disabling all other Chrome extensions? I recall someone else ran into a conflict with another Chrome extension.
Click to expand...
Click to collapse
Indeed, only this computer has any issues. I tried turning off all chrome extensions, still no dice. I am sure there is one singular obscure setting somewhere we are missing. Or maybe its like 'mattykinsx' said, it's a Chrome issue?
zcace said:
Indeed, only this computer has any issues. I tried turning off all chrome extensions, still no dice. I am sure there is one singular obscure setting somewhere we are missing. Or maybe its like 'mattykinsx' said, it's a Chrome issue?
Click to expand...
Click to collapse
Quite possible it's a Chrome thing.
Perhaps create a System Restore point (or otherwise back up your current instance) and try the newfangled thing.
bhiga said:
Quite possible it's a Chrome thing.
Perhaps create a System Restore point (or otherwise back up your current instance) and try the newfangled thing.
Click to expand...
Click to collapse
I take it back. Downloaded Chrome Canary, installed only Google Cast, still drops connection after a couple of minutes.
zcace said:
I take it back. Downloaded Chrome Canary, installed only Google Cast, still drops connection after a couple of minutes.
Click to expand...
Click to collapse
Your Network location is set to Home or Work, yes?
Can you post a shot of the Advanced tab of your network interface's properties from Device Manager?
(Alt-PrtScn will capture the active window, or you can use the Snipping Tool)
bhiga said:
Your Network location is set to Home or Work, yes?
Can you post a shot of the Advanced tab of your network interface's properties from Device Manager?
(Alt-PrtScn will capture the active window, or you can use the Snipping Tool)
Click to expand...
Click to collapse
What are we trying to glean from this?

Chromecast not seen on network since 16664 update

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.

Unable to cast netflix

I used to use the netflix on daily basis until about three weeks ago I started to get the following message after a long time displaying the netflix splash screen on my TV: "Humm... It seems we're unable to connect". And then the netflix closes after 10 seconds. Every other chromecast official app works good, but Netflix. I also noted that if I restore the chromecast and launch netflix, everything will work. But if I cast other app, as YouTube for instance, and then return to netflix, I'll get the problem again, requiring another restore.
My chromecast software version is 16664.
Is anyone experiencing the something like that?
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I used to use the netflix on daily basis until about three weeks ago I started to get the following message after a long time displaying the netflix splash screen on my TV: "Humm... It seems we're unable to connect". And then the netflix closes after 10 seconds. Every other chromecast official app works good, but Netflix. I also noted that if I restore the chromecast and launch netflix, everything will work. But if I cast other app, as YouTube for instance, and then return to netflix, I'll get the problem again, requiring another restore.
My chromecast software version is 16664.
Is anyone experiencing the something like that?
Click to expand...
Click to collapse
Just to confirm, you're not using any DNS relocation/redirection (Unlocator, Unotelly, etc), right?
I just used Netflix the other day, and I'm still on 16664.
It's weird that everything else works except for Netflix, and also weird that factory reset makes it work. Could be a bug or perhaps something with WiFi connectivity. You don't have a WiFi repeater or multiple APs using the same SSID do you?
bhiga said:
Just to confirm, you're not using any DNS relocation/redirection (Unlocator, Unotelly, etc), right?
I just used Netflix the other day, and I'm still on 16664.
It's weird that everything else works except for Netflix, and also weird that factory reset makes it work. Could be a bug or perhaps something with WiFi connectivity. You don't have a WiFi repeater or multiple APs using the same SSID do you?
Click to expand...
Click to collapse
I use regular DNS. I also tried different WiFi routers and I always got this issue. Rarely Netflix works without need factory reset.
I was wondering if it could be a problem with the chromecast cache. Do you know a way to clear the cache without factory reseting?
luizm.jr said:
I use regular DNS. I also tried different WiFi routers and I always got this issue. Rarely Netflix works without need factory reset.
I was wondering if it could be a problem with the chromecast cache. Do you know a way to clear the cache without factory reseting?
Click to expand...
Click to collapse
Not that I know of... however, since the Netflix app is stored on Chromecast, there's a small possibility that it's a RAM or NAND issue on your Chromecast itself. If it's not rooted or special in any way, you might want to consider getting it replaced.
Or see if you can borrow another Chromecast to see if the problem is localized to your specific device.
bhiga said:
Not that I know of... however, since the Netflix app is stored on Chromecast, there's a small possibility that it's a RAM or NAND issue on your Chromecast itself. If it's not rooted or special in any way, you might want to consider getting it replaced.
Or see if you can borrow another Chromecast to see if the problem is localized to your specific device.
Click to expand...
Click to collapse
This is new for me. I thought Netflix was loaded online. I'll ask a friend that has chromecast to test mine in his home and and borrow his chromecast.
I'll let you know the results tomorrow.
Thanks
I borrowed a chromecast and first time it worked. After casting YouTube videos and then return to netflix, same thing happened. My friend got everything working great using my chromecast.
The only thing that never changed is my cable modem, but I never change anything on it. Moreover, why this is happening only with netflix and why it works if I factory reset are still a mystery.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I borrowed a chromecast and first time it worked. After casting YouTube videos and then return to netflix, same thing happened. My friend got everything working great using my chromecast.
The only thing that never changed is my cable modem, but I never change anything on it. Moreover, why this is happening only with netflix and why it works if I factory reset are still a mystery.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps you are seeing the first case of Net Neutrality biting you in the ISP?
See if you can reach Netflix via the browser...
I don't think so. I can access netflix anywhere else: tablet, phone, ps3 and computer. Besides, my friend use the same isp.
The only other place I having trouble in access netflix is my old Asus cube that I had retired since I got the chromecast last year.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I don't think so. I can access netflix anywhere else: tablet, phone, ps3 and computer. Besides, my friend use the same isp.
The only other place I having trouble in access netflix is my old Asus cube that I had retired since I got the chromecast last year.
Click to expand...
Click to collapse
Quite the puzzle...
Since your Chromecast works on your friend's network, and your friend's Chromecast shows the same behavior as yours on your network, the breakage factor definitely seems to be something about your network.
I really can't think of your cable modem being an issue unless isn't going bad (if it has an interface, look for excessive errors and/or poor signal quality - for example, Motorola SurfBoards usually have an interface at http://192.168.100.1/).
As your friend is using the same ISP, I would compare your router settings with his - ISP login type, routing and DNS in particular.
Of course if you have different routers then the router itself is still a variable.
I'll try to share my mobile Internet connection as soon I get back home to see if it will do the same.
Also I'll try to look the router log to see something.
Sent from my HTC One_M8 using XDA Free mobile app
I tested chromecast connecting to my phone in tethering mode. Netflix worked everytime. But when I got back to my regular connection, the problem appeared again.
So the problem seems to be located in my cable modem that also is a router.
Sent from my HTC One_M8 using XDA Free mobile app
Ok first question...do you have another router connected to the Modem Router? Are you using the Modem's built in WiFi or this other router's?
If you have another router then chances are likely you have a double NAT situation which is messing you up.
Check your other router and see what IP address is has listed under Internet connection...If it is a 192.168.xxx.xxx then it's a double Nat and you need to call your Cable company and have them put the Modem into Bridge mode.
If you do not have another router and use only the Modem router then you need to call the cable company and have them change the settings on the router to allow multicast and UPnP...Maybe a few other settings as well. Tell them what you are trying to do they have probably gotten lots of calls from others with the same issue.
Me personally I prefer to use my own router and have them put the Modem into Bridge mode so I have full control over the network and don't need to call them whenever I have a problem or want to change settings.
Asphyx said:
Ok first question...do you have another router connected to the Modem Router? Are you using the Modem's built in WiFi or this other router's?
If you have another router then chances are likely you have a double NAT situation which is messing you up.
Check your other router and see what IP address is has listed under Internet connection...If it is a 192.168.xxx.xxx then it's a double Nat and you need to call your Cable company and have them put the Modem into Bridge mode.
If you do not have another router and use only the Modem router then you need to call the cable company and have them change the settings on the router to allow multicast and UPnP...Maybe a few other settings as well. Tell them what you are trying to do they have probably gotten lots of calls from others with the same issue.
Me personally I prefer to use my own router and have them put the Modem into Bridge mode so I have full control over the network and don't need to call them whenever I have a problem or want to change settings.
Click to expand...
Click to collapse
My cable modem a public IP provided by my ISP, and a private IP that is 192.168.0.1. My router has a WAN IP provided by my cable modem (192.168.0.xxx) and a LAN IP 192.168.1.1. My chromecast used to be connected in my router LAN, but I changed it to connect directly to the cable modem router. I'll try to put the cable modem in bridge mode to see what happens as I have full access to its configuration.
Thanks again
luizm.jr said:
My cable modem a public IP provided by my ISP, and a private IP that is 192.168.0.1. My router has a WAN IP provided by my cable modem (192.168.0.xxx) and a LAN IP 192.168.1.1. My chromecast used to be connected in my router LAN, but I changed it to connect directly to the cable modem router. I'll try to put the cable modem in bridge mode to see what happens as I have full access to its configuration.
Thanks again
Click to expand...
Click to collapse
Yep that setup causes a double Nat situation Which doesn't work well for most networking applications....
Especially since you are also dealing with Two different Wireless networks.
Best setup is to have the modem just be a modem and send public IPs to whatever connects to it.
Then you won't have any Nat translation issues PLUS you get the ability (if your Modem has multiple ports like most Modem/Router Hybrids do, You can get a public IP for any device directly connected to the Modem which is good for running servers and for testing router issues.
Problem solved!
I turned off the wifi on the cable modem and put it on bridge mode, letting my router deal with my network. Netflix is now working good on both chromecast and Google tv.
However I believe the problem was related to a still unknown setting in the cable modem as I left it operating alone and netflix was still not able to load.
Thank you very much for the help. I really appreciate it.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
Problem solved!
I turned off the wifi on the cable modem and put it on bridge mode, letting my router deal with my network. Netflix is now working good on both chromecast and Google tv.
However I believe the problem was related to a still unknown setting in the cable modem as I left it operating alone and netflix was still not able to load.
Thank you very much for the help. I really appreciate it.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
it may very well have been a Router issue with the Modem...But now that it is only a Bridge the other router's settings will handle all the communication needed for the CCast and it should work...
As long as the settings on the second router were not the issue in the first place.

Categories

Resources