Roon Arc no longer available

[David_Flynn]

Core Machine

NUC8I5BEH3 I5-8259U, Samsung 250GB 970 M2, 8GB DDR4, ROCK installed

Network Details

NUC connected by Ethernet to splitter which is connected by ethernet to Linksys Velop Mesh master node, which is in itself connected by ethernet to router Virgin Hub 3.

Audio Devices

Cambridge 851N (Roon Ready) connected to Linksys WiFi
KEF LS50 ii
iMac (and Project Pre Box Digital S2)
iPad (Linksys WiFi)
iPhone (Linksys WiFi)
Sky Q (AirPlay)
Sony TV (Chromecast)
Sonos One (x2 WiFi)

Library Size

10500 tracks (connected to NUC by USB to a 4TB external hard drive)

Description of Issue

Roon Arc has been working well recently, but in the last few weeks it cannot connect to the core. I haven’t touched my set-up at all, so I’m assuming there’s either something from the Linksys update that has changed it, but wanted to double check. The diagnostic info is below. My Virgin router is modem only.

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“82.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/\“>\n<s:Body>\n<s:Fault>\ns:Client\nUPnPError\n\n<UPnPError xmlns="urn:schemas-upnp-org:control-1-0">\n501\nPAL_UPNP_SOAP_E_ACTION_FAILED\n\n\n</s:Fault>\n</s:Body>\n</s:Envelope>\n”}
}

[mjw (Here I am with a brain the size of a planet and they ask me to pick up a piece of paper. Call that job satisfaction? I don't.)]

The diagnostics you’ve provided suggest that UPnP is not properly configured on your router.

However, I note that you only mention one splitter. Is this correct? For correct operation, two should be used, i.e., reducing the number of cable runs. Please clarify.

[David_Flynn]

Hi, sorry for the delay, but thanks for coming back so quickly (I was travelling for a few days).

That’s interesting re the UPnP. I made a mistake, it’s an ethernet switch, not splitter. So the cable from the NUC goes into the ethernet switch (five ports), one of which is connected to the master Velop node, which is then connected to the router. This had historically worked, and the reason for doing this is because my Roon connection needed to be to the Mesh wifi, but so did other ethernet cables.

[David_Flynn]

Not sure if this helps, but here’s a fairly poor diagram!

Roon works perfectly across the house using the Mesh wifi, but Roon Arc has stopped (it previously worked on this configuration)

[David_Flynn]

So the good news is that after phenomenal help from Linksys, I managed to solve the problem (in so far as they were able to properly diagnose where the issue was).

It was a port forwarding issue, but both from a Virgin ISP and Velop mesh system. So to solve it, I created a specific port forwarding role in the Velop Mesh system browser. I then put my Virgin 3.0 Hub back into router mode so I could make sure UPnP was listed and created a port forward process there as well, before putting it back into modem mode (Linksys found that it was being blocked by Virgin and their system).

I restarted everything and it all works. Just wanted to add here in case anyone else has an issue.