Roon Remote on 192.168.1. does not find the Core on 192.168.33

Roon Core Machine

NUCLEUS+ at my home with IP 192.168.33.200, Serial 54B203F6880D
pingable from my Office PC IP 192.168.1.xxx.
33 is at Home, .1 is in my office (theres a VPN)
PC in the Office is a Windows 10 from DELL
From work I can access the Nuclueus Website, from where I can reboot or shutdown

Networking Gear & Setup Details

At Home a Fritz Box Cable 6660 and a Sophos XG 106, and Ubiquiti Switch USW-PRO-48 POE
At Work a Vodafone Plus Box and a Sophos XG 125, and Netgear GS116E

Nucleus at home is connected directly to the switch
Roon Remote is running perfect on several devices at home
Speaker and/or Streaming Amps in several levels of the house
Roon ARC when travellin is also working

Connected Audio Devices

1x M10V2 with speakers
1x Elac Discovery Z3 and others

Number of Tracks in Library

6500 tracks

Description of Issue

Everything works fine from home.
Even Roon ARC, through the Sophos firewall at home.

So Yesterday, I set installed Roon Remote on my PC in the office (other place) too. We have a VPN running. It worked at once, I only had to give Roon Remote the IP 192.168.33.200.

Then, the first task was to go into settings to update my preferences. The change to the dark mode required a reboot of Roon Remote, and from there, it did not find the Core again. That was 10 minutes after first log-in.

I still can ping the Core, I can Reboot and or Shutdown it via website, but it does not want to connect.

All following screenshot are taken from the PC in my office.

Kind regards
Manuel

Welcome to the forum. Unfortunately for you, Roon doesn’t support running via a VPN. I guess for precisely the sort of reasons you are experiencing.
It is only supported on a contiguous IP range.

This thread may get moved to the tinkering section where the tinkerers may be able to help you.

Roon officially supports core and remotes on the same network and subnet.

Therefore, I’ve moved this thread to #tinkering since other users may have successfully setup what you are attempting.

1 Like

I didn’t realize you could do this. Can’t you just do that again?

There are two kinds of VPNs. One is the kind you run at home, so that you can connect to your home from outside networks. The other is the kind you run at work, so that employees can log in from home. Sure, they are the same thing, but it makes a difference when you say, “theres a VPN”, as to which of the two you’re referring to? Typically a VPN creates another subnet, with a distinct IP address header. If neither the core nor the remote are on that subnet, it has to route packets to (and from) the subnets they are on. Is the VPN set up to do that?

Hey Bill,

it’s when you press Help (in screenshot 3, then you get a window like screenshot 4 hwrw you can specify an IP-address…) However after the first restart of Roon Remote, even that did not help … it just stayed searching, but i can still access the core via windows explorer…

My VPN is a peer to peer between two Sophos Boxes (IPSEC)
It’s just for me, the owner of the business and for an additional server backup.
We did choose indeed 192.168.1 at work and 192.168.33 here at home when setting up…

So routing and relay should be automatic. Is multicast enabled for the VPN?

Hi Bill,

now it works, and i am not sure why…

The only thing I did was this:
Because some devices at home showed me two Cores to choose from, even though I had deleted all settings of the first core which was on my home PC firstly, before i purchased a NUCLEUS, I decided to delete the roon App completely from that PC and reinstall it as a Roon Remote. That worked, and now shows only one Core. Not sure if I had to, but I also renamed the RAAT Folder to BAK_RAAT… on that formerly Core-PC.

So, today I tried it angain from work, and it connected to NUCLEUS instantly!
This time I even did not had to specify the NUCLEUS IP that is a different subnet!

Firstly I had no speakers available on the PC at work, but after installing ROON-Bridge they showed up in Settings - AUDIO

Happy now!

1 Like

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