# No Local Audio Devices found on WIndows 10 Pro Remote **URL:** \ **Category:** Support\ **Created:** [December 10, 2016, 5:40pm UTC](https://community.roonlabs.com/t/no-local-audio-devices-found-on-windows-10-pro-remote/16947 "2016-12-10T17:40:04Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![AMP](https://community.roonlabs.com/letter_avatar/amp/32/5_5575768a8748004e209b776fc1b2916d.png) [@AMP](https://community.roonlabs.com/u/AMP)\ **Post date:** [December 12, 2016, 3:23pm UTC](https://community.roonlabs.com/t/no-local-audio-devices-found-on-windows-10-pro-remote/16947/4 "2016-12-12T15:23:29Z")
> [@Kirby\_Marshall](#): > > The only piece I did not list was switch The switch may indeed be the issue. Any chance you’re using Cisco managed switches (SG200 / SG300)? This all seems very familiar to me as I beat my head against the wall with a UPnP server running on a QNAP that was simply invisible on the network. Turns out that the QNAP and the switch were getting into a fight regarding multicast packets and the switch was winning by simply dropping them. Roon/RAAT uses multicast to find audio endpoints and I wonder if these packets are getting dropped in a similar way in your setup. If you are using a managed switch then the easiest way to test would be to substitute an unmanaged switch and see if it works. Otherwise check the configurations of the (network) devices on your network (including those which aren’t seemingly in play here) and disable any reference to IGMP snooping / multicast routing / UPnP. It’s also worth checking your QNAP to ensure that jumbo frames are disabled. This _shouldn’t_ make a difference for device discovery, but has been known to cause some strangeness in similar configurations. --- _[View the full topic](https://community.roonlabs.com/t/no-local-audio-devices-found-on-windows-10-pro-remote/16947)._