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.
Roon ARC is not ready despite my router's UPNP setting for the roon core give automatic port permission.
The diagnostic in the roon app gives the following: { "ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "external_ip": {"actual_external_ip":"134.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"null"}, "natpmp_autoconfig": {"status":"NotFound"}, "upnp_autoconfig": {"server_ip":"192.168.178.1","found_upnp":true,"error":"<?xml version=\"1.0\"?>
s:Client UPnPError
606 Unknown Error Code
"} }
Rooter: FritzBox 7490 Roon Server: Innuos Zen Mk3 (connected to rooter via LAN)
Do you have a second router active in your network setup? If not, then this error usually indicates a CG-NAT (carrier-grade network address translation) layer upstream of your internet account. This is something your internet service provider will have implemented.
If you’re using enterprise-grade or corporate internet, I suggest contacting the IT department for steps to properly bypass CG-NAT. Otherwise, reach out directly to your ISP and inquire if either a dedicated IPv4 address or native IPv6 is available for your account.
Thanks Connor,
I contacted the ISP and they switched my account from dual (IPv4+IPv6) to IPv4 only.
We also restarted the Rooter.
Both actions without success.
The ISP is providing static IP addresses to business clients only.
Beside that, Roon ARC worked very well before the Innuos Zen Mk3 (my roon core) got updated. And I cannot imaging that innuos had the need of fixed IP addresses in mind when providing the update.
· 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.
You reported the same error with error code “606” four weeks ago here and it’s probably best if you continue working with @connor from Roon Support:
Right, but the system told me that this conversation has been automatically closed. Thus, I thought I had to start a new one.
Will contact Connor directly then.
Carl, thanks for merging.
Unfortunately, now the title is misleading.
I checked the UPnP configuration on my rooter. Everything seems fine with that.
Still roon gives me the failure message shown above.
