Core Machine (Operating system/System info/Roon build number)
MacOS Big Sur 11.1/latest download of Roon at 28 Jan 21.
Network Details
Testra router to which NAS is connected by ethernet and MacBook also connected by ethernet.
**Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)**Macbook Pro/Gustard DAC/Arcam amp
Description Of Issue
I can’t connect Roon on my Macbook Pro to a network share on my Synology DS218+ NAS. 2 screenshots attached of Roon details and NAS configuration. I must add that Audirvana has no diffculty finding my music files.
See screenshot–won’t connect. I have used the NAS name, IP address, with and without username + pwd, but zilch.
This is going to be a slightly vague direction I’m going to tell you to investigate: I seem to remember having similar issues with SMB and it turned out to be a mismatch of SMB implementations on my Synology NAS vs the client’s needs that I was trying to connect from. Try to alter the SMB config on the NAS to allow it to run a maximum version of a later iteration than its default - put it at SMB3 rather than the SMB1 default, leave the minimum at its default. You’ll find this in the Synology control panel>File Services>SMB/AFP/NFS then click on “Advanced Settings”. It’s under there. Worked for me - hope it gives you some success.
As you have a synology, you might want to investigate the Roon Core implementation for Synology NAS devices. I’ve been using it for a year and it means I don’t need a laptop/workstation/NUC or similar to always be running to provide the Core as the NAS is handling it and is the always-on device on my network. Speed is acceptable, but greatly improved if you add a SSD to the NAS and install the Roon Core onto that instead of any mechanical drive in the array(s).
Excellent, enjoy the music! One reason for this particular confusion is that local machine name discovery does not always work as expected across operating systems. I was never able to use the local name for my Synology NAS on different local devices reliably until I spun up a local mDNS server on my Ubiquiti router. But I don’t recommend becoming one’s own sysadmin unless you’ve been in the business for a while
So @John_Flood then corrected the network share location to point to music instead of volume1 (read his first screenshot) or else if it works now he is connected now to the share volume1? Sounds strange as volume1 shouldn’t be a specific folder one could share or so I sought.
