Michael,
OK, so sticking with the first option, this is what I see in the SRM’s Network Center > Local Network >
Like this:
?
Maybe. They should just publish a damn complete manual. I tried searching their knowledge base and it’s woeful.
I suppose so. It’s just about telling the DHCP server to always assign the same IP to a given device (the Nucleus in this case)
I’m sure you can turn off the reservation any time. But a reservation can’t make anything worse.
Yes, nothing to change on the Nucleus, it simply keeps using DHCP as always. The only difference is that when it uses DHCP to ask the router for an IP, the router always sends the same one to use. The Nucleus doesn’t even have any knowledge about this IP being the same every time, nor does it keep a record of previous IPs. The only thing it knows is „my IP is aaa.bbb.ccc.ddd“, and that’s all it needs to know about that.
Right, this is exactly what I couldn’t find. Thanks. The relevant part is:
You don’t necessarily have to pick a specific address to assign. Any IP the router proposes should be fine. The whole exercise is just so that it always uses the same one, whatever it is.
Mario,
Agreed. It’s not the easiest site (or system) to use 
.
Which I think I have done, by having just made this change:
Haven’t I?
So now I can amend my share to:
smb://192.168.0.221
and I’m all set?
… always my fear
I see. Thanks!
1 Like
As the router knows the hostname of the Nucleus, i.e., “nucleus” (capitalization does not matter),
and we know that it provides a local DNS on the LAN (green highlight):
you don’t actually have to bother with IP addresses at all. You can simply use
smb://nucleus
and the router will translate hostname to IP for all devices on the network if they ask for “nucleus”. That’s the whole point of DNS
E.g., on mine:
Sorry I have been away from the phone for a while.
Mario as always has given good advice.
Once you are using a reserved IP address there’s no need to use the IP address in finder as it will not change.
1 Like
To be precise, if the router provides a DNS on the LAN (which most routers do but some crappy ones don’t), there is never a need to use the IP address in the first place, such as in the Finder.
By using the “nucleus” hostname, the Finder will simply send a DNS request to the router to ask for “nucleus” and the router’s DNS will respond with “use this IP: aaa.bbb.ccc.ddd”, which is whatever IP the router has currently assigned to the Nucleus.
However, the Mac has a DNS cache, so that it does not have to ask for the IP every time, and it is possible that the cache gets stale and contains the wrong IP if it changes often. In this case, the Finder might try the wrong IP. Normally, with healthy devices and network this should fix itself automatically without any ill effects.
But it’s possible that something is going wrong, so in @Mark_Sealey’s situation with the weird double mount on the Mac it is good to rule out this possibility by using the fixed IP assignment as discussed.
Please don’t apologize, Michael!
As always indeed!
Because it looks (at least to me) as though my screenshots suggest that I’ve done things correctly, I’ll go back to:
smb://NUCLEUS
Yes?
2 Likes
/10chars
Fully agree and that is why I prefer the term reserved IP address rather than static IP address
Even though I suggested the idea of the issue potentially being a changed IP address, I am not convinced that is actually the problem.
But importantly it does takes another potential problem away.
1 Like
I changed it back to smb://Nucleus, Mario - after seeing this on the last time (immediately after making the changes suggested) I restarted:
So then I took the Volume out of Settings > General > Login Items, where ‘Open at Login’ and of course it doesn’t appear at all, though Roon is quite happy.
Of course Cmnd+K works to get the Nucleus back and visible, although now it appears as ‘Data’, which won’t help when I add new Albums.
Sorry this has got so confusing. Not sure what to do now …
Michael,
Understood.
No, I can believe that because of what I saw here after making the changes I did.
So if you disconnect both and reboot and reconnect the server.
What happens then after you reconnect?
Mario,
Right; thanks. And I really do think I did it correctly. After two restarts, this is what I see there:
But now I haven’t got a folder hierarchy on the Nucleus (in)to which I can drag-and-drop Albums.
I’m sure that’s something simple?
I’m also not convinced that this is causing the problem, but the path to figuring out mysterious issues is to systematically rule out every remote possibility until only the real cause remains So I fully agree with your approach here.
I just thought it makes sense (for any future readers happening upon this) to clarify the purpose of DNS because there’s too much confusion already in this thread.
(And generally, people are dicking around with IP addresses way too much, creating problems on the way that aren’t necessary, although DNS was put into service in 1985 (and RARP in 1984, followed by DHCP in 1993) precisely to avoid the confusion caused by dicking around with IP addresses. )
Michael,
You mean physically detach the Nucleus after Roon > Settings > General > Roon Server; then reboot; then reconnect?
Just want to be sure before I make things worse…
I also appreciate it’s late where you are .
Your Mac seems to be mounting the folder twice for some reason, as I already suspected a long time ago
I don’t understand this. As per this screenshot,
what happens if you enter one of the two InternalStorage folders?
Mario,
Understood.
Here’s something:
I seem to be able to get to the directory in Nucleus which I’m used to in the Finder from both the ‘Nucleus’ Volume itself and ‘Nucleus > Data’. Both in the sidebar’s ‘Locations’.
Is it safe to then navigate to the Nucleus’s (Linux, RoonOS) ‘Storage > InternalStorage’, where I can see the Watched Folder?
I suppose I’m effectively asking whether ‘InternalStorage’ in the Finder is some sort of symlink created by RoonOS?
If that were the case, the Reserved IP you have both kindly talked me though may indeed have fixed the duplication.
But am I risking anything by navigating to ‘InternalStorage’ that way?
I can do the same at the command line, and Roon seems quite happy at each boot etc.
No sorry I meant clicking on the disconnect button shown in your finder screen shot, rebooting and then connecting again.