Not ready - Roon ARC was unable to securely access your Roon Core: 2 routers

[Bill_Juvonen]

Roon Core 2.0 (build 1169) on NUC-I5

I have 2 routers: Asus RT-AX88U behind a T-Link using DD-WRT.
NUC is connected to Asus (10.0.2.20-static)

I got ARC to connect when initially setting up the NUC so know it works with my ISP (NextLight), but at that time it was on ethernet from the T-Link router (10.0.1.xxx). I stopped using ARC for a few months as it wasn’t quite stable enough yet, but I have a road trip coming up and would like to try it again.

I’ve: restarted my Core, turned off/on UPnP on both routers, manually setup port forwarding on both (Port is now 55002), rebooted everything, turned off/on firewalls, and read/tried everything I’ve found in the community…

Help, please

Diagnostics data:
{
“connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},

“external_ip”: {“actual_external_ip”:“161.aaa.bbb.ccc”,“router_external_ip”:“null”},

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

“upnp_autoconfig”: {“server_ip”:“10.0.2.1”,“found_upnp”:true,“error”:“<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/\” s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/\“><s:Body><s:Fault>s:ClientUPnPError<UPnPError xmlns="urn:schemas-upnp-org:control-1-0">718ConflictInMappingEntry</s:Fault></s:Body></s:Envelope>”}
}

Made some changes I don’t remember and now I get this:
{
“connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“161.aaa.bbb.ccc”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“10.0.2.1”,“found_upnp”:true,“error”:“doaction request return statuscode: ConnectFailure”}
}

WAN IP on 1st router is indeed the 161.xxx.xxx.xxx in the diagnostics screen

[Suedkiez (Just a fellow user like you)]

@Bill_Juvonen

ConflictInMappingEntry

Possibly UPnP still running in addition to your manual rules, or an error in the manual rules creating a conflict

[Bill_Juvonen]

I would assume PPnP could remain on with manual port forwarding, but…
I’ve added screenshots of my port forwarding to my original post

[Suedkiez (Just a fellow user like you)]

@Bill_Juvonen

I would assume PPnP could remain on with manual port forwarding, but…

Don’t assume. Yes, one might think so. In reality, not every router deals well with it and there have been numerous cases on the forum where this was the problem.

@Bill_Juvonen

I’ve added screenshots of my port forwarding to my original post

Thanks.

You normally need only TCP forwarded, not BOTH.
Shouldn’t “Source Net” have an entry? (I have no experience with DD-WRT)

I can’t see if UPnP is on.
Also check the Port Range Forwarding tab to ensure that there is no conflicting rule there

Check that the Roon ARC settings in the main Roon app show that it’s using the 55002 port.
Try clicking Reset in the Roon ARC settings in the main Roon app, sometimes it seems to help.

@Bill_Juvonen

I have 2 routers: Asus RT-AX88U behind a T-Link using DD-WRT.

I missed this originally. With 2 routers you probably need two daisy-chained forwarding rules. One on the T-Link forwarding the external IP:port to the Asus, and on the Asus to forward it on to the Core. And the 2 rules must not conflict somehow.

Try something like this:

ARC connection issues -intermittent

Hey @Victoria_Carlin, Thank you for the detailed follow up! Lets focus on the double-nat situation. I don’t see any mention of a modem in your network setup. Do you have a specific modem model you can share? Or, is the FIOS G3100 acting as a modem/router combo? Typically, with mesh setups, you have to create two port forwarding rules. One for the modem/router (G3100) to route to other router (Orbi), and another from the other router (Orbi) to the core. And to confirm, when you bypass the Orbi…

Cant Get ARC To Work with 4/5 g

Are you daisy-chaining port forwarding rules, one from the modem to the router and then another one from the router to the Core? You may / probably have to. I suggest you try this: The modem is the external interface that gets the ARC connection from the outside and it must be able to forward from its external IP & port to the internal network, this being represented by the router. This port forwarding rule on the modem should forward the port to the router. Set up a similar rule on the route…

A ConflictInMappingEntry error also occurred here, also with 2 routers, and was resolved by daisy-chaining the rules on the 2 routers:

Roon ARC port forwarding issue

Operating System is Windows 11 Pro My Networking hardware is the ASUS RT-AX82U WiFi 6 The results: -After numerous tests and reading on others posts here, the issue persists…I’ve gone into the settings of my ISP router and opened the ports 55000 - 55002, and on my ASUS Router via (WAN/Port Forwarding). -I’ve also set a Static IP through the ASUS router interface in (LAN/DHCP Server) -UpnP is enabled, NAT type is Symmetric -To add, my assigned IP as is shown in MyIPLookup is different than …

[Bill_Juvonen]

Thanks for all the advice! I did try disabling UPnP on both last night to no avail.
I’ll check out and try the other suggestions later today and report what works or doesn’t.

[ToneDeaf (Ozzie)]

Hello @Bill_Juvonen

It could be a red herring, but I updated my Asus router (GT-AX6000) firmware l last week to version 3.0.0.4.388_21617-g1288c22. Since the update , UPnP / automatic configuration of ARC seems to fail. It worked fine, reliably and consistently, before. It may or may not be related.

I have not bothered to troubleshoot this systematically, other than a router reboot and reboot of the Roon Server (to no avail). No reason, as I normally use ARC, if at all, with a ‘0’ port configuration and VPN, which is unaffected. And I just checked that opening and forwarding a specific port also still works fine as a fall back.

[Bill_Juvonen]

Update

After spending several hours yesterday trying all the various things suggested, to no avail, I ended up hooking my NUC (Core) directly into the TP-Link router, bypassing the Asus, and ARC connected without issue.

Today I tried with only the Asus and struggled to get a good connection. I ended up disabling all firewalls and antivirus on the computer and the router and rebooting everything and… Success!

The router settings at that time had UPnP on and Port Forwarding off (I never did get it to work with UPnP off and forwarding on). I then started trying different combinations and re-enabling everything one at a time, with varying success.

** After many, many reboots after making changes, I discovered that after nearly every reboot of the router, ARC would fail to start (even if no changes were made on the router). I needed to also shut down Roon and restart it to see what really worked and what didn’t (just Roon, not the NUC). Often it would start up successfully after restart even though it showed it failed prior. I’m thinking a lot of the things I tried yesterday would’ve worked just fine had I known that in advance.

I haven’t tried adding the second router back in… I may not. I put it in initially to try to isolate my IoT devices and cameras but found having two networks too cumbersome and I have strong passwords in place, so I’m not gonna lose any sleep… actually, I’ll lose less.

[Suedkiez (Just a fellow user like you)]

@Bill_Juvonen

I ended up hooking my NUC (Core) directly into the TP-Link router, bypassing the Asus, and ARC connected without issue.

That’s another way instead of daisy-chaining two rules. If it works for your ISP, it’s IMHO the better option if there are no specific requirements for two routers (I get the isolation attempt). Seems to me that half of the ARC issues are caused by such weird two router setups that their users often don’t actually understand in detail. (The other half by CG-NAT and similar that’s not providing routeable IP addresses, and a small rest by other minor issues like wrong rules or no UPnP enabled)

Dunno about the issue after router restart, but be aware that it can take many minutes after a restart of the router until it has established a connection to the ISP. In that time, nothing that needs internet will work. Make sure to wait long enough before drawing conclusions.

If it’s really not working after router reboot, might be an issue with the router and/or ISP. I never experienced that, but on the other hand I basically never reboot my router, so who knows