· ARC can’t reach Roon server - Moved to New House
Tell us about your home network
· I’m no expert and I think this is a bit complicated. I have an Arris G36 router which feeds an Eero mesh network and I also I have a Ring Gateway Pro - which I think provides cellular backup for Ring devices. It looks like I have multiple NAT issues, but no idea how to fix
ARC not reaching your Roon Server after a move usually points to the new network layout rather than ARC itself. With an Arris G36 feeding Eero, plus the Ring Gateway Pro in the mix, you may be dealing with double NAT or even triple NAT which can block inbound connections to Roon ARC.
Before we go further, a few things would help us confirm the path forward:
What device is running your Roon Server, and is it connected by Ethernet or WiFi?
Is the Arris G36 still doing router duties, or is the Eero set to bridge mode and handling routing instead?
Does the Ring Gateway Pro connect to the same internet line, or is it only on the local network for Ring devices?
As a starting point, we'd want to get this down to a single router doing NAT for the network that Roon Server sits on. The following guides will be useful while we sort this out:
I was able to get ARC to see the Roon server. Not sure if this was best way, but I was able to enable port forwarding on the ISP modem upstream from Eero which also has port forwarding enabled
Glad to hear ARC is working! The double port forwarding setup (on both the ISP modem and the Eero) can work but is not ideal long-term - you have double NAT between the Raspberry Pi and the internet. If you ever run into issues again, the cleaner fix would be to put the Eero in bridge mode so only one device is doing NAT, then set up port forwarding just on the ISP modem.
For now though, if everything is working enjoy the music!
