Thank you for the report and we’re sorry to hear that you’re having issues with ARC remote access.
The snippet you’ve posted suggests that an IPv6-format external address is available on your network, but your Core is unable to use the appropriate firewall pinhole to reach the broader internet and stream content (and authorizations, images, etc.) to/from ARC.
This problem has two common culprits.
A second router in the setup between your Core and the broader internet. ISP-supplied modem/router combinations, for instance.
Firewall settings on the upstream router (the Nighthawk, in this case).
A few suggestions:
In the web admin for the Nighthawk, try disabling IPv6 in favor of IPv4. Depending on your service provider, UPnP may then be able to connect via port forwarding.
If you do have a second router in the network, try removing it as a variable and connecting directly to the upstream router.
I also recommend disabling any VPNs you might be using.
I was able to access my core remotely from my office but only for about 30 min. When I got to my office I received a message that ARC couldn’t access the core but it played everything just perfectly! but again for about 30 min. Then the message was essentially ARC cannot connect to the core.
Hello, I tried to access my core from my office WiFi and ARC said it could not connect to the core. Do I need to do something similar to the office Comcast-provided/branded modem/router? Please advise.
Checking in. ARC cannot connect to core from WiFi while at work or anywhere . “Poor Connection” even though wifi tests well over 700mb per second. It connects while at home.
You said you’d keep a lookout for my response 7 days ago. Thanks for any help.