· None of the above quite fits
· None of these quite match
· At least two issues:
· 2 issues - Roon ARC has never worked & the system will only pla through the system output, not through any other devices.
Further info: everything works normally with system output. With other devices - currently Kiwi Ears DAC - while the icon alongside the track name responds when I press play, the progress line at the foot of the page remains at 0:00 and nothing is heard. Then, after a while, a message appears - too many filuares, playback stopped. The device is enabled and set up to default.
I have reinstalled Roon several times but nothing corrects this - except, occasionally, the third third party device (Kiwi Ears) will fire up and work. I have the same problem with a Cubilux DAC.
I have a lot of music files on a Synology NAS on a wifi network as well as a numerous DSD files on an SSD attached directly to the computer. Neither source works with the Kiwi Ears or any other device. Only system output.
Given that the Kiwi Ears qoocsionally works there would appear to be a stbaility issue with the Roon software.
Hi @Nic_Garnett,
Thank you for your post.
Let’s first clarify some details about your issue with ARC. Are you having an issue with using ARC with a cellular connection (port forwarding), or are you unable to use the app even on your home WiFi?
Please share a screenshot of any diagnostic error message you see in the Settings → ARC page within Roon.
Concerning the issues you’re experiencing with playback: we can pinpoint the specific error Roon is encountering with playback on any given Zone once we have access to diagnostic logging. However, your Roon Server machine has so far not responded to our server requests for automatic log reports, likely due to network security or the machine being offline. At your convenience, please use the directions found here to locate and compress (zip) a set of RoonServer logs to our File Uploader.
We’ll follow up with what we find. Thank you!
Hi - many thanks for your speedy response. Attached is a screen shot regarding the first issue. As to the second issue, I think I have idenbtified that I have a network issue which results in system latency. I am now happily using different devices on the Roon system without difficulty - mafter allowing necessary time - so we can terminate this particular.
Hello @Nic_Garnett
Excellent point. Looking at that 10.18.142.17 address, there is a very high probability that you are behind CGNAT (Carrier-Grade NAT).
What is CGNAT and why does it break ARC?
CGNAT is essentially “Double NAT” performed by your Internet Service Provider. To save money on public IP addresses, the ISP puts hundreds of customers behind one single public IP.
It’s like living in a large apartment complex with only one street address. When Roon ARC tries to “knock on your door” from the outside, it hits the ISP’s front gate. Because the ISP hasn’t set up a rule to send that specific traffic to your specific router, the connection simply dies there. Your local port forwarding rules are ignored because the traffic never even reaches your router.
How to confirm it’s CGNAT
Log into your Bell modem and look for the WAN IP or Internet IP.
If you are indeed on CGNAT, a standard port forward will never work. You have two ways out:
Many thanks: your assessment is correct and I will proceed accordingly. Please consider both issues closed and accept my thanks for the thoroughly efficient way in which my concerns were handled.
Hello @Nic_Garnett
Thank you for the update. We are glad to hear that we were able to help you. Enjoy your music!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
