Who is your internet service provider? Generally, we can resolve the issue knowing this alone, as weâve accumulated experience with most major ISPsâ particular implementations.
PLDT PHILIPPINES
Please list the make and model of your modem and router
TP LINK XE75PRO MESH ROUTER
MODEM : GPON FIBERHOME HG6245D
Do you have any additional network hardware, like additional routers or managed switches?
NONE
Does your network have any VPNs, proxy servers, or enterprise-grade security?
NONE
ANTIVIRUS: BITDEFENDER TOTAL SECURITY
What machine are you using as a Roon Core, and how is it connected to the internet?
WIFI CONNECTION
HP ELITE X 1012 G2
i7-7600 2.8GHz
16GB RAM
64 BIT OS
WINDOWS 10 PRO 22H2
As mentioned above, are there any specific error codes displayed in the Roon Settings â Roon ARC tab? If so, can you post the error here?
Do you have an IPv6 pinhole configured in your router to allow ipv6 TCP connections to your Roon Server (at the ipv6 address shown in the Roon ARC settings page) on port 55013?
If so, this will be enough for âReadyâ to be reported on the Roon ARC Settings page that you posted a screen shot to above.
An ipv6 firewall pinhole will be good enough for remote ARC clients to connect using IPv6 - but if the remote is connecting by an IPv4 only service, then the working IPv6 connectivity will not be any good to you.
Incidentally, the IPv6 ip address of your Roon Server that is visible in the screenshot is a public ipv6 address and should probably not be shared online.
If you disable the exception in the IPv6 firewall, you may see some diagnostic text which will give more clues as to what might be going wrong.
However, looking around on the internet, it appears that PLDT PHILIPPINES use CG-NAT. If that is the case you will not be able to get IPv4 connectivity working unless you can get PLDT to give you a public routable (possibly static) ip address.
If you cannot get ARC connectivity working for IPv4 any other way, then you can always try Tailscale. There is a Roon Help Centre article on how to set it up:
You appear to have two subnets; 192.168.68.0/24 and 192.168.1.0/24.
This is indicative of the presence of two routers.
You have two choices:
Elliminate the second router by putting one of the routers into bridge mode or access point mode.
Set up manual port forwarding on both the router for TCP connections on the ARC portâŚon the router that handles the Internet connection you need to forward to the WAN side ip address of the second router. On the second router you need to forward TCP connections on the same port to the ip address of the Roon server.
Once this is done the ipv4 connection should work. And then you can reenable ipv6.
Alternatively you can use the Tailscale solution described above.
this is what happened when i deleted the port forwarding rule i created for roon ARC and turned on UPNP. i still have not switched to access point mode .
It makes perfect sense that the port forwarding options are not available on the Tp-Link router once it has been put into Access Point mode. This mode disables the network address translation (NAT) and DHCP services on the router so that it turns into a switch and media bridge (connecting the Wifi network to the Wired network) and thus there is no NAT layer to forward across.
The good news is that, now you only have one subnet - 192.168.1.0/24.
The fact that the ARC settings page in the ordinary Roon client is now reporting âReadyâ suggests that uPnP on your ISP router has successfully opened port 55002 as used by the Roon Server to support ARC.
I donât know why ARC is not working and is showing the failure to connect to the Roon Server. Have you tried logging off in ARC (âDisconnect from Roonâ at the bottom of the ARC settings page) and then re-connecting? Some people have reported fixing such issues by uninstalling ARC and re-installing.
Once again, if all else fails, you can always use Tailscale to avoid the need to set up port forwarding at all.
Please Note: you have now shared two screen shots that show the IPv6 address of your Roon Server. This is a public ip address so you shouldnât make it know to the public at large. It represents a security risk.
I think that the ânot using UPNPâ part may be important in the two router, two port forwarding rule case.
In principle, if your ISP router is correctly forwarding to the second router (in your case, the ASUS), then enabling UPNP on the second router should be sufficient to establish a connection. However, the Roon server performs a check to see if the public IP address it sees is the WAN side ip address of the router to which the Roon Server is connected when it establishes a port forwarding rule by UPNP. This check will fail when two routers are involved.
I believe that this is probablly why the advice in various posts from Roon Support staff is to disable UPNP and use manual port forwarding on both routers when double port forwarding is used.
Hi @ted_anthony_tobias_k,
Thanks for writing in to let us know about this issue. Iâm sorry to read that you are having problems with using ARC. Did @Wade_Oramâs latest suggestion help you to resolve your issues with ARC?
Your question is by no means invalid or inappropriate, but it better lives in Roon Software Discussion or even Feature Suggestions, where the Product Development team will see and ingest it and other users can raise their voices. Support threads close with a quick cadence after solution.