Unable to access Roon ARC after setup (ref#EXQWSB)

Support ARC: Port Forwarding Help
1

Network Setup

· My only router was provided by my ISP

ARC Status

· ARC is *Not Ready*

Roon Error Code

· “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }

Have you successfully located and enabled the UPnP or NAT-PMP settings in your router's web UI?

· I've turned UPnP/ NAT-PMP on and ARC won't connect

Select the Diagnostic Keyword or Text String

· ClientUPnPError501ActionFailed

· How would you like to continue with the network configuration?
I would like to try and find a solution for UPnP/NAT-PMP on Roon Community

Describe the issue

I am unable to access Roon ARC despite setting all the things required.

Describe your network setup

Starhub in Singapore. TP Link SH-EBB810V and Google Nest. Running a Roon Nucleus One

2

@Kiat_Lee are you able to post the exact error message you see in the Settings → Roon ARC tab?

3

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“222.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“192.168.0.2”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.86.1”,“found_upnp”:true}
}

1 Like
4

It appears you have two networks, one with IP addresses of 192.168.0.nnn and the other with addresses of 192.168.86.nnn. Do you have two networks or two routers in your network?

5

Hi! I have two networks running. The google mesh router runs off the main router which is also the TP Link Network. The Roon Nucleus One is one the google network.

Interestingly, I had the same set up with my previous Roon Core running on a MacMini. and there were no issues with Roon ARC. :slight_smile:

6

Roon requires that all Roon devices must be on the same network (or “subnet”). Is it possible to place your Roon Server and all Roon endpoints either on the same Google network or the same TP-Link network?

7

Both of them are on the same Google network. All my devices are. It is more of an issue that Roon ARC is not able to receive. :slight_smile:

8

The point being that ARC is attempting to connect with the roon server and has to pass through two routers to get to it. You will have to manually set up port forwarding on both routers for it to be able to do this - the automatic setup done by Roon will only be able to use the one router with the Roon Server in its network.

The other option is to use the Google mesh in bridging mode and just have one network in your home.

1 Like
9

Hello @Kiat_Lee

Thanks for the details. The issue with Roon ARC here is that it needs a direct path to your Roon Server, but in your setup it has to pass through two networks/routers. This is why the automatic UPnP/NAT-PMP configuration cannot complete.

To resolve this, you have a few options:

  1. Single Network Approach:
  • Configure your Google mesh to operate in bridge mode so that all devices, including the Roon Nucleus One, are on one subnet.
  • Perform port forwarding or enable UPnP.
  • This is usually the simplest solution and allows ARC to connect automatically.
  1. Port Forwarding Approach:
  • Keep both routers, but you will need to manually forward the necessary ports from the Nucleus through both routers to the internet.
  • ARC requires this if it has to traverse two network segments.

Essentially, for ARC to work properly, it either needs one unified network with port forwarding or UPnP or manual/double port forwarding through both routers.

Would you like instructions for the port-forwarding setup for your specific routers?

1 Like
10

Thanks for the offer. Yes, please. Thank you!

11

Hi @Kiat_Lee,

Thanks for the follow-up!

To allow traffic in, you’ll need to:

  1. Forward the desired ports from TP-Link → Google Nest.
  2. Forward the same ports from Google Nest → your device.

What You’ll Need

  • Your Roon Server local IP address (e.g., 192.168.86.20)
  • Your Google Nest’s WAN IP address (its address on the TP-Link network)
  • Your Roon ARC port number (check in Roon under Settings → ARC — usually something like 55000, but it may differ)

1: Reserve Static IPs

This ensures your forwarding rules stay consistent.

On TP-Link SH-EBB810V

  1. Log in at 192.168.0.1 or 192.168.1.1
  2. Go to Advanced → Network → DHCP Server (or LAN Settings)
  3. Find your Google Nest in the DHCP client list
  4. Reserve its IP (e.g., 192.168.0.2) — this becomes the internal destination for the first forward

On Google Nest Wi-Fi

  1. Open the Google Home app
  2. Go to Wi-Fi → Settings → Advanced Networking → DHCP IP Reservations
  3. Reserve a static IP for your Roon Server device (e.g., 192.168.86.20)

2: Forward the Roon ARC Port on the TP-Link

In the TP-Link web interface:

  1. Go to Advanced → NAT Forwarding → Virtual Servers (or Port Forwarding)
  2. Click Add New
    • Service Type: Roon ARC
    • External Port: (Use your Roon ARC port, e.g. 55000)
    • Internal IP: Google Nest’s WAN IP (e.g., 192.168.0.2)
    • Internal Port: same as external (55000)
    • Protocol: TCP (Roon uses TCP only)
    • Status: Enabled
  3. Save and Apply.

3: Forward the Roon ARC Port on the Google Nest

In the Google Home app:

  1. Tap Wi-Fi → Settings → Advanced Networking → Port Management
  2. Tap Add
    • Device: your Roon Core device (with the static IP from Step 1)
    • External port: same as your ARC port (55000)
    • Internal port: same (55000)
    • Protocol: TCP
  3. Save and Apply.

4: Confirm in Roon

  1. Open Roon → Settings → ARC
  2. Roon should automatically test the connection.
    • If setup is correct, you’ll see ✅ “Ready for use outside your network.”
    • If not, check that both port forwards match exactly and that your Roon Core’s IP hasn’t changed.

Hope this helps! :folded_hands:

12

Hi @Kiat_Lee,

Do you require any further assistance on this thread? Without any further response, the topic thread will close out due to inactivity.

Let us know and we’ll proceed from there. Thanks!