Roon ARC unable to access due to Network Error 526 and MultipleNatFound status (ref#8NXF8C)

Support
1

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· roon ARC will not be able to access your room server,{
"ipv4_connectivity": {"status":"NetworkError","status_code":526,"error":"error code: 526"},
"external_ip": {"actual_external_ip":"91.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"null"},
"status": "status": MultipleNatFound
,
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.0.1","found_upnp":true},
"multinat_autoconfig": {"status":"Failed","error":"Unexpected uPnP Control Response - See Log"}
}

Tell us about your home network

· tp-link archer AX11000, no vpn,

2

The error code 526 is currently appearing for everyone, even if their ARC works, because of the ongoing Roon cloud issues that are mentioned in the blue banner on top of the forum. See:

If you want to configure ARC with port forwarding, it might be best to wait until this is error code 526 is fixed by Roon Labs, so that it doesn’t get in the way. That said, the “MultipleNatFound” error in your diagnostic box is probably a real issue. Search for MultipleNatFound here:

If you are not using two or more routers at home, then the issue might be with your ISP and it may be difficult or impossible to overcome (depending on the ISP).

Generally, it is much easier to forget about port forwarding (and any and all errors that may appear in the diagnostic box) by simply using the Tailscale option to enable ARC access without port forwarding. See here:

And if you are running the RoonServer on Windows, continue here:

3

Hi @vitodeprins,

Suedkiez is correct regarding Error 526—this is a known cloud display glitch that you can ignore for now.

However, the MultipleNatFound status in your diagnostics is real. It means Roon detects two layers of network translation, which prevents ARC from connecting. This typically happens in one of two scenarios:

  1. Double Router: Your ISP modem is acting as a router before your TP-Link.

  2. Carrier-Grade NAT (CGNAT): Your ISP is not giving you a public IP address at all.

Option A: Fix the Network Configuration (If possible) To check if this is fixable via settings:

  1. Log in to your TP-Link Archer AX11000.

  2. Check the WAN / Internet IP address.

  3. Compare it with the IP shown on whatismyip.com.

  • If the TP-Link WAN IP starts with 192.168.x.x or 10.x.x.x, you have a Double Router setup.

  • If the IP starts with 100.x.x.x or simply does not match the website, you are likely behind CGNAT. In this case, standard port forwarding will not work.

Option B: The Tailscale Solution (Recommended) If you cannot change your ISP modem settings or if you are behind CGNAT, using Tailscale is the best solution. It bypasses these router restrictions entirely without needing any port forwarding.

Here is our official guide on how to set this up: https://help.roonlabs.com/portal/en/kb/articles/tailscale-setup-instructions-windows-roonserver

Let us know if you need help with the setup!

4

Hi @vitodeprins,

We’ve not seen a response and wanted to check in.

The cloud outage affecting the port test has since been resolved, so you should now see an accurate diagnostic message in Settings → ARC. Can you please share that here?

We need to ascertain whether you’re behind a layer of NAT at the local level (resolvable with router settings changed) or a layer of CG-NAT at the provider level (in which case you’ll need to resort to Tailscale).

5

We’re going to close this thread due to inactivity at this time, but you can reactivate the conversation by submitting a new support request here if you require more assistance. We’ll merge topic threads accordingly. Thanks!