![]() When you ping the devices, note the response message content so you can report it in any communication to Google Cast Support. If the device is unable to maintain the correct time, contact the device vendor. If the system time on either the sender or the receiver is incorrect, reboot the device and connect it to the internet. The system time on most sender devices (such as a phone) is mutable, but you should allow the device to get the system time automatically by connecting it to the internet. The system time on a Cast device is immutable and the device can maintain the correct time if connected to the internet. A disparity of as little as 10 minutes may cause authentication to fail. The authentication handshake between the sender and receiver can fail if there is a significant disparity between the system time on the sender device and that on the receiver device. If all apps of a certain platform fail consistently, while those of another do not, the problem may be with the platform. If your sender app is on the Android platform, run a different app on iOS, and vice versa. Run any app (not Netflix or YouTube) on a different platform than that of your sender app.When running your sender app on other platforms, is the discovery behavior the same? ![]() Run your sender app on a different platform (if possible).On the other hand, if all apps have problems discovering your receiver, the problem may be with your receiver or the network. If other apps are consistently discovering your receiver, and your sender app isn't, the problem is probably in your sender app. Run a different sender app (not Netflix or YouTube), and touch the Cast button to view Cast devices on the network.Observe the sender app and note the conditions under which it loses its ability to discover your receiver: what is happpening in the app? Is the time to connection loss consistent over several restarts? If the receiver device is now listed (discovered), there may still be a problem with the sender app. In the sender app, touch the Cast button to view Cast devices on the network.On iOS, double-click the home button, select the sender app, and swipe it away to shut it down.On Android, force the app to stop by using the Android system settings.Connect both the sender and the receiver to the same WiFi network.To get further assistance with your issue, gather all available information such as debugging logs, ping response data, and network service data, and use one of the support options described in Google Cast Support. The sender device and the receiver device must be connected to the same WiFi network.ĭo not attempt to resolve discovery issues while in guest mode.Īlso, see Debugging for more information about debugging your Cast receiver application.The sender device must have WiFi enabled and running.The receiever device is an official Google Cast device.The sender device is running a Cast app that you can use for testing.ĭo not use the Netflix or YouTube apps to test discovery, as these use some specialized discovery mechanisms.Because there are so many potential factors, and so many variables in the discovery process, these measures may not definitively prove any one cause, but they help you narrow down the possible causes.īefore investigating your device discovery problem, be sure the following conditions are established: This document describes ways to trouble-shoot for device discovery problems: the receiver does not appear in the list of connected Cast devices or, worse, the Cast button does not appear when you run the sender app. When device discovery fails, the issue may be with the app (sender or receiver), the Cast device, or the network. The sender app can then connect to a receiver device and begin casting. The Cast SDK performs device discovery, as described for Android, Chrome, and iOS, to provide the user with a list of available Cast receiver devices. If you find the device on these domains it is working fine and it is a router / NW issue.Īpp/ Radio / Chromecast Discovery Troubleshooting googlezone._tcp and / or googlecast._tcp.The device should appear in the following domains:.Connect the device and your PC to the same Ethernet network.You can verify this by using a bonjour browser if you are so inclined: Please review your router manual to make sure mDNS is turned on. Anyway, usually there's a setting to activate that in the router. This is odd because there is no security risk, that could be caused by doing this. Unfortunately some routers don't have forwarding of this traffic between WiFi and Ethernet enabled by default. The remote control relies on mDNS discovery to find devices in the network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |