Today my ChromeCast arrived.

It doesn't connect to my WiFi on my RB2011UAS-2HnD.

First I thought it maybe an issue with my WiFi WPA2 password, there is a special character in it.
But if I try to connect it to another WiFi VirtualAP with an easy password, it still doesn't connect.

So I pulled my travel router (D-Link DIR-505) out of my laptop backback and it DOES connect.

Maybe distance (don't think so, because everything else connects at the same distane from the AP).
So removed my DIR-505 and plugged it in, near the mikrotik. Now the chromecast connects. No distance / signal problem.

Does anyone have any idea what possibly is going wrong in my MikroTik ?

Can you post your wireless settings?

Here is my config, I masked my passwords.
But tried all of my virtual ap's aswell, but doesn't work.
Tried it at work, where we also have a RB2011UAS-2HnD, also unable to join that network.

[admin@gateway] /interface wireless> export
# jan/02/1970 03:58:31 by RouterOS 6.13
# software id = D8SP-R40Z
#
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n bridge-mode=disabled channel-width=20/40mhz-ht-above country=netherlands disabled=no distance=indoors frequency=2472 l2mtu=2290 mode=ap-bridge name=RhinoTech ssid=RhinoTech
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk mode=dynamic-keys supplicant-identity=MikroTik wpa-pre-shared-key="*******" wpa2-pre-shared-key="********"
add authentication-types=wpa-psk,wpa2-psk mode=dynamic-keys name=jampinet supplicant-identity=router wpa-pre-shared-key="*********" wpa2-pre-shared-key="************"
add authentication-types=wpa-psk,wpa2-psk eap-methods="" mode=dynamic-keys name=guest-wifi supplicant-identity=router wpa-pre-shared-key=****** wpa2-pre-shared-key=******
add authentication-types=wpa-psk,wpa2-psk mode=dynamic-keys name=PokerNight supplicant-identity=router wpa-pre-shared-key=******* wpa2-pre-shared-key=********
add authentication-types=wpa-psk,wpa2-psk mode=dynamic-keys name=NicktNet supplicant-identity=router wpa-pre-shared-key=******* wpa2-pre-shared-key=*********
/interface wireless
add disabled=no l2mtu=2290 mac-address=D6:CA:6D:85:62:42 master-interface=RhinoTech name=NickNet security-profile=NicktNet ssid=NickNet
add default-forwarding=no mac-address=D6:CA:6D:85:62:41 master-interface=RhinoTech name=PokerNight security-profile=PokerNight ssid=PokerNight
add default-forwarding=no disabled=no l2mtu=2290 mac-address=D6:CA:6D:85:62:40 master-interface=RhinoTech name=guest-wifi security-profile=guest-wifi ssid=Rhino-Guest
add disabled=no l2mtu=2290 mac-address=D6:CA:6D:85:62:3F master-interface=RhinoTech name=jampinet security-profile=jampinet ssid=jampinet
/interface wireless access-list
add comment=iZiggo interface=RhinoTech mac-address=E0:F5:C6:92:3A:65
add interface=RhinoTech mac-address=6C:AD:F8:6B:AC:B1

Enable bridge mode on your wireless. Chromecast needs peer 2 peer communication on the wireless.

I enabled bridge mode, but still the Chromecast isn't able to connect.

Is it working for you now?

Well, It's a small step in the right direction.

Now the chromecast does connect, but it complains that it has no internet access.
Which is very werid because, if I let the chromecast connect to a portable/travel router it works.
If I let it connect to my old AP (retrieved from the dust) it also works, the weird thing is, that it uses the same DHCP server so it should be able to reach internet.

Well I find out that it is somehow a coverage issue.

The chromecast works in my living room, but not in my bed room.

It does work in my bedroom on my old AP, which is far less powerfull then my mikrotik, so that's a bit weird.

I'will see if I can fix that aswell somehow...

Thanks for all your replies.

hvwees, hello!

Just have solved same trouble: cannot connect chromecast to wi-fi provided by MikroTik (RB951).

Solution: switch "Channel Width" to (20MHz) and "Band" to (2GHz-B/G).

As I know connection problem relate to N-band or channel width.

Also work with AP mode but be aware that connection issue is due to "Default Authenticate" must be disabled !!!