This is incorrect. Roon ARC does work with BT Home Hubs. You’ll need to set up a manual port forwarding rule and direct this to the Roon server. In addition, IPV6 should be disabled.
Alternatively, use Tailscale as described in thew above post.
Both @Suedkiez and @mjw have shared accurate information above (thank you!) and I feel it’s best to review what’s been shared to see if either solutions may work for you before moving any further.
Let us know your results, and we’ll be monitoring for your reply!
Bold statement and untrue. I ran mine for a couple of years without no issues at all. I tried port forwarding and then disabled it all and moved on to Tailscale. I’d highly recommend looking to to this option.
To explain what we have been through we have a couple customers in the UK that when our server is connected to a BT Hub (modem/router) they can see this on their Roon Remote app:
The port forwarding rule in your screenshot does absolutely nothing in a Roon setup without ARC.
To be frank, as a regular user I shudder to think that a company that clearly has zero grasp of networking goes around and changes Windows, including turning off its firewall, and sells the result for 14k to unsuspecting people who have even less clue.
Exactly. We’ve been saying this for a couple of days now.
Almost certainly something is preventing Roon server from discovering the remote, and by changing the port forwarding, the router restarted, and the issue was briefly cleared. My guess is that the issue will reappear if the server is rebooted.
But, as @AndyR suggests, turn off IPV6 in the Homehub.
Thanks for your post. In the experience of this forum, there’s no known factory-shipped setting on any tier of BT Home Hub that blocks Roon’s local discovery or handshake protocols, so we’d like to look at this more closely.
As stated above, Roon does not rely on port forwarding for any interaction with Roon Remotes inside the LAN. If changing this feature had an effect for you, it’s likely a secondary effect.
If RoonServer can reach upstream services and login, but spins when connecting to a Remote, we’d need to see the particular failure logged in the relevant server instance itself. If this is a modified Windows OS, I recommend ensuring that the Defender firewall or any other stateful network features have safelisted Roon. Roon’s port assignment is dynamic to an extent, so if there are port restrictions anywhere on this network, safelisting Roon’s processes becomes a surgical activity. It’s for this reason that we don’t often recommend Roon on enterprise or highly-managed LANs.
If you can zip up the logs and upload them for the particular RoonServer Windows machine with which you’ve been testing, we’d certainly like to take a closer look. You can use the directions found here and send over a set of logs to our File Uploader at your convenience.
