In any case, manual config of ethernet settings is almost always a bad thing to do, and it CERTAINLY is a bad thing when it cannot be done on both sides. Presuming you cannot set it on the TV side, you also should not set it on the router side! (i.e. leave it at auto negotiate)
Problem isn`t so simple. All "simple" things were tested. Different link speed, auto link, dhcp reservation time, static ip, upnp, add mutlicast, loop protect disable, disable all firewall deny rules, changed arp lifetime, different vlan for TV and chromecast laptop that has wired connection. That`s why the last chance is registration here and ask for help, i have no ideas what it can be.
I don't know such a mode on wired ethernet that requires more than the default auto-negotiate being enabled.I think it`s some specific standby mode that doesn`t support by default and need to be activated but i have no idea what it can be.
i`ve stopped at 14th page. All articles are around "Make chromecast work" and dated 2014-2017 years. In samsung tvs it starts from 7th series and, as i think, after 2018 year
I have tested it with my Philips TV with Android and built-in Chromecast.Cane somebody test chromecast on tv with mikrotik router?
I agree with you because i`ve tested this only with samsung 7series and lg with same chromecast version. But this issue appiars only when i use mikrotik router. Have some additional packages installed/configured which differ from default?I have tested it with my Philips TV with Android and built-in Chromecast.Cane somebody test chromecast on tv with mikrotik router?
It works fine. TV is in standby (connected wired ethernet), I turn on my HP Chromebook (which is on WiFi) and select casting, it already sees the TV and I can connect it, TV powers on.
Heck I did not even know that this works, I always turned on the TV using the remote control beforehand.
I also did not test this after a really long time in standby, like next day. I could try to remember to test that tomorrow.
But it looks like the blame is more with your TV than with the router...
Sometimes you have to value your time more than your preferred hardware, I don't have this issue as it works properly on all my Chromecast devices but if I had spent more than 8 hours diagnosing I would be looking for something else too.Couldn`t solve the issue. Ordered zyxel keenetic. My practice of Mikrotik usage and install for home usage goes to end after more then 50 installed devices.
I`ve spent days for this. Chromecast works fine on powered on devices and i can`t say that it doesnt work at all. The problem is with deep sleep when device become unreachable and i`m losing 30% of functions for my new tv devices when i can`t use chromecast, control from phone, can`t use tvs with smart home controllesr. I`ve bought new mikrotik device, unboxed it and connected to internet (dhcp from ISP), configured wifi and local network then one by one used all manuals from internet for chromecast configuration and all off them didn`t help me. TV still unreachable when it`s in sleep mode. Tested on same router two other TVs: sony and philips and they have no this issue so i can conclude that "probem" affects only webos and tizen. With ANY other router (i really tested ALL other manufacturers) in same condition this function works perfect.Sometimes you have to value your time more than your preferred hardware, I don't have this issue as it works properly on all my Chromecast devices but if I had spent more than 8 hours diagnosing I would be looking for something else too.Couldn`t solve the issue. Ordered zyxel keenetic. My practice of Mikrotik usage and install for home usage goes to end after more then 50 installed devices.
Thank you for reply. Static was the second thing that i did after cable connection. And yes, my other devices in standby mode work good too: vacuum cleaner (wifi), termal switches (wifi), door monitor (cable).What is the lease time on DHCP addresses? I have two Xbox One's that connect via swicthes (none MT units) to my core router (4011) and I had issues that if the Xbox one was in standby mode for more then the lease time I could not turn if on by using the app from my phone or see that it had renewed it's IP. I moved from 8 hours to 8 days. This solved the issue for me. Could be an issue with the Xbox but it was the same. On standby the port is 10 Mbit.
This was a few years ago and have not tested since.
Have you tested to add a static IP address to the TV to verify if it has to do with DHCP?
Edit: Should note that I have had other things working fine in Standby mode at the time of issues with Xbox One.
Maybe some basic check of the DIAL protocol flow is needed. We all know that the Mikrotik bridge mysteriously blocks some traffic (like in the many DHCP cases) and reacts to things like STP protocol set to "none", to work completely different as non-compliant bridge. I only have the Chromecast Ultra, and that is not linked to the sleep mode of the TV in the same way.as a built in.I should note that both my TV and my Chromebook were on the same LAN segment (not my primary segment but a special one for this purpose).
Probably it will not work correctly when you use different segments and rely on some form of multicast routing.
I don't have that on my router, there are 5 different segments but there is no multicast routing between them (and almost no normal routing).