Has anyone found a good way to troubleshoot and confirm these suspicions? This aligns with our experiences as well since adding more Chromecast devices and Google Home devices.
tcpdump -n host 224.0.0.251 and port 535381–90 of 118 posts
Has anyone found a good way to troubleshoot and confirm these suspicions? This aligns with our experiences as well since adding more Chromecast devices and Google Home devices.
tcpdump -n host 224.0.0.251 and port 5353ChromeCast is such a frustrating product. It does exactly what I want in theory. In practice I have to wait 10 to 60 seconds to get it to connect, or reboot my phone. I've started giving up and just using the computer attached to my TV. I don't think I've been having the particular Wi-Fi issue described in the article, but ChromeCast has been just slow and flaky in my experience. I've had both v1 and v2. It seems to…
I've got a pretty good ($100) TPLink router and a 100Mbps Comcast connection in my 1BR apartment. I can almost never find the 5Ghz channel and get constant drops on my laptop, particularly the Linux one. I've got a 1st Gen Chromecast, a Google Home Mini, and a Pixel XL. Sounds like this is my culprit. Finally.
I have the same router I bet (Archer c7) and I'm convinced it just hates Android devices in general. Every time my phone has a connection hiccup it takes several minutes to renegotiate DHCP... But if I turn off WiFi and count to 15 and turn it on, it reconnects in 3 seconds flat. I'm tempted to throw out my wifi gear but I'm having trouble who in the industry isn't total garbage, because I have an Asus AP that sure i…
"This is the single biggest reason we’re no longer recommending our former pick, the Archer C7. Though the C7 has great range and good single-device performance, it doesn’t have band steering, which means that it stumbles when several devices are connected and there’s a lot going on. The problem is compounded by the router’s relatively weak single-core CPU."
...our former pick, the Archer C7, leap all the way off the top of the chart into “oh, this is horrible” territory shortly past the 75th percentile — which means that roughly one out of every four page loads will leave you wondering if you should hit reload.
I've got a pretty good ($100) TPLink router and a 100Mbps Comcast connection in my 1BR apartment. I can almost never find the 5Ghz channel and get constant drops on my laptop, particularly the Linux one. I've got a 1st Gen Chromecast, a Google Home Mini, and a Pixel XL. Sounds like this is my culprit. Finally.
ChromeCast is such a frustrating product. It does exactly what I want in theory. In practice I have to wait 10 to 60 seconds to get it to connect, or reboot my phone. I've started giving up and just using the computer attached to my TV. I don't think I've been having the particular Wi-Fi issue described in the article, but ChromeCast has been just slow and flaky in my experience. I've had both v1 and v2. It seems to…
This is how everyone used to build computers, PCs just became the outliers due to way things went with IBM/Microsoft.
Now with the all-in-one models, it seems even PCs are getting back to those days.
Ah good, I feared Google needed to update their devices to stop DDOS-ing my home network, luckily for them they don't get blamed and we think that the router vendors should add more robust DDOS-protection.
Lots of anecdotal experience in this thread about how bad Chromecast is so I'd like to offer my opposite: Chromecast has been one of the nicest additions per dollar for my home. It has been working well for me for a year or so. I even used it today (for the first time in a week or more) while cooking and it worked like a charm first try. The only real problems I've had with it, I switched hardware, but used the same…
I've got a pretty good ($100) TPLink router and a 100Mbps Comcast connection in my 1BR apartment. I can almost never find the 5Ghz channel and get constant drops on my laptop, particularly the Linux one. I've got a 1st Gen Chromecast, a Google Home Mini, and a Pixel XL. Sounds like this is my culprit. Finally.
It sounds like it is only on wakeup of the chromecast? how often is that happening? It wouldn't cause 'constant drops'
ChromeCast is such a frustrating product. It does exactly what I want in theory. In practice I have to wait 10 to 60 seconds to get it to connect, or reboot my phone. I've started giving up and just using the computer attached to my TV. I don't think I've been having the particular Wi-Fi issue described in the article, but ChromeCast has been just slow and flaky in my experience. I've had both v1 and v2. It seems to…
So I'd check your router if you keep having issues.