What happens if you press the "Select a different Roon Server" button?
· I see my Roon Server, but I still can't connect.
When you try to connect, what screen do you see?
· I see the Server but the Connect button is grayed out
Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.
· No, the issue remains the same
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *Windows*
Select any of the following components that are present in your local network setup
· *Antivirus* *software *installed on RoonServer _or _Roon Remotes
You mentioned antivirus software. Please select the specific Antivirus you have from the list below
· None of the above
Describe the issue
My roon remote on Android phone and second computer (MacBook Pro) have always connected to my Roon server Windows 11 desktop fine. Stopped out of nowhere.
I've uninstalled and reinstalled roon on phone and it is trying to connect to the server it finds. Though it cycles the location between 192.168.7.151 and 10.0.0.233. never connects.
In Mac it finds and tries connecting to the 192.168 IP, never completing connections
Describe your network setup
Besides info I gave in previous step my music files are on a QNAP NAS unit connected to the Windows 11 desktop. And I have an Xfinity modem and eros network extender. All of these exact components have been working fine with my roon setup for years. Nothing has changed
Also worth noting that in Roon on my Windows 11 machine where the server is installed, it sees the MacBook pro as an audio device I could enable. And, before I reinstalled roon on my Android device, my main Roon install also saw that Pixel phone under audio devices.
From my main server on Windows 11 I have no problem playing out to all other audio devise connected to my home WiFi network and enabled in Roon as always.
Also, Roon ARC, still installed on my same Android phone, continues to connect and operate fine to play music from my Roon library on the Windows 11 machine. The Roon ARC listening port is showing Roon Server IP at 10.0.0.233 port 5000
Hi Bernd. I’m not terribly technically minding in these regards. But I can see the following:
Desktop Ethernet IPv4 address: 10.0.0.233
Desktop WiFi IPv4 address: 192.168.7.151
And for what it’s worth, I reach my QNAP NAS via browser at: 10.0.0.127:8080/cgi-bin/
It would be rather beneficial to reduce your network to a single IP range. Either 10.0.0.x or 192.168.7.x and have a single DHCP server handle address leases.
Unfortunately I don’t know both, your router and the network extender. Maybe someone here could chime in with some more knowledge of the devices in use?
I believe @BeeKay is spot on correct with their above comments - your issue here is very likely your Roon devices hopping between different local subnets. If you’re not needing two subnets, then I’d suggest accessing your router settings and disabling one of the subnets - this should force all your Roon devices to land on the same subnet and should absolutely help you with your connection issues.
Let us know how it goes, and what your results are afterward!
Thanks @benjamin. While I’m in no way technically fluent enough to understand in detail, I believe I actually do need two subnets, one for my QNAP NAS unit, and one for my main computer & router. This is how everything was configured “out of the box” years ago, all with Roon never having this problem in the past.
If disable 10.0.0.x, my NAS will not be reachable. If I disable 192.168.7.x all access to the internet on my main computer will be unavailable.
Is there no way to configure Roon to navigate this? Again, it’s been perfectly fine for years this way.
Hi @Noah_Weiner,
You can set an allowed range of IP addresses to only include one subnet in your router settings. That would still allow you to access the internet on both your QNAP and main computer while also making sure that your remote isn’t switching subnets. Is there a reason that this wouldn’t work for your use case?
@daniel thank you for the clarification, and sorry I didn’t reply sooner (I missed the email notification when you replied).
I follow your logic and it sounds like it should work, yes. I’ve navigated to where DHCP subnet ranges appear to be configured in my Xfinity router settings. But it seems like the (default) range is already restricted to not include the any of 192.168. subnet at all (image below).
Perhaps I’m missing something? There are obviously a lot more setting sections in my router admin section. But I’m at a bit of a loss already. Your help is very much appreciated.
Unless I’m missing something, are you able to change the IP of your NAS to the 192.168 subnet, and adjust your router settings to reflect the same scheme?
The second IP could very likely be from your extender - so you could investigate updating this extender as well.
We may be able to help more specifically if you’re able to share the specific make and model router and extender you’re using. Let us know!
I can’t really answer your question, mostly out of a lack of having dug deeply into trying any such things before. But allow me to give you specific make/model info so, perhaps you might help further.
Extender info:
eero Pro WiFi System (eero Pro 2nd generation + eero Beacon WiFi extender)
model: B010001
software version: v7.7.5-15
eero Pro IP address: 192.168.71
eero Beacon IP address: 192.168.7.195
and here from the eero app, some more details that might be useful?
Hi @Noah_Weiner,
I edited your screenshot to hide your WAN IP address. I assume this screenshot is from the router not the extender. Is that correct?
Is this meant to say 192.168.7.1? If so then your router and extender are in the same subnet now which is good. Has there been any improvement with your remotes being able to connect with your server?
That screenshot you edited (thank you!) is from the eero app on my phone, not the router, which I understand to be the primary Xfinity box which brings service into my home.
And yes, 192.168.7.1 - sorry for the mistype earlier. This IP is showing in the eero app as the IPv4 address under the primary eero Pro device.
Just some more context from yesterday and today: Curiously, while the Roon app on my phone was hunting to connect to the server (flip flopping every minute or so between trying to reach the Home Desktop via 10.0.0.233 and 192.168.7.151), I experimented by toggling WiFi off and on for the primary Windows 11 machine where I have Roon installed with my QNAP NAS music storage attached.
Once WiFi was back on, and connected to the WiFi via the eero Pro, the Roon app on my phone connected at 192.168.7.151. It was working! But short lived, as within a minute or so, it lost connection. In doing this several times, the app on my phone does stay connected a little longer than a minute or so sometimes. But eventually loses connection.
I guess this is just logical due the the root issue we’re trying to address. But I wanted to share it as new (to me) info.
Thanks for your patience so far, we’ll keep this thread going until the setup is fully functional.
Zooming out, the root issue here is that a) your QNAP (Roon storage location) is located on one subnet (10.0…)and b) your Roon Remotes are all connected to another subnet, possibly the network generated by your range extender (192.168…).
It looks like you have the QNAP and RoonServer hardwired to the Xfinity box, and everything else is connecting to the Eero by WiFi. The Windows machine connects to both.
If you can easily rearrange this setup to connect all of the units by hardwire to the range extender (eliminating the Xfinity router and using it as a modem), that’s a simple solution to this problem.
The ability for RoonServer to reach both your storage and the remotes in this configuration will depend entirely on the Windows network configuration and the Xfinity settings. There’s no Roon setting for managing multiple subnet connections simultaneously - Roon will connect to whichever network interface offers the most throughput.
How have you configured your Watched Folders in Roon?
Long-term, the most stable solution would be what @BeeKay had advised here, which is to restrict your entire network to one subnet. You’d need to reassign the QNAP to the 192. subnet, or in your router settings, prevent the WiFi and ethernet from generating separate subnets.
@connor, thanks for the reply and commitment to help me through this until I’m fully functional.
Yes, this is all correct.
I could give this a try since I happen to have a spare extremely long cable with which to do so. I assume it’d be wise to turn off all components in my stack first, then switch the cable to have the NAS wired into the eero, then power everything up. Is this correct? Everything ought to just “work” thereafter without additional configuration?
I can’t help but feel that your and @BeeKay’s second “stable solution” merits attention. And perhaps with a bit of hand holding I could pull this off more ideally. So, I did I little searching and seem to have found the spot where reassignments would be configured. But I’m feeling very all thumbs here, and would appreciate your guidance.
Do I just brazenly change the entry of the Fixed IP Address to 192.168.7.151 and hit apply? Or are there deeper level things to configure?
If it is so easy (that’d be great!), I assume the url from which I reach the QNAP would simply change from http://10.0.0.127/ to specifically http://192.168.7.151/? I’d like to confirm that before trying anything, since I fear losing access to the NAS in this process.
I’ll await your reply regarding both suggested solutions. And thank you in advance for the help here.
Regarding your caveat specifying “as long as that specific IP isn’t being used by another device,” I did my best to determine if another device is using that address. Google guided me to ping it via CMD prompt, which I did, finding this:
I’m all thumbs here, but it would appear that in pinging that IP there was, in fact, a device using it? I honestly don’t know for sure. Can you help me understand if 192.168.7.151 is or isn’t available for the task we’re trying to complete?
Assuming (hopefully) it is free to use (if not, please advise next steps), will I change the QNAP Fixed IP Address to 192.168.7.151 and also switch the Default Gateway from 10.0.0.1 to 192.168.7.1? Or should I leave Default Gateway alone? FYI, I reach my Xfinity modem via 10.0.0.1 currently.
Hi @Noah_Weiner,
You should be able to see all of the in use IP addresses in your router settings. So you should be able to use the to know for sure if the address is available.
The goal is to get everything involved with Roon on the same subnet. Do you have anything else running on the 10.0.0 gateway? If not it should be safe to switch it. Is your QNAP getting its IP address from the Eero or the xfinity?
You should be able to see all of the in use IP addresses in your router settings.
To the best of my ability to see the IP addresses from within my Xfinity Gateway Modem which, as I mentioned, I’m accessing at 10.0.0.1, it appears everything is connecting via that 10.0.0 gateway.
I see the eero at IPv4 Address 10.0.0.42.
I see 24:5e:be:7b:64:1d at IPv4 Address 10.0.0.127. I’m assuming 24:5e:be:7b:64:1d is the QNAP since the QNAP itself is showing 10.0.0.127 as its fixed IP address, as I mentioned earlier.
So you should be able to use the to know for sure if the address is available.
I see no other info in the Xfinity dashboard which is letting me know 192.168.7.151 is available since it mentions it nowhere. Since Xfinity isn’t showing 192.168.7.151, does that mean 192.168.7.151 is available for the QNAP?
Please recall that my eero app indicates that the eero Pro IP address is192.168.7.1 and it’s eero Beacon is at 192.168.7.195. the eero Pro is hardwired to the Xfinity box via ethernet cable.
In my eero app I see all manner of wireless devises in our home connected to it at a wide range of different IPs all starting with 192.168.7. I didn’t happen to see 192.168.7.151 anywhere while poking around.
Do you have anything else running on the 10.0.0 gateway?
I’m getting a touch confused. Is 10.0.0 the Xfinity modem? Only my desktop computer and the QNAP connect by ethernet cable to the back of the Xfinity box
Is your QNAP getting its IP address from the Eero or the xfinity?
The QNAP is connected to the Xfinity box via an ethernet cable. I have no idea how it or any devises get their IP addresses. So it’s hard form me to know how to answer your question, or where to look for the answer.
But since the QNAP indicates a fixed IP of 10.0.0.127, would that mean it’s getting it from Xfinity (into which the QNAP is wired via ethernet)?
Thanks for the follow-up and you have our apologies on any confusion so far!
Taking a few steps back, and based on your most recent reply, the easiest way to merge all your devices onto one subnet would be to disable DHCP on your Eero Beacon (essentially enabling bridge mode for the router), which would force all your devices to connect to the Xfinity box.
You can only enable Bridge Mode if your Eero gateway is connected to your Xfinity router. Once in Bridge Mode, your Eero network will stop assigning IPs and act purely as a mesh Wi-Fi system.
Here are more specific steps on how to put the Eero into bridge mode:
Open the Eero App on your mobile device.
Tap the Settings tab (bottom right).
Tap Advanced.
Tap DHCP & NAT.
Select Bridge.
Confirm the change when prompted.
After you’ve done this, reboot both your routers, and that should force your devices all onto the same subnet. Let me know if this helps!
