And you’ve set your ports to 55000 or 59659?
Yes, everything is currently set to 59659.
I am using “Roon Rock” and “NUC” interchangeably to refer to a small factor intel i7 computer that houses the Roon Rock software and nothing else.
Hi,
I am using an iMac running Ventura 13.
So, your ISP is no longer a “guy in a flat with 18 cats”?
I suspect that your new ISP is doing something similar, however. He will have the router that needs to be set up with port forwarding I think…
1 Like
Ha!
Yes, he is the guy in a flat with 18 cats. Well remembered.
The advantage of dealing with an ISP that comprises 1 dude and 18 animals is that you can chat to him in a bar, and get him to switch you from Cogent to his alternative feed, Orange.
But yes, whatever is wrong could be how he has set himself up.
I too am left with thinking that this is an ISP issue. But there is a small bell ringing about reading some story that Netgear’s Orbi router has some weird problem with Roon. But I have not been able to confirm. So I plan to go back to the Netgear forum and ask.
1 Like
I will ask him. Time to brush up on my spanish.
1 Like
necesito que reenvíes el tráfico en el puerto 59659 para poder usar Roon Arc
No bad.
I checked with my ISP and he says all ports are open.
This makes sense to me as in the past I have had no problem logging into storage, weather things, or cameras in my house.
OK, off to Netgear…
Having open ports is NOT the same as Port Forwarding… Your ISP needs to add a specific port forwarding rule to his router to explicitly forward all traffic on the port that Roon ARC uses to the IP address that is used by your Roon Core.
2 Likes
Hello, try to change your router from ipv6 to ipv4. ARC does not support the ipv6 protocol, only ipv4. It was my problem at first and once I managed to change the protocol, it worked immediately, until today. If your router does not allow you to change, talk to your internet provider so that they can do it for you. I hope it helps you. Good luck.
OK, I have passed your request onto my ISP with the relevant numbers. Will let you know what happens.
Hi
I can change my router to use IPV6. So I tried setting it to IPV6 Auto (there were many options).
It did not work (drat). Error message remained unchanged. Connection is still being refused at that port.
No, you must use ipv4.
Your ISP needs to add a specific port forwarding rule to his router to explicitly forward all traffic on the port that Roon ARC uses to the IP address that is used by your Roon Core.
Well, I did ask him and he did not find this a sensible suggestion. Nor do I.
The Roon IP address is coming from my personal router, not him. The numbers above are all local IP addresses. The port forwarding is happening in my house. I have to set up my router to forward a port to an internal IP address . Asking him to do it does not make any sense to either of us.
But then I do not understand how the internet works, so what do I know.
OK, I am done here.
It does not look like a roon problem. So I am going to set up camp on a netgear support forum.
But I leave with a question: this thread is searchable and will turn up on google. Is there any information above that really should not be in the public domain? Should I now be changing my IP addresses to stay safe?
Bye, but if I ever find out what is going on, I will come back and post what worked.
I think we had established last year that you have in fact a multiple NAT situation (i.e. he has a router and you have a router).
If this is the case then he needs to set up a port forwarding rule in his router to forward the port number used by ARC to the IP address used by your router and you need to set up a port forwarding rule in your router to forward the port used by ARC to the IP address used by your Roon Core…
The multiple NAT thing was 6 months ago. Since then we have stopped using Cogent, who owned the second NAT. Roon is no longer reporting a multiple NAT so I assume that is not the problem.
So he doesn’t have a router in the flat with the cats?
I do not know what lies in his lair. I am just going by:
- The IP address of the device that was acting as a second NAT belonged to Cogent, and sat in Alicante, 200 miles away.
- Now I am via orange, the cogent NAT no longer appears on traceroute pings.
- Roon is no longer reporting “MultipleNAT found”
I do not know or understand how I end up with a fixed public IP address (its now coming from Orange in Madrid) without there being a second NAT.
My router is set to get its IP address off the ISP. Again, I have no idea how that works.
…and while on the topic of stuff I do not understand: this is my router to the orange IP assigning thing
192.168.1.1 (me)
192.168.100.1
192.168.201.1
85.xxx.xxx.xxx
62.pool85-xxx-xxx.static.orange.es
Which looks like 3 changes of IP address!
As an aside, I tried the dangerous thing of setting the roon NUC as a DMZ , i.e. all ports open. Then checked to find Roon still could not reach it. The port was showing as closed to the public. Weird. Anyway , I quickly set all that back to safety.
Well, without a clear idea of what he has and what he is doing, I think the chances of success are close to zero.
I’ve edited your message to remove the public address from view.
To me it looks as though there are (at least) three routers in the chain - all of which are going to need port forwarding rules, but if your guy is not prepared to do anything (because he thinks it’s not sensible), then I think you should just forget about running Roon ARC.