Windows 11 Pro
Intel(R) Core™ i9-9900K CPU @ 3.60GHz 3.60 GHz
Networking Gear & Setup Details
Ethernet and WiFI. No VPN
Connected Audio Devices
Number of Tracks in Library
Description of Issue
Roon App used to work until I changed my router. Now, even though everything is on the same wireless network, Roon App can’t find Core and hangs with message: Connecting… App still identifies the Roon Core by name and IP address but never connects…
More details of your network, and how everything is connected would be helpful. Particularly if the new router replaces old or is an addition.
One possibility is that the core is connected to your ISP router, and Wi-Fi is now provided by the new router. This often creates two separate networks.
To resolve this issue, connect the core to the new router.
New router replaced the old router. No other changes were made. All other devices work successfully off the new router. Music will still play from my PC (Roon Core) to my Cambridge Audio EVO 75 player across WiFi, if selected/started from the PC.
What doesn’t work is using Roon App, either from iPhone or iPad, to select and play music from the Core to the player. This used to work with the old router.
Thanks for that @Roger_Williams, can you please give your new router a hard reboot again to refresh your network?
To confirm, you have tested hardwiring your core via Ethernet directly to your new router?
If you could provide the router model, it would be good to double-check any firewall settings on the router that may be preventing Roon to be an exception.
PC is already using DHCP, if that was what you were asking. This is ridiculously complicated OR you have no idea what advice to give me. I don’t want to keep trying random things being suggested. You seem to have no claer documentation for what should be happening. Everything else on my network works perfectly, and as I said Roon on PC connects to my EVO75 over wifi perfectly too. It’s just the Roon app. I am paying a lot of money to use Roon and expect it to work as a real consumer product, not some techy networking puzzle from the 1990s…
Let’s go back to the screenshot of the Roon app I sent you. What is the app trying to do and why can’t I over-ride it in the app? Do you have an article that explains this?
@Roger_Williams, I appreciate that it’s frustrating when things go awry, but please be mindful that community members are volunteering support to assist you.
I’m taking this opportunity to remind everyone of the forum guidelines.
At the risk of annoying you again, can you make sure that your home WiFi network is set to Private network and not Public network in your Windows Network Settings?
When you first connect to a Wi-Fi network in Windows 11, it’s set as public by default. That means that your PC is not discoverable to other devices on the network.
Apologies to any volunteers trying to help me. I am still astounded that no-one from Roon Tech Support participates in this support group and appears to leave it to community users to support the product. If this was freeware, expectations would be different, but paying $120/year, users deserve more.
Can you help me further on this? You can see I am frustrated with the lack of any progress here, and the suggestions of the community are no help to me…
Yes, while I appreciate that you’ve become frustrated with the situation, I’m going to politely ask that a mutually respectful tone is observed in the resolution of your issue as we move forward. With a myriad of potential causes around your connectivity issues, it’s important to gain a full understanding of your system setup in order to troubleshoot properly, which you did not include in your original post. Based on your initial description, your router was the only thing to change in your setup. That was where my initial questions came from.
Based on your account information, I see you have both the legacy 1.8 mobile app as well as the 2.0 version on your remote devices. With your core now on 2.0, do you also have another core device on 1.8 you are running? If not, I would suggest removing the 1.8 legacy app.
With that, refreshing your RAATServer database may be helpful. Steps to follow below: