Roon ARC stopped, showing 'Not Ready' with connectivity errors (ref#JJPILV)

[Robert_Gould]

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

· 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 worked fine...and then stopped working. Not it says Not Ready. Here's the diagnostic: {
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"72.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"status":"NotFound"}
}

Describe your network setup

Roon Core SonicTransport connected to NAIM ND5

[BeeKay (Bernd)]

Does ARC work OK internally i.e. when connected to your WiFi?

[Wade_Oram]

I’m assuming that you are using an explicit port forwarding rule in your router since the Roon Server is reporting that uPnP and NatPMP are not found.

If this is the case, has the ip address of your roon server (the SonicTransporter) changed for some reason. If so, your port forwarding rule in the router will need to be updated to forward to the new ip address.

If this is the case, you can prevent the ip address of your roon server from changing by either configuring it to use a fixed ip address (outside of the range of ip addresses reserved for use by DHCP in your router) or, prefereably, set up an ip address reservation for your SonicTranporter in the router’s DHCP settings.

The latter is much preferably because it will cause many fewer issues if, at a later date, you change to a router using a different sub-net (e.g. 192.168.50.0/24 instead of 192.168.0.0/24) because the new router will just issue an address in the new subnet whereas, if a static ip address is used, it will be retained and render your SonicTransporter unreacheable by other devices on your network.

[connor]

Hi @Robert_Gould,

Please see the response above for a useful initial suggestion.

Who is your ISP? Users and team here are broadly familiar with the market offerings/availability of dedicated external IP addresses for users blocked by carrier-grade NAT.

[Robert_Gould]

[I had written below, and posted the response. Then I went back to Roon Arc settings and tried, again, to change the Port. For some reason, this time that worked and all is well again. So feel free to ignore below, but I leave it here just for the record.]

Thank you. I confess I understand very little of the suggestion. However, I think it already has an Address Reservation. When I go to the LAN Setup section, at the botton of the page is a table labeled “Address Reservation”. One of the devices listed is the sonictransport, and it has its own IP Address and Mac Address.

I should add, if I didn’t before, all of this was working just fine a week ago. and has for at least a year or two. The mystery is why it no longer does.

My ISP provider is Spectrum.