Roon ARC connectivity issue with Mesh network due to "Multiple NAT" (ref#YBU64Q)

[Peter_Skinner]

Network Setup

· Do you have a mesh network? (Google Mesh, Eeros, Ubiquiti, etc.)

ARC Status

· ARC is *Not Ready*

Roon Error Code

· None of these are listed. It simply says "TIMEDOUT" or similar.

System or third-party *firewalls *or *antivirus software* can sometimes block RoonServer from reaching ARC.

·
Try adding RoonServer and its associated processes to the whitelist of any firewalls or antivirus software you have installed, including the Windows system firewall, if applicable.
[You can learn more about firewall exceptions with Roon here.](https://help.roonlabs.com/portal/en/kb/articles/firewall)

Has the status in Roon -> Settings -> ARC changed after adding exceptions in your firewalls and antivirus software for Roon?
ARC is still *Not Ready*

Don't give up yet.

· I'm stuck. I'd like to create a post to ask Roon Community for help.

Describe the issue

Roon ARC can no longer connect since I added a Mesh network. The problem appears to be a "Multiple NAT" issue. Adding manual port forwarding rules has not solved the problem. Please help!

Describe your network setup

ISP: EE (fttp connection)
Router: SmartHub Plus
Mesh Network: TP-Link Deco XE75 (connected to router via Ethernet)
RoonServer: Running on a Mac mini with macOS Sequoia 15.6.1 (connected to another XE75 unit via Ethernet)

ARC used to connect perfectly but since adding the Deco Mesh Network (to improve network speed/reliability) ARC can no longer connect).

UPnP is enabled on both the EE Router and on the TP-Link Mesh Network and I have added manual port forwarding rules to both but this has not solved the issue. (I have also tried disabling UPnP on either or both the router and mesh network but nothing has not helped.)

Here is the current diagnostic message:-
{
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"86.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"null"},
"status": "status": MultipleNatFound
,
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.68.1","found_upnp":true},
"multinat_autoconfig": {"status":"Failed","error":"Unexpected uPnP Control Response - See Log"}
}

Please can anyone help me to resolve this problem - thanks!

[Suedkiez (Just a fellow user like you)]

@Peter_Skinner

UPnP is enabled on both the EE Router and on the TP-Link Mesh Network and I have added manual port forwarding rules to both but this has not solved the issue.

(I have also tried disabling UPnP on either or both the router and mesh network but nothing has not helped.)

UPnP will never work if there are two routers.

And you can’t really have UPnP AND manual rules, (though with some routers you kind of can because some let you use UPnP for some devices and manual rules for others, but never for the same device, so that’s irrelevant here)

As UPnP won’t work with two routers and most likely interferes in such a scenario, definitely turn off the UPnP on both routers and create only manual rules. Even if it didn’t help, it’s a step in the right direction.

Then please describe the details of the manual rules.

[connor]

Hi@Peter_Skinner,

You mentioned that your provider is EE - it’s the experience of many users on this forum that they’re in the process of rolling out carrier-grade NAT for their residential-tier broadband accounts. It’s possible that their implementation rollout was coincidental to you adding the Deco.

Do the manual rules you’ve created in both routers match Roon Settings? If these manual rules are fully identical, then the multiple NAT diagnostic result is coming from EE’s CG-NAT.

I recommend reaching out to your provider to inquire if they have dedicated external IPs available or native IPv6.

Since you mentioned you have a Mac Mini, an easy way to traverse the NAT and get ARC working would be to install Tailscale. This is an alternative to port forwarding. It’s a safe and secure proxy-mesh VPN that will circumvent both the two-router NAT and the CG-NAT reliably.

Here’s a guide. Let us know if you have questions. Thank you!

Tailscale Setup Instructions: MacOS RoonServer

[Peter_Skinner]

Many thanks Connor. Tailscale installed and working perfectly - seems like a great solution!

[vadim]

Hello @Peter_Skinner

Thank you for the update. We are happy to hear that Tailscale helped to solve the CG NAT issue. Enjoy your music!