ARC stopped working due to network error with eero settings (ref#JO6KNG)

Support
1

Network Setup

· I use multiple routers, none of which are provided by my ISP

ARC Status

· ARC is *Not Ready*

Roon Error Code

· The ARC settings page says "Not Ready," but I can still connect to ARC via cellular data. I'm having another problem.

Describe the issue

My ARC stopped working suddenly and nothing has changed as all looks fine to me. I've attached some screen shots of the eero settings to make sure I'm not missing something.



{
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"104.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"192.168.1.203"},
"status": "status": MultipleNatFound
,
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.4.1","found_upnp":true}
}

Describe your network setup

AT&T Modem
Eero Pro
NUCi7

Worked fine since ARC release; suddenly stopped working and will not work.

2

Since the diagnostic text that you posted refers to ip addresses in two different subnets (192.168.1.0/24 and 192.168.4.0/24), it looks like you have two (or more) routers in your home network. Presumably your AT&T Modem is actually a modem/router (with multiple lan ports and/or WiFi (even if not used).

This would be sufficient to generate the MultipleNatFound error that you are seeing.

There are a number of ways that this can be reolved:

  • Elliminate the routing functionality of one of the routers either by setting the router that manages the ISP connection to bridge mode (or modem only mode) or by putting the other router into access point mode.
  • Configure manual port forwarding on both routers (uPnP will not work with two routers). On the ISP router add a port forwarding rule to forward TCP connections on the ARC port to the WAN side ip address of the second router. On the second router configure a port forwarding rule to forward the TCP connections on the ARC port to the ip address of the Roon Server. Manual port forwarding works best if the ip addresses of the devices are reserved in the DHCP settings of the router that issued then so that the ip addresses do not change (and thus avoiding the need to change the port forwarding rule).

Whilst there is no evidence that it is the case in your situation, the MultipleNatFound error can also be caused by the ISP using CG-NAT and the two causes are not mutually exclusive. From reading it appears that at least some AT&T broadband customers are on a CG-NAT service. If you are one of them you will not be able to get port forwarding to work.

To work around CG-NAT the recommended option is to use Tailscale.

This solution has the benefit that it will work with CG-NAT and it will also work with multiple routers and is thus a universal solution to MultipleNatFound issues.

3

I’m not sure what you’re suggesting then

4

Hey @jtwrace,

Thanks for writing in! @Wade_Oram is 100% correct in their above statement - with a proper option for a easier solution as well:

Due to the MultiNatFound error, your best bet would be to test out using Tailscale - with the link provided in his response I’ve quoted above.

Let me know if you have any other questions along the way! :pray:

5

It appears to be working with Tailscale now. Is there a way to remove the below error? I’ve changed the port number but my OCD still bothers me to have an error there.

image

6

If you are using Tailscale, this error is completely irrelevant because it pertains to ARC access to the Roon Server via port forwarding which you are not using. You can safely ignore it.

The only way to remove the error, to my knowledge, is to correctly configure port forwarding on an ISP service that does not employ CG-NAT - but if you do that, you don’t need Tailscale :grinning:

7

ARC works outside of the home as long as it’s coming from Tidal. All of my music on my NAS isn’t accessible from ARC while it is fine from Roon within the home. I’m at a loss as to what isn’t working.

IMG_6019
IMG_60191179×2556 198 KB

IMG_6018
IMG_60181179×2556 288 KB

8

Hi @jtwrace ,

If you can use ARC whilst connected to cellular data, then port forwarding/Tailscale are functioning without issue. You’d otherwise have an issue with session authentication and a banner error indication that ARC couldn’t see your RoonServer.

This generally indicates network throttling or packet loss in either a) the connection between RoonServer and the internet OR b) the connection between the NAS and RoonServer.

How is the NAS connected relative to RoonServer in the Eero network? Please list any network hardware in between. I’d also verify that RoonServer.exe and other Roon processes are safelisted in any firewalls, including Windows Defender.

I recommend resyncing ARC on your home WiFi once again for due diligence.

We’ll watch for your response. Thank you!

9

I was able to get the NAS working working again as a setting on the eero system for port forwarding changed.

As for packet loss, my Firewalla Purple has those specs for my network as you can see below. Out of curiosity, what do you want to see?

IMG_6052
IMG_60521179×2415 83.7 KB

10

Hi @jtwrace,

Thanks for the update.

We usually want to know of any managed (L3) network components that sit between RoonServer, endpoints, and/or the broader internet. Packet scheduling, spanning tree, and multicast settings can all dictate Roon’s ability to download and distribute (or in this case, upload) audio files to other devices.

It sounds like this case is resolved, but we’re happy to keep the thread open if you have additional questions or ongoing issues.

Please note that the most recent ARC update contains stability improvements for server-phone connection.

11

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.