This diagnostic indicates that your Roon Server has tried, and failed, to work together with your router’s UPnP stack to open the port. This might be because UPnP hasn’t been enabled, but it’s more commonly because either:
a) a second router is active on the same network or
b) your ISP has implemented CG-NAT
If you only have one Orbi router with no ISP-provided gateway, then this will likely be CG-NAT.
If you do have a second router, you can try:
enabling UPnP in both routers
if that doesn’t work, creating a manual port forwarding rule per these instructions:
if none of this is working, your Windows 11 configuration will support Tailscale. This is a workaround to port forwarding that allows ARC to connect.
If you only rely on a single router and still encounter double-NAT, it’s most likely the case that your internet provider has implemented their own CG-NAT above the level of your account.
Tailscale will work reliably if you’ve already configured that at this point. However, another last-resort option is to reach out to your ISP and inquire if they have dedicated external IPv4 addresses available for residential-tier accounts.
Just checking in on this. Were you able to ask your ISP about getting a dedicated IP, as we suggested? If they’ve made any progress or you’ve run into questions, let us know and we can take it from there.
Thanks for getting in touch.
I’m sorry for the delay in response.
We do implement CGNAT (like many ISP’s are having to do so in recent times).
Generally it doesn’t affect standard use but it can impact external network access and server hosting.
Normally we’d advise on a paid static IP add-on which would resolve this but as you’ve been with us for 6 months without seeing an issue, I’ve raised this with our network team to see if there’s a workaround we can apply for you.