Trying to connect to my Core (Server) on my Windows machine with my Macbook Pro.
Core Machine (Operating system/System info/Roon build number)
Windows 10 / Intel i7-7500U CPU @ 2.70GHz 8GB / Roon Version 2.0 (build 1353)
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Core connected via ethernet / Remote via WiFi Eero Pro
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
External DAC connected via USB
Description Of Issue
My Roon core is not recognized by any of my Roon remote points, including my Macbook Pro and my iPhone app. I have checked the firewall settings on my Core machine, but I am open to suggestions because I am not an IT specialist. I wish Roon was plug-and-play like it used to be, but this update is (IN MY LOW-TECH OPINION) kind of botched. Please advise if you have any knowledge about what I should do. Thanks.
I would have to agree that something is broken. I am encouraged that people are reporting the issue. Hopefully, there will be a fix soon and Roon support will keep us posted.
I think many just don’t open new threads as they see there are already a bunch of - so Roon is aware. Though I think many are eagerly waiting for a feedback about the status and next steps.
Thanks for writing in about your issue! Since some time has passed, I first wanted to check in and see if you were still having issues connecting to your server?
If yes, I’d be curious to see if the same issue occurs when using a different device as a temporary server. Let me know if this is something you’d be able to setup and test out.
Our team is still investigating potential issues as well as solutions, so I hope to have more information to share soon.
Have you verified that your Windows Firewall settings are still set to allow RoonServer.exe, RAATServer.exe, and RoonAppliance.exe?
You can use these instructions to add the exceptions and the executables themselves would be located in your Database Location/RoonServer/Application folder path.
I would also add these exceptions to any Antivirus or other Firewall blocking applications you may have and ensure that you connected to your network via a Private network, not a Public one, see this guide for more information.