Cannot Connect to Roon Arc on Synology DS920

[Tack_J.eel]

Suddenly i cannot connect my Roon Core to Roon Arc

here is

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

[connor]

Hi @Tack_J.eel,

Thank you for your post and we’re sorry you’re suddenly encountering a port forwarding snag.

Your diagnostic message contains a ConflictInMappingEntry line, indicating that the port Roon has attempted to assign to an automatic rule in your router via UPnP is already in use by another process or program.

Often, this is the result of a VPN or other streaming software that has reserved a range of ports. You can try changing the port listed in Roon → Settings → Roon ARC to a different number in the 50000-65000 range to start. Also check to make sure a VPN, proxy server, firewall, or other software isn’t interfering here.

Occasionally, the port mapping conflict is the result of outdated router firmware that interferes with the UPnP stack. Restart you network hardware and toggle UPnP on/off, just in case.

Lastly, certain implementations of carrier-grade NAT will trigger this error. Who is your internet service provider? It might be worth verifying that they haven’t rolled out CG-NAT to your account tier in the last few weeks.

[Tack_J.eel]

This was caused by the firewall settings in Nas. Thank you.