A few weeks ago I start experience connectivity problems trying to cast from IOS device. The solution until now have been to unplug the HDMI cable and power cord for a few minutes and then plug the Chromecast device back in. But now it is not working at all. I have used Wireshark to monitor the network traffic, and I see that the Chromecast does not use the DNS server settings in the DHCP configuration provided. Once it have received the IP address from DHCP Discover, Offer, Request and ACK frames it start sending DNS request to Google DNS servers 8.8.8.8 and 8.8.4.4 and continue to do so even through the firewall return ICMP error 107 - Destination unreachable. As it is a domain network all network devices must use the provided DNS servers from the DHCP settings, as external DNS requests are blocked. Is there a firmware update available to fix this bug? I have the wireshark capture log file available if needed
Actually this problem was solved using the very helpful support assistance from google. The problem was related to change of network switch to Unify and somehow the Chromecast did not work consistently with the new switch until a hard reset to factory default and a reconfiguration from scratch. It has since worked flawlessly Hope it can help someone if you run into similar problems
Update - after unplugging the power to device a couple of times, the Chromecast did start once using the DNS server from DHCP. I also have a wireshark capture of the network traffic in this successful scenario. It seems like random whenever it works or not from boot. But in all successful cases during the resent weeks, the Chromecast stop working after 1-2 days and I again must restart the device to restore connection. Very annoying and frustrating. Hope someone can help me track down this problem
Actually this problem was solved using the very helpful support assistance from google. The problem was related to change of network switch to Unify and somehow the Chromecast did not work consistently with the new switch until a hard reset to factory default and a reconfiguration from scratch. It has since worked flawlessly Hope it can help someone if you run into similar problems
I'm glad to hear that you were able to get support on this issue, and I really appreciate you coming back with your fix. Did you have any more questions or need any additional help?
We haven't heard back from Krikand, and it's been a few days, so I'm locking the thread. As always, feel free to make a new thread if you have any more questions or concerns.
