I would love to use ARC, but it just does not work.
ARC works perfectly well when I am in my house over the wireless network. Outside I receive the “poor connection” or “core unreachable” response even if I am on an enterprise wireless network at the remote location. I have done quite a lot of investigating, but have no clear conclusion about what causes the failure or what to do about it.
I suggested #support:port-forwarding-help and then there would have been a posting template with questions to tell us some more. You can copy this into a reply:
Roon Core Machine
→ Include your operating system and machine info (Model, CPU, RAM)
Networking Gear & Setup Details
→ Your network gear (model of routers/switches), if on WiFi/Ethernet, and if you are using a VPN
Who is your internet service provider?
Please list the make and model of your modem and router?
Do you have any additional network hardware, like additional routers or managed switches?
Does your network have any VPNs, proxy servers, or enterprise-grade security?
Connected Audio Devices
→ Specify what devices you’re using and their connection types, like USB/HDMI/Chromecast, etc.)
Description of Issue -
What is the exact port forwarding error message you see in the Roon Settings → ARC tab?
→ Tell us about the problem you’re having in as much detail as possible. Screenshots are always appreciated!
Outside on my home I receive the “poor connection” or “core unreachable” response even if I am on an enterprise wireless network at the remote location.
And Roon Settings → Roon ARC at home says “Ready” or is there an error message?
If it says “Ready” and the “Poor Connection” appears on the wifi as well, including the home wifi, it can usually be fixed by resetting the ARC app from Home > Settings. Sometimes, an uninstall/reinstall of the ARC app is necessary.
However, you will lose any downloads in ARC in either case.
This seems to happen sometimes after updating:
However, if it works on the wifi at home without “poor connection”, it is also possible that the enterprise wifi is blocking some traffic.
“However, if it works on the wifi at home without “poor connection”, it is also possible that the enterprise wifi is blocking some traffic.”
It works at home with out the “poor connection” or or “core unreachable” messages. It does not work at any non-home location, no matter what kind of network I try. Occasionally I can see a few files in ARC, but I never can play them. It is not just 1 enterprise network we are talking about. Travel notes, airports, wifi at businesses of all kinds, my car, ect…
Yes. Worth a try if it happens on all foreign networks. Although in the cases where this helps, the “poor connection” usually happens on the home wifi as well
Extensive testing away from the house, on a variety of wifi and cell conditions, all end with one of the afore mentioned 2 messages and ARC fails to play music.
Contacted Andrew Gillis at Small Green Computer and checked whether the previous generations of SonicTransporter i7 would have an issue with ARC. Hh confirmed that it should work.
Personally I would not waste time on the current version anymore and would wait for the next update. There is a slew of ARC fixes in the latest EarlyAccess beta update to address stuff like this. Maybe it helps. If you want to, you could of course switch to EarlyAccess now, or wait until it lands in production
Have you checked the app to see what it says in arcs settings in Roon as you don’t mention this even after @Suedkiez mentioned to do so. Just because it works at home doesn’t mean anything as it doesn’t use the port forwarding required for out of home access when on your home network.
It should show Ready like below. If not then it’s your local network or isp stopping it working. If this is ok then it could be your device or outside influences.
Apologies for the long delay in getting to your thread. Following up here, I’d be curious to see if you experience the same issues when temporarily setting your core up through one of your remote devices.
If possible, test out migrating your core to your Macbook Pro or your iMac, and see if the same issue occurs. Here is more information around this: