This is the cause of the MultipleNATFound error - at least in the first instance.
I can see two non-routable ip addresses in the diagnostic text that you have posted. Your Roon Server is on 10.0.0.1 whilst the WAN side ip address of of the router to which it connects (presumably the ORBI) is 192.168.1.64. These ip addresses are in different subnets and are both non-routable - meaning that they both reside on your local network.
So I believe:
You have an ISP supplied router with a WAN side ip address 71.aaa.bbb.ccc (obfuscated as in the text your quote) and a LAN side address of, probably, 192.168.1.1 or 192.168.1.254.
Your ORBI router with the WAN side port connected to a LAN port of the ISP router. The ORBI router has a WAN side IP address of 192.168.1.64 and creates a LAN probably with a 10.0.0.0/24 subnet and, guessing now, a LAN side ip address of 10.0.0.254.
In order to fix the MultipleNATFound issue you need to elliminate the two subnets by changing the mode of operation of one of your routers to prevent it doing any actual routing (NAT and DHCP).
The can be done be doing any one (and only one) of the following:
Put the ORBI router into Access point mode (so that it provides WiFI access but leaves the ISP router doing all of the other router functionality - routing, NAT and DHCP).
Create a manual port forwarding rule on both routers (with uPnP disabled on both). On the ISP router you need to create a port forwarding rule to forward TCP connections on the ARC port (as shown on Roon ARC settings page from which you got the diagnostic text) to 192.168.1.64 (the WAN side ip address of the ORBI router). On the ORBI router, you need to create a manual port forwarding rule to forward TCP connections on the ARC port to ip address 10.0.0.1 (Your Roon Server).
As an alternative to this, you can ignore port forwarding and use Tailscale to create a VPN which allows ARC to connect to your Roon Server as if it was connected to the same router as your Roon Server. This is slightly more difficult to do if you use a RoonOS device (NUC/ROCK or Nucleus) because it requires another ‘always on’ computer - even if only a small SBC like a RaspberryPi.
The Roon Help Centre article describing how to use Tailscale can be found at:
Kind thanks for takin got time to write his detailed and helpful answer. I hope it helps others.
I went with your suggested option “2” and put my router into bridge mode, letting the ATT router do its thing. This removed any NAT related messages, but ARC still wont work only now the error yields no Diagnostics Data.
I will try and dive into my Fiber Optic ATT router’s options and see what may be causing issues, I would love some suggestions in that regard.
Presumably, in the Roon → Settings → Roon ARC page (where the diagnostic text is displayed), the connection status summary is ‘Ready’ with text ‘Roon ARC can securely access your Roon Server’.
At this point, in Roon ARC you could try the following:
Logout of Roon ARC (In Roon ARC → Settings, scroll to the bottom of the screen and select ‘Disconnect from Roon’ and then log back in.