Ok @DMLUX1 , thanks for adding more details. So your wifi devices connected to your SSID need to access the following IP list: 192.168.20.50 (printer) 192.168.21.201 (Keiths Airtame) 192.168.21.122 (Joe V Airtame) 192.168.21.156 (Joe M Airtame) 192.168.21.117 (Philly Airtame) If wifi devices in your SSID are getting IP from Meraki AP (NAT mode) then your MR runs DHCP and does NAT for your wifi device traffic. In this scenario, your wifi devices don't get associated to a VLAN. As a result, there is no solution for you other than redesign your SSID. That's because your AP does NAT and so the wifi devices traffic gets kind of unidirectional - i.e.: wifi devices can initiate a connection to a LAN device but never the opposite way. Most screen-sharing requires BI-directional traffic therefore, this scenario would never work unless you redesign your SSID associating it with a switch VLAN. I'm assuming your printer lives in a switch VLAN (e.g.: VLAN20) and your Airtame devices live in another switch VLAN (e.g.: VLAN21); I'm also assuming your SSID is associated with yet another switch VLAN (e.g.: VLAN100). Am I correct? If my assumptions above are correct, then your Wireless firewall rules are correct and the issue might be related to: your switch or firewall doing the routing between VLANs has some Access Control List (ACL) denying traffic between these VLANs. So the solution is you add an Allow ACL. MS Switch ACLs are described here. MX Firewall Rules are described in this other Article here. your wireless screen-sharing relies on some broadcast or multicast kind of network traffic that requires them to be living in the same VLAN. Sometimes We can fix that kind of multicast traffic by allowing it to flood to other VLANs and switches as described here. Other few times you may need to convert Multicast to Unicast.
... View more
