Unable to Connect to ARC with Timeout Error (ref#KWJ70T)

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

I am unable to connect to ARC. I am using a personal laptop, through ISP provided router.

I would get the following error message:

{
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"189.ddd.eee.fff","actual_external_ipv6":"null","router_external_ip":"189.ddd.eee.fff"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.1.254","found_upnp":true}
}

I have added roon, raatserver, and roonappliance to the Firewall allowed apps.

Describe your network setup

ISP: Infinitum (MX)
Network device: ZTE ZXHN F670L
Link: WLAN. through Cisco Anyconnect VPN. Though the issue is the same regardless on whether the VPN is activated or not.
OS: Windows 11

Hi @Mario_Spota,

Thank you for your post. It’s our understanding that TelMex infinitum has implemented carrier-grade network address translation (CG-NAT) on most of their residential fiber tiers. I recommend first inquiring with your provider whether or not your account is behind a layer of network address translation, as this will prevent the port forwarding from working. See if you can remove the CG-NAT layer.

If you’re still unable to connect after verifying CG-NAT is not active on your account, then I recommend trying Tailscale, a proxy-mesh VPN endorsed on this forum, as a workaround.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.