Roon Client Stuck "Enabling" Any USB DACs - PC

Tinkering
1

Roon Core Machine

  • Roon ROCK Version 1.0 (build 259) production
  • Intel NUC - can’t remember which gen, but I believe it’s an i5 with 8GB RAM

Networking Gear & Setup Details

I am using a custom built router running pfSense with segmented networks. This is achieved by using NICs with multiple ports. Roon ROCK is on a 192.168.10.xxx network. The PC with issues is on a 192.168.50.xxx network. Wifi devices are on a 192.168.20.xxx network and have no issues. The firewall in pfSense is configured in such a way to allow traffic between devices outside the 192.168.10.xxx network and the Roon ROCK. This is achieved by reserving an IP address based on MAC addresses and then allow traffic for those particular devices to get through to the Roon Rock. I am not using a VPN for anything related to Roon.

Connected Audio Devices

My main system is a WIFI connected Raspberry Pi4 with a USB DAC. This devices works flawlessly. I have recently built a new PC that will not let me add any USB DAC, hence this post. I have a second PC that seems to work, but I will do more testing with anyone who would help me out.

Number of Tracks in Library

Not sure on track count, but I have used 38% of 1848 GB available. I can add a track count when I get home.

Description of Issue

When enabling and naming any USB DAC devices on my new PC, it just gets stuck on “enabling” and never actually enables it. I can’t enable built-in system devices on the PC either. I have not tried HDMI devices or anything other than USB devices. I have, however, disabled all anti-virus software and windows firewall to test if that was messing with the Roon Client. I also created exceptions for Roon, but they were already in windows firewall due to the popup that comes up when you first open the Roon client software. This did not change anything and the DAC would still get stuck “enabling”.

3

Hello @Dakota_Edwards and welcome to the forum.

Roon requires all involved devices being on the same network. There is no support for your current network setup using multiple networks.

You might want to look into the #tinkering section of the forum in search for a solution to make Roon cope with your current setup if you wish to keep that (hint: you need to find a way to route multi cast traffic between your different networks). But it would IMHO be easier, and if you expect official support even required, if you could stick to the single network approach.

Disclaimer: I’m just another Roon user.

4

I don’t see how the firewall is the issue. The PC that was in this location prior to building my new rig had never had issues connecting and playing music on my Roon ROCK. The old righ was on the same IP address and everything.

5

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.