Used ARC for a few months without any problems, but last night it couldn’t connect. The connection to the Core was too weak. It didn’t even work at home. Thought maybe a port change was the cause but it turned out not to be the case, its still port 55000. After a reset of Roon ARC, there was a connection again. So it could be OK. But now I see an error on my PC as well as on my iPhone SE 2022 and iPad Pro when I go to Roon > Settings > Roon ARC.
Roon ARC tests the connection but after a few seconds the message appears that Roon ARC was unable to access my Roon Core:
That’s weird because when I start the ARC app, ARC just works. This is how it is in my house. I wonder if it will work tonight during a train journey.
Unfortunately, no connection.
Outside my house Arc doesn’t function, there is no connection.
Port 55000 now doesn’t work outside but also not inside. My router setting for UPnP is enabled and the IP address of my Core is automatic enabled for port 55000 but that doesn’t work in the end.
What have I done to solve the problem. I entered a new port number for my Core’s IP address: 55500.:
The screenshot looks like an Ziggo (provider) router.
A couple of questions/remarks:
Do you have another router in the network chain? Just to be sure.
You have uPnP enabled in the router and you have a port forwarding rule. The ports overlap and that often results in an error. And the displayed server_ip isn’t the ip of your core. I prefer not to use uPnP. You can try to disabling it, leave the port forwarding rule enabled and restart your router.
If an AP isn’t a router than there is one router.
Your second remark:
When I discovered the problem I looked into the configuration of my router. There I saw this screen in Portforwarding:
As you can see there was no overlap. After I configured port 55500, because port 55000 did not work after all, and the problem was solved via my mobile, I also wanted to check it on my PC where I also wanted to set ARC via port 55500, but as soon as I opened ARC in Roon’s Settings, it selected port 55000 and that worked too. Very curious. Going back to my router’s configuration I saw both ports but also a third port that I had created in September due to connectivity issues. So from no overlap I have now gone to 3 ports and everything seems to be working… so far.
I have given permission for UPnP in collaboration with a friend to backup our hard drives with music files via our NAS. I’m not going to just take that permission away.
Hopefully I’ve given some more clarity and if you have any advice, I’d love to hear it.
I don’t understand this remark. As far as I know this is the IP address of my server, the SonicTransport, with the Roon Core. I use this IP address to enter my Roon Core and HQPlayer.
I see online that the TP-Link is an AP device so it doesn’t have a firewall. All the firewalling and NAT is done by the main router, the Connectbox.
It is weird that the server_ip in the diagnostic message on the Roon Core states 192.168.178.1 because most of the time that is the address of the Connectbox. And the ip address of your Core is x.x.178.220 as displayed on the Roon Arc tab and on your forwarding rules. Perhaps something messed up in the Connectbox.
You could try removing the manual port forwarding rule and then restart the Connectbox. And then see if it works.
Another thing you might check is whether the PC with your core is seen in the Connectbox: menu-option Verbonden apparaten (an image of my Connectbox below):
Hello Joost,
As far as I can see my server and the Core has on every picture I included the same IP address which ends with xxx178.220 . Even on this one where it is broken in two parts:
So that’s not a problem.
And yes I can see my PC and my server in the menu of connected devices. I can see all the connected devices, sometimes named as unknown and sometimes with the wrong name. It’s a mess with the connectboxes from Ziggo. Probably you know that.
Yes, that is why I have another router behind it and forward all traffic through the Connectbox to that one to do the firewalling.
Did you try removing the manual port forwarding rule and then restarting your Connectbox? And your might want to restart the TP-link and your device with the Roon Core (in that order) once your router is totally up and running again. If that doesn’t work I’m out of ideas.
