· I use a single personal router not provided by my ISP
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.
Describe the issue
Roon Arc not ready
Describe your network setup
On EE Broadband using Asus RT-AX59U as the router. My PC is the roon server connected to the router via wifi.
Note: I don’t use uPnP so all my port forwarding rules are manually configured. If you use uPnP, your rules may appear in the lower part of the page under the “UPNP, NAT-PMP and PCP forwards” heading.
The information I found while doing a search was scattered and confused. Some recent posts indicated EE had gone to full CGNAT for everything. That is why I suggested the OP contact his ISP to find out for sure.
This is not the same page. This is the WAN setting page where you add an explicit port forwarding rule.
If you go to the system log (on the left near the bottom) and then select the ‘Port Forwarding’ tab, you should see both the explicitely added rules and the rules added by uPnP/natPmP.
However, if you have uPnP turned on and you have this explicit rule, it may explain why you are getting the ‘ConflictInMappingEntry’ error in the diagnostic text.
You should either (both not both):
Delete the explit port forwading rule on the page thatyou have just shown and let uPnP configure the port forwarding.
Turn uPnP off (and use the manual port forwarding as you have it at present).
If you do the latter, a manual port forwarding rule, it may be a good idea to use a DHCP reservation to ‘reserve’ an ip address for your Roon Server so that it always gets the same address. This can be done in the DHCP tab of the LAN settings page. If you do not do this, then, at some point in the future, the ip address allocated to your Roon Server may change and then your explicit port forwarding rule will cease to work.
DHCP address reservation gives you many of the advantages of a static ip address for a device on your local network without the possible issues in the future if/when you change routers or, for any other reason, change the subnet that you use on your LAN.