· I use my ISP's router alongside a personal router.
ARC Status
· ARC is *Not Ready*
Roon Error Code
· None of these are listed. It simply says "TIMEDOUT" or similar.
System or third-party *firewalls *or *antivirus software* can sometimes block RoonServer from reaching ARC.
· Try adding RoonServer and its associated processes to the whitelist of any firewalls or antivirus software you have installed, including the Windows system firewall, if applicable. [You can learn more about firewall exceptions with Roon here.](https://help.roonlabs.com/portal/en/kb/articles/firewall)
Has the status in Roon -> Settings -> ARC changed after adding exceptions in your firewalls and antivirus software for Roon? ARC is still *Not Ready*
Don't give up yet.
· I'm stuck. I'd like to create a post to ask Roon Community for help.
This could be the cause of your problems with Roon ARC.
If you look at the Roon Settings → Roon ARC page using the normal Roon application (Windows or Mac) or Roon Remote (Android or IOS), then as well as the “Not Ready” indication that you have indicated above you should see some diagnostic text. It would be helpful if you copied that diagnostic text to a reply to this thread.
However, if you see “MultipleNATFound” in the text, then it means that the presence of the second router is preventing Roon Server from setting up the uPnP port forwarding that is necessary to make ARC work when connecting from outside of your home network. In this case, you may find that an earlier reply of mine to someone else with a similar issue will be of help:
Sorry I mean I have a personal router connected to the NBN modem box connected to the wall, rather than 2 routers. I don’t think that that setup would cause the problems that you mention.
This error seems to indicate that the router at 192.168.1.1 does not have a direct connection to the outside.
Can you make a note of your router’s WAN side ip address (if everything is working well it will not start with “192.168”, “10.” or even “172.x” where x is in the range 16.31). Then compare that ip address with the ip v4 address you get when you go to whatismyipaddress.com. Do not report either address here unless the two addresses differ and the router’s WAN side ip address starts with one of the non-routable address ranges that I listed just above.
If they are the same then everything is good and you just need to sort out your port forwarding. Try disabling uPnP on your router and setting up a manual port forwarding rule to forward TCP connections on the port indicated on the Roon ARC settings page (often 55000 or 55002) to the same port at 192.168.1.12 (your Roon Server’s ip address).
Alternatively, if they differ, then there is another address translation happening between your router and the internet. This may be NAT on another router in your network or it could be CG-NAT used by your ISP (although, from what I can find, Tangerine in Australia do not appear to use CG-NAT - I pressume you are in Australia). The use of CG-NAT is often, but not always, indicated by an WAN side ip address of “100.x.” where x is in the range 64 to 127.
Put simply, you’re one of several users with libraries of ~200,000+ who are experiencing poor performance with ARC. Diagnostics indicate a pattern of memory allocation failure between ARC and the operation system across these cases. There’s ongoing work to make ARC more nimble with large databases, but progress is incremental. You can expect gradual improvement over the next several releases, particularly on phones with more memory and processing power.
