Not sure when it happened but the shares setup several months ago aren’t able to access them. There are 3 shares. smb://192.168.1.2 /Roon Folder 1. Something has changed the IP from 192.168.1.2 to 92.168.1.8. Are there any Roon or Apple docs? Maybe setup a static IP on the Mac? I hesitate to make any unnessary changes since the only issue is Roon accessing the shares. My ROCK has the 8Tb SSD on it. Or I could add an expansion to the Mac Mini itself
Probably simply your router’s DHCP. The DHCP is free to assign different IPs from its configured IP range to connected machines. Depending on the router and its DHCP configuration, they can change more or less often.
It’s easier and less error prone to configure your router to always assign the same IP to a specific device. Nearly all routers can do this. Then it won’t change. Read your router’s manual to find out how to do this.
Alternatively, don’t use the IP to access the share in the smb:// path, but use the device’s network name:
Most routers maintain a DNS name service on the LAN, meaning that they translate the machine’s name to whatever IP they may have assigned to it by DHCP at any given time. Then the IPs don’t matter at all, even if they do change.
Your router’s admin interface will normally show you a list of the machines on the network with their names and current IP. Just use the name from there in the smb:// path.
You can also find a Mac‘s name like this:
1 Like
smb://RandalliniM4Pro/Roon Folder 1 shows as being shared as is /Qobuz
And does it work?
Where’s the RandalliniM4Pro taken from, the Mac or the router’s admin page?
Router admin page
Looks ok to me, so far. What’s the error that you get then?
Anyway, you could also still go the other way and tell your router to always use the same IP for the Mac, then keep using this IP. In many routers this is called “IP address reservation” or some such.
Hm ok weird, if the router knows this name and then can’t find it.
I’d still prefer an IP address reservation on the router simply because then you can’t get into trouble later if anything changes in the network configuration.
But setting a static IP on the Mac will also work. Although then you still have to configure on the router to exclude the Mac’s static IP from DHCP assignment (else it might give the same IP to another device and then nothing will work due to IP address conflict). Or use a static IP that is outside of the range that the router uses for DHCP assignments. (The range should be configurable on the router)
1 Like
Exactly
(10chars)
I have never had a problem with using a Mac for a Roon server. I setup a static ip address on the Mac. I even shared the storage on the Mac when using Roon on a Linux server with no issues. The Linux server didn’t have any storage on it, I just made a link to the storage on the Mac that I used to use for Roon.
Whilst this works fine, I, like @Suedkiez, still prefer to use a DHCP address reservation on my router rather than a statically configured ip address on the Roon Server device.
The advantages are, IMHO, two fold:
-
All the changes are on the same device - the router. If you set a static ip address on your Roon Server device, then you also have to check your router settings to make sure that the ip address that you set is not included within the pool of addresses allocated by the router’s DHCP server. If this is not done, then the same ip address may be allocated by DHCP to another device and that would lead to lots of problems. Further, since this may not happen straight away, you could have the situation that a system that works for weeks, months or even years, suddenly stops working because you added a new device to your network or powered a device off for a period longer than the DHCP lease time set on the router (typically a day) before powering it back on.
-
Fewer problems with network configuration in the future. With a static ip address, any change to the configuration of your network such that a different subnet is being used (e.g. say 192.168.1.0/24 instead of 192.168.0.0/24) for whatever reason (including changing ISP and getting a new router with a different default subnet), will render your Roon Server device unreachable. Fixing this can be awkward if the Roon Server device is headless (no keyboard or screen). By contrast, with a DHCP reservation, such a change will not cause any problems since the Roon Server device will just get a new ip address in the new subnet via DHCP - although you may want to set a appropriate new DHCP reservation in your router.
1 Like
I realize that the error being shown might not be consistent with what I am about to say, but the username should not be your full name; it can’t have spaces.