My Roon Core [virtual host] can't configure ARC

Roon Core Machine

Windows 10 Pro 22H2
Intel(R) Core™ i7-7700K CPU @ 4.20GHz 4.20 GHz
16.0 GB (15.9 GB usable)

Networking Gear & Setup Details

Huawei Fibre Optic Modem Model: Huawei Echolife hg8240h
I checked with my Internet Service Provider and they told me that the Modem is in bridged mode and therefore there should be not NAT-PMP issue on their side . I am not sure on this given the below ROON ARC error message,.

LAN / WiFi Router connected to Huawei modem: D-Link Dir-868L

UPnP enabled on the Router:

Port Forward setting on the Router (192.168.0.102 is the IP address of my PC with the Roon Core installed on it):

Connected Audio Devices

Not relevant for enabling ARC?

Number of Tracks in Library

Not relevant for enabling ARC?

Description of Issue

My Windows Firewall settings (I have uninstalled Avira, no other protection is on as per my knowledge):

Roon Core error message when trying to setup ROON ARC in the ROON Core:

{
“connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“161.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“10.32.173.57”},
“status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.0.1”,“found_upnp”:true}
}

So upnp seems to be fine but it shows a problem with natpmp?

I was reading through the proposed solutions but can’t figure out which one might work.

Appreciate help and support.

Welcome to the Roon community, @Friedrich_Brida.

The diagnostics you’ve provided suggest that UPnP is not properly configured on your router. However, I note that you are using a virtual machine for your Roon core. Therefore, since this isn’t a supported configuration, and is the possible cause of the problem–depending on the virtual network interface used–I am moving your post to #tinkering.

Nonetheless, you may want to try the following steps:

  • Try to enable UPnP/NAT PMP in the web administration interface for the router directly upstream from your Core
  • Try to open the port manually in your router’s port forwarding configuration
  • Make sure the IP/Port matches the Port listed in Roon > Settings > ARC
  • Check for any VPNs or Firewalls that might be interfering
  • Check if your modem is in Bridge mode

If you continue to experience difficulties, please include the following information, and community members, such as myself, will attempt to assist.

  1. What is the make and model of your modem and router?
  2. Do you have any additional network hardware, like additional routers or managed switches?
  3. Who is your internet service provider, and what is your geographic region?
  4. Is your Modem configured in Bridge Mode so that it operates only as a modem, or do you have the ports forwarded on both devices?

Dear Robert, thank you for your feedback. I am not clear why you conclude that I am using a virtual machine for Roon? It is intalled as a Core with the Windows downloaded version on my Windows PC running Windows 10.
Can you please enlighten me on your conclusion.

@Friedrich_Brida, your second screenshot identifies your core as “Roon virt. serv”.

I don’t use ARC, but fwiw that may be just a D-Link thing. If you look at the description in the header on that page of the router config, D-Link is describing a port forwarding function as “Virtual Server”. These router companies sometimes have odd ways of describing functionality.

My own router shows it’s firewall setting as “NAT only” which gave me a start. It’s not just NATing.

1 Like

@Friedrich_Brida, I’ve moved the thread to #support:port-forwarding-help. Please take a look at my first post for your next steps.

Dear Martin, thank you for highlighting the virtual server situation. Actually as you can see in the second screenshot the box is not ticked, so it was not running as a virtual machine. Nonetheless for this reason, I decided to reset my D-Link router and to uninstall my Roon Core and start completely new to ensure that I have no tinkering done on my side and run everything with a clean new Roon setup.

As a result the “NATPMP” issue persisted. So I again went back to my ISP to reconfirm whether their optic fiber modem is in bridge mode which they reconfirmed and stated that there should be no NAT issue on their side. I then insisted that I don’t think the issue is on my WiFi router side. So we together went through the whole setting and they took the time to read this post since my Roon error message was exactly the one mentioned there:

They then decided to recheck again on their side and get back to me. After a few hours they called me and asked me to check again and voi la it worked.

They clarified and admitted that the issue was on their side and despite their modem being in bridged mode connected to my router via PPPoE connection they had to do some settings on their side to get it fixed. They didn’t explain exactly what they did but at least now the case is closed and Roon ARC works perfectly fine.

Thanks again for your help and this topic can be closed.

3 Likes

Hi @Friedrich_Brida,

Welcome to the Roon community. When i look at the error message, there is a multiple layer of NAT (see bold text in error message below).

You wrote in your post that your ISP told you that the Huawei is in bridge mode. Did you checked this by yourself? I would suggest that you login in the Huawei and check if it’s really in bridge mode.

Maybe this link will help you.
https://forum.huawei.com/enterprise/en/huawei-ont-bridge-mode-introduction/thread/498679-100181

Regards,

Maarten.

Hi Maarten, thanks for your help. As mentioned in my last reply, after discussing intensively with my ISP they did some work at their end (am not clear what they did, they just told me on the phone that they changed something on their side) and with this the issue is resolved.

Nonetheless I will for future potential issues personally check whether the Huawei modem is actually in bridge mode.

2 Likes

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.