Can anyone enlighten me?

After the last update my Roon backup stopped working. For the past years, the backup has successfully backed up to my Nas Server \192.168.0.23\ Public\Roon Backup.Now, for some unknown reason the address has changed to \192.168.0.21\Public\Roon Backup ?
Nothing has been moved, added or changed…. It’s all quite bizarre.
Additionally, Roon Arc has also decided the Port address has also changed ??? From 55002 to 55001. ( As it no longer worked on the original port number 55002)
All is working as it should now, but I’m confused to say the least.
Has any other Roon users experienced such bizzare anomalies.

This is not a complaint, I just need a better understanding of how network addresses and port numbers can change.

I only noticed this, as an error displayed that the last backup failed !

Confused :woozy_face::woozy_face::woozy_face:

1 Like

The IP addresses are assigned by the router, so it’s quite normal that they can change. Roon has nothing to do with this.

You can either use the network name of the QNAP instead of its IP address to configure the backup location in Roon, in which case the IP address becomes irrelevant. This works if the router provides a name service for the local network, which most do. You can see the name of a device in the router’s network overview somewhere in the router’s web admin interface.

Alternatively, your router probably allows you to reserve IP addresses for specific devices, making it always assign the same one. In this case, the IP of the QNAP won’t change anymore.

Regarding the ARC port, I don’t know what would prompt Roon to change it.

2 Likes

Thanks for that, i now have a slightly better understanding. Still very confused about the ARC port number change, as it been working perfectly for months now and then suddenly… NO Connection.

1 Like

The only reason the port is changing is because it’s relying on UPNP. Likely something else on your network wanted to use 55002 for some reason. Because UPNP is dynamic and negotiated between your router and the device requesting to use the port, it too is normal to change.

You’re better off setting a static IP address (on the Roon server or in the router - both are fine, but the former latter is preferred) and manually forwarding a port.

3 Likes

Thanks for that, the perfect answer. :+1:

1 Like

Pedant mode on…

Personally, I would say that setting a reserved address in the router is preferable to setting a static address in the Roon Server - less chance of problems in the future if you are not familiar with networking.

5 Likes

Apparently UPNP on my sky router is automatically set to on, by default. I can turn it off, is that what is being suggested to obtain a static address?

As I am only loosely IT savvy, what happens to everything else that is connected to the router. ?
Sorry if its a bit of a naff question.

No. For static IP addresses, there should be a router settings page where you can see all of the various network devices, and then provide a static status, to ensure that the DHCP server doesn’t change it. You can create a list of your devices and assign the IP address, or more common, just use the IP address that is currently assigned by DHCP and fix it as static.

For my Linksys router, it has a DHCP Reservations list page showing each device name, the interface type (wired or wireless), assigned IP address, the devices MAC address and then an open check box which if I click on and then hit save, the device moves from the DHCP section list to the Static section list.

1 Like

Many thanks for that. I’ve found the reserved list (which was, of course empty).
Wright or worng, I’ve added my Roon Server (NUC) and my NAS drive to the reserved list. The rest, for now remain as they were.
All appears to be working for now and hopefully auto assignment can no longer happen. (at least for these two addresses).

1 Like

It will work until you change our router or do a re install of wndows…Windows always knows best… Ha ha

No you’re right - I had my wires crossed when I was writing. I set my statics on the router side, not the device side. Thanks for the correction!

Well, now that you know how to switch devices over to static IP addresses, there isn’t anything stopping you form doing it for other devices too. There should not be a limit on the number of devices (well, probably within reason based on how many devices the router can actually handle, but probably at least 50). I set all of my primary devices to static: computers, laptops, iPads, phones, and a few smart devices. Then when extended family comes and goes, my devices are still in the same state and under control as I expect. Makes IT life at home easier :wink:

1 Like

Ehhh probably don’t do that. For a small handful of devices that you actually need to access via IP, that’s a great solution. But then you rotate out devices one day, you get more in, people come over for a large gathering, etc… and suddenly you are out of IPs that haven’t been reserved or already leased, or you get some weird collision. For those that don’t want to do network maintenance (most people), just let it assign dynamic IPs as the router wants.

If you routinely need to access a device, do it by the DNS name and search domain, rather than the IP. Makes things a lot easier when you can type “ssh user@john-computer.localdomain” than memorizing what IP goes where.

1 Like

I’ve had a similar problem as @Peter_Boyse for over a year. I used to be able to back up with ease from my music server which served as Roon Core - easily discovered and accessible by Finder on my Mac. I used to be able to back up directly to my Mac’s local drive. No more! I can only create backups on the music server, which, of course is no bueno.

I have reached out to Roon support, but with no response. Any help is appreciated.

I don’t know how you reached out but can’t find a support thread by you on the forum. I’d software to create one by clicking here: Support, then click Get Help

It’s here - @noris replied, but @Robert_Furstenberg was not impressed I think…

Thanks, I didn’t scroll back all the way to January

I exhausted all options and possibilities to no avail. In fact, Mark Cole, the COO of Antipodes who is extremely tech savvy and an expert of course navigating Roon was likewise unable to arrive at a solution. We had a remote session and he was quite determined to resolve the issue but after over an hour we both gave up. The issue bubble up after a new Mac OS as I recall.

Robert, as I understand you are trying to use your Mac as a destination or file storage for Roon through SMB/network shares?

Have you tried connecting from a different device to your Mac through IP address and confirm that you are actually able to connect to the Mac file share? Can you send a screenshot of your MacOS Sharing → File Sharing settings?

Yes, I have been able to transfer files without issue from my Mac Studio running 14.5 to my Mac Mini connected to the same local network. I am ONLY able to b


ack up to my Antipodes K41 server as described previously. The COO of Antipodes spent over 2 hours trying to make this happen but finally gave up, and certainly he has VAST experience with Roon. I am attaching multiple screenshots for your benefit dating back to last year as well as a fe amor current ones as recently as today. Thank you! ![Roon Network Share Issue Fall 2023|406x500](upload://1bbWgP3hkFWQ17QKUOvtw5v9h3P.png) ![Roon Netwrok Share Issue 2024|320x500](upload://aMOYjWan5V2HLaAhgI6vWEAKGDe.jpeg) ![Screenshot sub-menu.06.26.24|658x500](upload://dunGyGRdEwBTyrhlQrQquVcYofG.png) ![Sharing Screenshot - Main.06.26.24|339x500](upload://eci8aXkZlulS1bqDG8dKpJ4ILDT.png)