I setup bridge1(include port6~10 and spf+1) in RB4011iGS+ and bridge2(all ports) in CRS309-1G-8S+, then connect spf+1 of the two devices.
My AD servers are in the bridge2, all computers in the bridge2 have no problem to join the domain.
All computers under the bridge1 are able to ping AD server and get the correct IP from DHCP of AD server.
But all computers under the bridge1 cannot join the domain (Can’t find network path).
On RB4011, you have /interface bridge settings set use-ip-firewall=yes. That isn’t necessarily wrong, but you want to check the /ip firewall settings if there are some rules which might interfere with intra-LAN traffic. While there are good reasons to have this setting set to yes usually that’s not needed …
Note that bridge firewalling might seem to work intermittently … because it only affects traffic which actually passes device’s CPU. With configuration of your RB that’s all the traffic through sfp+ (because that port connects directly to CPU) while it doesn’t necessarily affect traffic between ether ports (those are connected to switch chip). It also affects traffic through bonds (they are implemented in software so traffic between bonds and the rest of network passes CPU as well).
On CRS bridge MAC is set to the same value as port sfp-sfpplus6 … and probably interface bonding1 has the same MAC address. Both physical ports, members of bonding1, are also members of bridge (although disabled). You might want to set bridge MAC to some unique value (such as 76:4D:28:10:DA:37) and remove bond members from bridge (leave only bonding1 as bridge member).
Both devices are having same bridge priority (default value of 8000). Which doesn’t matter if there’s no loop in the connectivity (STP protocols fight against it). But it doesn’t hurt to change priority on one of devices to some other (round) value so that one of devices is persistently declared as root bridge. Which device should become root depends on topology, probably the center switch is a good candidate to become root bridge.
You’re saying that computers are able to join AD … meaning that L2 (ethernet) connectivity is just fine. Therefore the most suspicious is the item #1 in the list above …