We use Lancom LN1700. These are very capable wireless APs, who have very strong routing functionality. Cisco were only the switches we use. Think this is sadly leading nowhere, the hardware will go...

@Tedd404 Regarding to Microsoft, exactly this scenario is more or less supported: https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/support-for-active-directory-over-nat It has...

@Tedd404 I´ve added some more info into the diagram to make the config more clear. And yes, you are right. Problem is to access the Active Directory Domain behind the NAT. Everything else is working.

@Loycelover- Nslookup resolves all DCs, Ping to the DCs works flawless. The moment i connect the domain integrated pc to the Omada (does not matter if wired or wireless), the domain logon takes ages,...

@Loycelover- Attached the problematic topology in screenshot. Think it makes the scenario clear. After the change to Omada, the PC cannot contact domain controllers anymore. DNS resolution works,...

We are running a new Omada ER7212PC on an external network, that is connected to our main network via fiber. Fiber connection goes directly to the internal corporate network. The Omada ER7212PC only...