ARC connectivity timeout with network errors (ref#HHCIT7)

Network Setup

· My only router was 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

Cannot connect to ARC
{
"ipv6_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"71.hhh.iii.jjj","actual_external_ipv6":"2601:aaa:bbb:ccc:ddd:eee:fff:ggg","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"status":"NotFound"}
}

Describe your network setup

ISP is XFinity, only one gateway/router, server is on a pc running windows 10 with extended support.

Hello @Dean_Heller

Thanks for reaching out. Can you please confirm if you have tried to set up a manual port forwarding rule for Roon in your router? According to the error code listed, it looks like your router does not support UPnP, so configuring a manual port forwarding rule would be needed. If you are unable to configure port forwarding to work properly, you can also use Tailscale:

I thought I had things configure but apparently I was wrong. I’ve now properly set up port forwarding and things are resolved.

Thanks

Glad to hear it @Dean_Heller!

We’re working on some improvements to ARC connectivity that should help make ARC more robust long-term. Please reach out in a new topic thread if anything else comes up.

Thanks!