The help feature says I need to enable the UPnP or NAT-PMP in my ATT router which is Model 5268AC. I can’t find that in my router to enable it. I am using a Windows 11 pc.
@John_Dickerson, I moved your post to the Port Forwarding Support section. I am a fellow user but also have the AT&T Pace 5268AC. You need to create a port forwarding rule using instructions similar to these I created for another user:
The only difference is that you will need to put the IP address of your Roon Core in the 1) Select a computer section
I have that exact same router. For me, the Roon pinhole was already there. I just added one that I named Roon ARC. For me, I put in a range of 55000 to 55002 and it worked. Not knowing anything about any of this, I did it for both TCP and UDP, but I think Roon only uses TCP. By the way, that router does not do UPnP. Also, I doubt it matters, but I did not choose the device by IP address, I chose Nucleus from the list of devices connected to my router.
What if you remove (but not delete) the Roon rule and keep the Roon ARC rule active? I would also delete the second screenshot showing Status as it has your public IP address listed.
Which computer is the rule “Roon ARC” assigned to? Can you post a screenshot displaying your options under 1) Select a computer? In an earlier screenshot above, there appears to be many options available (SonosZP, Home-Theater, and an Android device ID)? Are there any rules associated and assigned with any of these other devices?
Sorry for all the questions, but my only connected device on my Pace gateway is another router which I let handle all of my LAN traffic.
Thanks for all your help! Maybe they will figure out what is wrong. The irony of all this is that my Plexamp does work remotely. I wonder what they do that Roon doesn’t. I prefer Roon…if we can get it to work.
A number of potential causes can underpin the diagnostic error you received in the ARC tab in Roon, but let’s start here:
I first recommend you verify you’ve added Roon as an exception to the Windows firewall on your Core device by following these instructions.
You’ll need to verify that the Roon executables are allowed through the Windows firewall, namely Roon.exe and RAATServer.exe. These executables will be visible in the folder path of your Roon database: databaselocation/Application. If you need help locating your Database on a Windows Core, here’s a guide.
Second, we’ve pulled routine diagnostics from your account, and there’s some indication that you’re using Roon with a VPN. Note that VPNs will interfere with port forwarding by translating the routable IP assigned to your router. If you are using a VPN, you’ll need to disable it to configure port forwarding and to use ARC. However, if you require your VPN to remain on for other uses outside Roon, note that Roon users are posting workarounds for accessing ARC via your VPN in the #tinkering and #roon discussion sections, like this one: ARC and a VPN - alternative solution?
We’ll follow up with next steps after you’ve verified these first two steps. Thank you for your patience.
I appreciate your update and sorry for the long delay. We will happily extend your trial since these issues have prevented you from enjoying ARC. I see it’s set to expire in a day, so I will tag the @accounts team to lean in for assistance. They can assist you with renewing and will reach out on this thread as soon as possible. Thank you again for your patience as support works diligently through the queue of ARC-related issues to circle back here.
I see from recent diagnostics in ARC that disabling the VPN may have defaulted your WAN IP address to an IPv6 format; I might double-check that you have IPv6 disabled on this Windows Core, or are prioritizing IPv4 connections. I’d do the same in the modem/router if that setting is available.
Please post any updated diagnostic messages. The most recent update of Roon automatically obscures routable IPs, so your anonymity isn’t at risk.
I’m reviewing our conversation and the comments from other users, as automated account diagnostics indicate that the timeout is persisting.
Forgive me for taking us back a step, but do you have a second router in this setup, by chance? If so, then you’ll need to set the same port forwarding rule in both routers for the Core to see the external IP here.
With NordVPN disabled, follow these steps to disable IPv6 on the Windows as a precaution: IPv6: How To Disable
Use the shortcut, Windows Key + X to open the Control Panel.
Open Network and Internet.
Open Network and Sharing Center.
Click Change Adapter Settings.
Right-click your connection and go to Properties.
Uncheck the box next to Internet Protocol Version 6 (TCP/IPv6) to disable it.
Once that’s done, please update to the latest version of Roon/ARC (released today, notes here) and restart your network hardware. I’m hoping the port forwarding will succeed after these steps, and please accept my apologies that we’ve been unable to resolve this more promptly.
