· 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.
First, verify in your MacOS System Settings that RoonServer has local network permission access. Navigate to System Settings → Privacy&Security → Local Network and toggle this feature on for Roon.
Next, you’ll need to decide whether you want to pursue manual port forwarding configuration or resort to Tailscale instead. The latter generally offers a simpler setup and more robust connectivity experience between RoonServer and ARC, since it’s not dependent on port forwarding.
If you’d rather rely on port forwarding, you’ll need to confirm that the ISP router (the Helix) is in bypass/bridge mode. From there, manually assign a port forwarding (TCP protocol) in the Deco admin settings. Use the port number and IP address listed in Roon Settings → ARC.
Alternatively, you can keep the Helix router functions active (Disable Bridge mode) and apply the exact same port forwarding rule in those settings, as well.
We usually recommend Tailscale for Mac users. See here:
Unfortunately, I use Proton VPN. I think running Tailscale and Proton VPN could potentially cause leaks. I will try port forwarding. Will update on my progress!
You’ll need to manually configure port forwarding in a two-router setup by setting the same TCP port forwarding rule in both router system administration settings pages.
This rule should point to the IP address and port listed in Roon Settings.
Your ISP may have be using their own carrier-grade NAT (CG-NAT) that will block the port above your account level. If you still get an error in Settings → ARC within Roon after setting the TCP rules in both routers, then reach out to the ISP and ask about the availability of a dedicated WAN IPv4 address.