Unable to Access Synology NAS Network Shares on Roon (ref#CKXL41)

Support
1

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

I have lost access to my Network Share folders on my Synology NAS. I am not sure how it happened, but found it that way a few days ago. My last Roon backup to my Synology NAS was Dec 24.

At this point, under Storage -> +Add network share, I am not able to add a network share and my folders show as "This drive is not available. Check the drive or edit this folder if it's been moved."

When I enter smb://192.168.1.249 it fails to connect with the message "There was an Unexpected error: Invalid Network Path". I am able to access my NAS files via my desktop's Windows 11 File Explorer with no problem.

My Roon backup also resides on the NAS Share folder so I am unable to Find backups to restore.

This has been running fine for many months with no issue of this sort.

Describe your network setup

-Intel NUC13ANKi5 running Roon Rock, SABRENT 1TB Rocket Q4 NVMe PCIe 4.0 M.2 2280 SSD, 2x Crucial RAM 16GB DDR4 3200MHz CL22

-Desktop PC: Microsoft Windows 11 Pro (64-bit), Z690 AORUS PRO, 12th Gen Intel® Core™ i9-12900K, 64 GB RAM

-NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS116NA).

-Synology DS2419+ NAS

2

What version of DSM are you running? What are your SMB settings on your NAS? Including the Advanced SMB settings…

1 Like
3

DSM version: DSM 7.2.2-72806 Update 2

4

Thanks. The community will need the other information, too, in order to help.

1 Like
5

I use a Synology NAS as my Roon backup location, and I have had a few backup failures where Roon seems to lose the connection to the NAS share.

The fix I have been using is to remove the network share and re-add it again. This has always worked.

So, it might be worth trying the same thing.

Nick

6

Thanks Nick, but I’m not able to load a network share. The Roon backup is on my network share so I’m stuck.

7

For the network share location I assume \johnnysp is the Synology‘s DNS name? If so then the name of the actual share seems missing. Something like \johnnysp\share

Edit: the second leading \ is killed here in the forum for some reason?

8

Thank you for your assistance. johnnysp is the name of the Host NAS. I have tried a variety of paths to access the Network share including: smb://192.168.1.249
smb://192.168.1.249/
smb://192.168.1.249/Music Library
smb://192.168.1.249/Music Library/
The following is entered as preceding with two double back slashes (not one as displayed here)
\johnnysp
\joihnnysp
\johnnysp\Music Library
\johnnysp\Music Library\

9

Just double check MacOS security settings. Settings > Privacy & Security > Local Network and disable and enable ROON.

Also, on the NAS. Can you access it with the above IP and login with the correct username/password? Does MacOS see it in Network?

10

Avoid blanks (space) in the share‘s name at all costs. There often is trouble. Do - or _ if needed

11

The forum uses the single backslash \ as an escape character. Therefore, you need to type three to see two \\ of them

1 Like
12

I run Windows 11 on my Desktop and can access the NAS from my local network without issue via File Explorer or mapping.

13

OK, but that is the way I’ve had it for a few years, with a space as Music Library. Of course that is not the problem, but thank you as that is good general guidance.

14

Sorry, my fault for not reading it was Windows!

15

Gotcha. I knew that, but I had forgotten that workaround. Thank you.

1 Like
16

Hi @John_Spaventa,

What are the Advanced SMB settings? Diagnostics we’ve pulled from the affected RoonServer instance indicate that the mount is failing due to outdated security. This sometimes results from the NAS defaulting to SMB 1.0.

18

My apologies to everyone who has tried to help. The problem was I was using an incorrect password. So happy we have the solution and I confess I am so red-faced and embarrassed. Please close this ticket.
Happy New Year to all.
Johnny

2 Likes
19

Happens to all of us. Happy New Year!

20

Easily done! Happy new a year!

21

Connor,
Before we close the ticket I wanted to add that the reason you saw SMB1 from the NAS was due to Norton 360.

Thanks again,
John