Roon Core Machine
Roon Client 1.8 Build 884 on custom-built PC, running Win11 Pro. EVGA X-299, Intel i9-9900X, 32GB RAM.
Roon Server 1.8 Build 884 running on Synology NAS DS920+
Networking Gear & Setup Details
Cisco CBS250–24T Switch, Netgear Orbi 850 Mesh Wifi AP
Connected Audio Devices
Cambridge Audio DACMagic 200m, AudioQuest Dragonfly Cobalt
Number of Tracks in Library
Small library, 606 albums, 7700 tracks
Description of Issue
Roon doesn’t see client PC or USB connected devices plugged in; only network connected devices. No option to manually add device. Outside of Roon, each USB device is functioning as expected. Just not able to use with Roon.
Not 100% sure; however, I think this occurred following PC upgrade to Win11/Roon 1.8/build 884.
As a quick check turn off Windows firewall (or if you run a different virus / firewall software turn it off) and check again…
Thanks for the suggestion. I wouldn’t have expected USB connections to be blocked in Roon by the firewall - I use McAfee.
Roon manages audio devices in a separate program from the main Roon app, for a number of reasons. Roon communicates with the audio program using networking mechanisms. It’s a bit silly that firewalls are able to interrupt this, but they can do so when misconfigured.
I am not personally familiar with McAfee, but there is probably a way to configure it so that it doesn’t interfere with this communication.
It appears that the firewall just needed to be cycled off/on. Coming back this evening (with the firewall restored) and a power-off/on cycle between, everything is connecting as expected. No manual firewall adjustments were needed.
Thanks again, you guys – that was just what I needed.
Roon discovery is probably blocked but now that things are discovered you can enable the fw again (at least for a while). I don’t like, for machines where I have enabled a fw, to just shut it off. So, good you’re able to turn it on now and things still work without having to reconfigure things. I suspect at some point in the future you’ll need to cycle again.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.