I'm not completely clear on your situation. Do you realise that non-Domain computers can log in using RADIUS credentials still? If you use Systems Manager, then it can automatically deploy certificates onto computers (and mobile devices) and you can do certificate based authentication. And you don't need any servers ...
... View more
@Gustavo wrote: Hello @Uberseehandel, I'll try this configuration, Is it necessary to add a forwarding rule specific for jabber or only enable the option? There is lots in the documentation about this topic, but for starters see - Configuring Bonjour forwarding for the MX security device also the below from other Meraki documentation - Common Problems There are a few common problems that can arise when deploying NAT mode with Meraki DHCP to provide client addressing. These problems are outlined in detail below: Roaming - NAT mode with Meraki DHCP will use the IP address of the AP as the public IP address for wireless clients. When a client roams between APs with Meraki DHCP, TCP connections will drop and have to be re-established. This can cause problems with some applications and devices. Bonjour and multicasting protocols - The client isolation features of Meraki DHCP will prevent wireless clients from communicating with each other. This will prevent Bonjour, layer 2 discovery protocols, and multicasting protocols from working. This can cause problems in networks that use Bonjour among wireless clients, or have IP phones or applications that require multicasting. Inbound client connections - NAT mode with Meraki DHCP prevents inbound connections to a wireless client. This can cause problems if a wireless client needs to be accessible from a different network. . . . . A connection, such as a remote desktop session, from the wired client to wireless client A will fail. Other common examples include failed wireless LAN connections to Chromecast devices, AirPlay enabled devices, printers or projectors. good luck.
... View more