I run a Client/Server setup. Win10 Roon Core - > Server 2012R2 RoonBridge -> Mutec with no issues.
Was trying out 2016 Core w/RoonBridge. Win10 Roon Core will not see the Mutec/DAC in network section of setup. Both run static IP addresses. I can PING between each, I can map a drive between each, firewalls are tuned off on both (troubleshooting), both have no issues getting anywhere network wise - local or to the internet.
Server 2016 itself sees the Mutec as noted in the Mutec Control Panel. This is an ASIO driver.
Going back to 2012R2 and all works fine.
I have seen others who are running Roon - RoonServer on 2016 Core/GUI so it “appears” to be something with RaaT and 2016.
I don’t have your exact setup but I also just tried out server 2016 in core mode. I have Roonserver running on a server 2012 R2 machine in minimal server mode. With 2016 none of my Roon remotes can see Roonserver. Like you I can ping the PC, remote desktop into it, etc. Definitely some service is removed in core mode that is required by Roon. Roonserver also does not work in 2012 R2 core mode so if you want to use 2016 it seems GUI mode is the only option right now.
Looking through the RoonServer and its RaatServer logs - the Win2016 RoonBridge is never seen - or heard (broadcast)? The remote I am using (Win7), its local audio is seen, but not RoonBridge on the Win2016 Server.
Double-checked Firewalls off. I can ping numeric or name, I can remote desktop, map drives to each other, etc. Just seems if RoonBridge is not announcing to RoonServer.
I will test to see if this fixes my issue with Win 10 Roon Core not seeing RoonBridge on Server 2016 Core Mode.
I will update this thread after testing.
Windows 10 Roon Core
Windows 2016 Core - RoonBridge
Both have Static IP, Firewalls disabled (for testing), both have internet access, can ping each other by IP or Name, can map drives to each other, can remote desktop to each other, but Roon Core cannot see RoonBridge.
NOTE: There are people running Roon/RoonServer on Server 2016 Core. I have not see ANYONE using RoonBridge with this OS.
Viewing “about” using Remote (Win 7), Roon Sees the 2016 Server in the list, and sees the RoonBridge software. It also noted there was an update needed to RoonBridge. I updated to the latest version of RoonBridge and rebooted. (Both RoonBridge and RoonServer)
Windows Server 2016 -> Mutec -> DAC : The Mutec Driver and Mutec device is seen in 2016 through the Mutec Control Panel.
RoonServer Widowns 10 - In Roon Audio Options, the Mutec driver is not seen…
I’m experiencing the same issue. My RoonBridge is running on WIN2016 CORE and while the bridge is visible in the About window it is not listed under the networked devices in the Audio Setup. Now I’m using HQP on WIN2016 Core and it works without issues.
Update: just tried win2016 essentials in GUI mode and everything works ok. The RoonBridge is visible in the Audio Setup. So you are right @dshore, something is disabled in the core mode that stops RoonBridge from working.