Casting to Chromecast does't work anymore after updating Chrome version on January/2018
Reported by
geraldoe...@gmail.com,
Mar 19 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Turn on Chromecast and wait it to be ready for casting 2. Open Chrome browser on a laptop running Windows 10, go to "three dots" menu and try to send content to Chromecast device 3. Next message appears: "no casting device found" What is the expected behavior? The expected behavior is to find the device on the list, since I can see it from other mobile devices on the same wifi network What went wrong? Since updating Chromecast on January 2018, don't remember the day or the versión exactly Did this work before? N/A Chrome version: 65.0.3325.162 Channel: stable OS Version: 10.0 Flash Version: Chromecast device not found I already called Chromecast support, tried some WA and there was no solution, for now
,
Mar 19 2018
Adding 'Internals>Cast' component and 'TE-Hardware-Dependency' label as Casting device is not available at TE end to test this issue. Request someone from Internals>Cast team to please look into this issue and help in further triaging. Thanks..
,
Mar 19 2018
,
Mar 19 2018
Thanks for chrome-net-export-log! I've looked through it and didn't see any relevant network errors, so I don't think it is network - stack related.
,
Mar 20 2018
192.160.10.2 is a public IP and won't work as of Chrome 64. Chrome 67 includes a flag which will allow you to cast to public IPs, can you try enabling that flag (in Canary today) and see if it works? If not, please re-open.
,
Mar 21 2018
John's comment helped me to solve the problem. I just changed IP rank and now it works! Thanks to all of you. Regards. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Mar 19 2018