After updating to Build 1353 this morning I am currently unable to remotely connect to my Roon Server. I have Roon Server set to startup automatically whenever the Windows 10 PC it runs on reboots and this is still functioning properly after the update and there are no issues with sound output/quality. (Note: I only remotely connect to this machine / manage my music using the apps on my Android phone or Windows 11 PC, the PC server just sits on a rack in the corner of the house with nothing attached to it save an ethernet cable and the audio output cable).
All of my remote clients, whether on Android or my Windows 11 laptop see my Roon Server but can’t
connect (see screenshot). If I try to configure the server, I just get the “Searching for Roon Server” message. (see second screenshot).
Is there a fix coming or a way to roll back to an earlier build?
Hey Robert, thanks for the reply! I still see both executables in my Windows Firewall as both public and private (both have green checkmarks). Honestly don’t know if they were both checked prior as I just checked for the first time in two years. Other than that my network is still private. Any and all feedback is appreciated! Chris
Not sure if it helps, but I uncheck the Public exceptions for these. I saw in another post that you also may need a private network exception for roonappliance.exe:
I haven’t had this issue but may be worth looking into.
Robert, can’t thank you enough as the Roonappliance.exe mentioned in the post was in fact blocked and after re-enabling it in Windows Firewall all of my remote connections are once again working perfectly. Thanks for finding this post, appreciate you!
