Ethernet connection (Synology RT660ax) to Nucleus, SMB
Connected Audio Devices
N/A
Number of Tracks in Library
8,438 tracks
Roon 2.0 build 1359
Description of Issue
Sometimes - but not always (20% of the time) - two instances of my new Nucleus’s ‘Internal Storage’ Volume appear in the Finder. As can be seen from this grab, the command line distinguishes between them.
They are functionally identical as far as I can see.
Always use ⌘k to “connect to server”, and enter smb://ip_address. Connect as Guest. Otherwise, don’t worry about it; I think the problem is with macOS, but this way I’ve near had an issue.
Mark so you have a saved shortcut saved on the desktop or side bar something like smb://nucleus can be different to connecting to //nucleus which I think these days defaults to cifs
I had a designer I had worked with who had saved hundreds of shortcuts in the side bar and all with different server names etc and it caused chaos
Your patience and persistence here appreciated, Michael… I tend to retain what I understand - when I do eventually get it !
I understand the principles of DHCP in terms of WAN.
My router is a Synology RT660ax, which I have had for a couple of months and seems to be working faultlessly.
So I fear I have to ask what would or could make the Nucleus’s (or is it my iMac’s) IP address ever change; rather than answering, “I don’t think so”, or asking where I could look in Ventura’s logs to see if it has and then make an assumption.
I can see why. And - despite what I have just said ( ) - the fact that I get the duplication perhaps once a week, doesn’t that suggest it is doing?
Am I correct in thinking that if I thus both gave Roon, say, 192.168.0.221 and my share sequence (Cmnd+K) also ‘192.168.0.221’, I’d be able at least try for a week and see if I got duplicates?
The router‘s DHCP may occasionally assign a new IP to the Nucleus. How often it depends on the time-to-live setting for DHCP in the router. You could try reserving an IP address for the Nucleus in the DHCP settings, this way it won’t change.
No, leave the Nucleus on using DHCP, else there will just be more havoc.
The Nucleus is the DHCP client here, it just asks the router‘s DHCP server to provide an IP (and other stuff like what the DNS is).
The DHCP server and what it does is configured on the router. I.e., configure it to reserve an IP for the Nucleus, so that it always hands out the same one
I see that from your posts and the level of detail involved in getting to the end result.
I do DHCP on Synology myself and it works nicely. You can set up the current IP as a reservation or reserve another one. Though I think option one should be the easiest way for you.
@Mark_Sealey I can’t find a manual for the router online (sigh) but this forum thread (though a bit old and a different model) may still explain correctly where to find the reservation option:
‘Reservation’ is new to me. Is it really as simple as keeping DHCP (as you say here) and effectively setting a parameter in the Synology’s dashboard (aka SRM) so that it assigns a fixed IP address to - in my case - the Nucleus?
That way - if I understand you correctly - I keep DHCP to avoid any ‘havoc’ ( ) at all.
Then, if the router ‘decides’ or needs to reserve a new one (refreshes the lease?), it will avoid doing so to my Nucleus; and hence I can mount it from my iMac in the way Michael suggested here?
Is it really that simple? And if I make a mistake, can’t I simply revert to the way IO have it set up now - because I will have recorded all current settings?
And I don’t need to change anything at all in the Nucleus web interface? It will pick up its IP address, Netmask, Gateway and DNS server from the (newly configured) Synology?
) of the InternalStorage Volume.
) - the fact that I get the duplication perhaps once a week, doesn’t that suggest it is doing?