MacBook Pro 15" late 2018 model
CPU: 2.2 Ghz 6-Core Intel Core i7
RAM: 16 GB 2400 MHz DDR4
Networking Gear & Setup Details
MacBook Pro 15" late 2018 model
CPU: 2.2 Ghz 6-Core Intel Core i7
RAM: 16 GB 2400 MHz DDR4
Network Gear: ISP provided router, Linksys MX4200 Velop, connected via USB to my hub.
VPN: Proton
Connected Audio Devices
Klipsch R-51PM connected via USB
Number of Tracks in Library
About 7,000 tracks or 558 albums.
Description of Issue
I’m simply not able to get ARC to work. I have attempted an automatic configuration, a manual one with port forwarding and the other recommendations in your website, but nothing. The UPnP is enabled, I’ve created a static IP address, placed the correct port number but I get the same message every time. I attach a word document with the error message:
Thanks Suedkiez, my VPN is disconnected most of the time, I only use it for specific reasons. I have looked into the MultipleNatFound error which I understand is the problem, but I am not savvy enough to descipher the different terminologies used in my ISPs provided settings.
Could my MacBook’s specs be the problem? It is a renewed 2018 15" MacBook Pro with 16GB RAM DDR4.
Christian, try the steps in this post - if you do not get this:
then your provider might not give your connection a public ipv4 address (Carrier Grade NAT GNAT), and you will have to ask them to change it for you.
EDIT: Just noticed that the Roon error message shows the external ip as router_external 192.168.100.3 which is a private IP, which means that probably your linksys router is seen as the external router and not the ISP provided one.
Thank you for your post and for your patience. To clarify a question you posted before:
Specs aren’t the problem here - you’re encountering a redundant layer of Network Address Translation (NAT) in between your RoonServer machine and the internet, and this is preventing ARC from seeing RoonServer.
There are two likely sources for this second layer of NAT. Either you have a second router in your network performing NAT, or your ISP is imposing it in the form of carrier-grade network address translation, or CG-NAT. It’s also possible that the VPN, when active, triggers the multipleNAT message in diagnostics you posted, but let’s ignore that for now.
Is the ISP router mentioned above in Bridge mode? If so, then the more likely culprit is your ISP. I’d reach out to their support and inquire if they are imposed CG-NAT, and if they have dedicated external IP addresses available for your account tier to assist with port forwarding.
