Hi @pustekuchen

Thanks for posting in our business forum.

If you have set up the IP-Port Switch ACL to allow mDNS(5353), which is the ACL I talk about in that guide.

If you set up the protocol properly with the help of Wireshark, that's the Bonjour Service you need to create instead of imagining a thing called "NAS.local" as the Bonjour Service. If you don't know how to use Wireshark or the specific service name, go to your vendor and ask them about their mDNS service and add it manually.

That's basically the whole you need to debug for the mDNS. Or it is not a mDNS problem.

Hey, thanks for the response.

Yes, i've checked with wireshark

This are the packages, i receive with my windows client when im in the management VLAN1 192.168.0.*

If i switch the port settings of my EAP655 (which my Windows client is connected to with ETH Port), to PVID VLAN10. I never see any of the mDNS packages from my NAS again.

Some other do (from a printer)

So mDNS Proxy doesnt work.

Okay, i retried it again. And it seems get a response to the query now from the Gateway. I can ping NAS.local with success. But not NAS (without .local). This works in VLAN1.

What could be the problem with Pinging "NAS" ?

to successfully ping "NAS" i needed to add a rewrite rule to my dns server for "NAS.lan". I will try the other services as well like screensharing etc.