Hi all, following the issued I had depicted here -
As stated in the original post, I had resolved the issue I had, and the issue was that I had unknowingly switched ISP’s, and the new ISP put me behind a NAT. Once I sorted it out with the ISP, ARC started working again.
Well, that didn’t last very long and a couple of days later ARC stopped working.
I tinkered around with it and what I found out was that when I changed the port from 55002 to 55001 on both the Roon core, and on the port forwarding of my router, things started working again. When I go back to 55002, it doesn’t work.
Could it be that the ISP automatically blocks ports which it suspects have unusual activity? Has anyone had something similar happen?
Yeah. I have Deutsche Telekom as my mobile provider and ARC did not work for one night and day recently, then continued as normal. This was during a recent large-scale cell network outage in Germany, which however didn’t much affect DT.
A port scan from my phone to the Core suddenly revealed the port as closed, but only when the phone was in the DT network. The port was open and ARC worked from other LANs and from the Vodafone cell network.
I’m thinking DT might have closed ports either trying to protect them from whatever caused the outage, or they just closed down as much as possible when maybe they didn’t know what was going on, or it was a result of a technical issue that caused the outage. Or some unrelated glitch, but anyways such changes can happen.
Well it’s different for me because even at the core the ARC test page reported that it wasn’t working, and I couldn’t use ARC from inside my LAN or from the cellular network.
I guess if it is some automatic port blocking by the ISP then it will happen again in a few days for the new port, but I just wondered if it’s something ISP’s do. Seems strange to me, and it would be strange if that port is only blocked for my IP.
Shields Up is the long-lived, tried and true strategy for examining your open ports. It’s not easy to share links to specific pages in the site. If you go to https://grc.com, and navigate your way into Shields Up (which will take a bit of effort), you can have it scan common ports or specific a custom port.
The site isn’t pretty and the clickable elements don’t always look clickable. I don’t think the site has changed much since the 90’s. Dig around and look for the “User Specified Custom Port Probe” option. Type the number of the port you want to test. Here’s an example of what it should look like with one of the ports you mentioned filled in.
Then click the words “User Specified Custom Port Probe” and it’ll tell you if the port is open or not.