Roon ARC stopped connecting despite unchanged network settings (ref#5YKCXE)

Support
1

Network Setup

· I use a single personal router not 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

· Something else

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 was connecting yesterday. Today it is not. No changes to Roon IP address. Port Forwarding did not change. I stopped UPnP and restarted it but no change:

Describe your network setup

ISP: SkyRunner
Orbi router with two sattelites
Same results from phone and desktop (wireless and wired)
Roon ROCK server

2

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“162.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.1.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>”}
}

3

Hi @Dave_Coie,
Thanks for reaching out to us about this issue. It looks like you are experiencing the same issue as this user. Roon Arc connection ClientUPnPError - ConflictInMappingEntry. They managed to solve this by using Tailscale instead of port forwarding. It is quite simple to set this up in ROCK. You can follow this help article. Let us know how setting up Tailscale goes for you.

4

Can you provide more explanation about how you reached this conclusion? As I said, ARC was working fine before. I have no idea what changed, but requiring Tailscale seems onorous.

5

It’s plain to see in the diagnotic message you posted. An alternative to using Tailscale is adding a manual port forwarding rule in the Sky router.

Use this guide, and use port 55000 (or what is displayed under Roon Settings → Roon ARC.( Choose type TCP.

6

This seems to ignore the fact that it was working fine until a few days ago and there has been no change to the Sky Runner router. I do have port forwarding configured on my router, which was required to get it working in the first place.

7

If you have port forwarding enabled, then you shouldn’t turn UPnP on, too. However, double check that resetting things hasn’t changed the port used by Roon. Therefore, check the port on the Roon Settings → Roon ARC page matches what is set up in the router.

8

Hi @Dave_Coie ,

That ConflictInMappingEntry means that something else is trying to use the same port as ARC is trying to use. It is possible that another application is trying to use UPnP and the router provided it to use the same port. You can try to perform a full reboot of your router (unplug/wait 30 seconds/plug back in) to see if that helps, or you can try to change the port / disable UPnP and leave just the manual forwarding rule. Let us know how this goes!

9

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