Desktop PC: Microsoft Windows 11 Pro (64-bit), Z690 AORUS PRO, 12th Gen Intel® Core™ i9-12900K, 64 GB RAM
Networking Gear & Setup Details
The NUC is accessed via LAN (Ethernet) → NetGear unmanaged switch → Verizon CR1000A Router. All via ethernet, no WiFi or VPN utilized. NUC is on the same internal network as the Desktop PC and NAS
Connected Audio Devices
Mobile device: Google Pixel 7 Pro for Roon ARC
Schiit Bifrost DAC via USB when played back via Desktop PC
Chromecast for Display - rarely used
Number of Tracks in Library
Was 176,827, now none since I am not able to connect my NAS share.
Description of Issue
After Roon Rock & Roon ARC ran fine for weeks without any problems I recently lost connection to my Synology NAS storage shares and have not been able to add them back. I continually received the message “There was an Unexpected error: Invalid Network Path”. What I did to remedy this was reinstall the OS via the ROCK home screen options, tried again to add a share from the NAS and still I was not able to add NAS shares with the same message. Via the ROCK home screen I reset the database, reposted the ffmpeg file in the Codecs folder and still I can’t add any shares from the NAS. I also rebooted the NUC & NAS a few times in between as well. I have gone through the Synology NAS settings and have found nothing out of the ordinary as both SMB & DHCP are turned on. What am I possibly missing here?
What ever you entered as path for the share does not get accepted as a valid SMB network share (path). I don’t know what component is responsible (a validator in Roon, .NET, system library, …). Without you sharing more details, we simple Roon trying to help, do have a hard time to come up with additional troubleshooting steps. Do you have any special characters in the path name maybe?
Thank you for the help.
I have entered the NAS share name of johnnysp in all possible ways including the internal IP. There are no special characters in the path.
\johnnysp
\johnnysp
\johnnysp\Music Library\Music\Albums
\192.168.1.249
smb://johnnysp/
None of the above nor with variations will work for me at this time.
All the variants that contain the host part only, omitting the share part, are invalid. This leaves us with only: \\johnnysp\Music Library\Music\Albums – \\johnnysp\Music Library without the ignored parts.
Assuming that you actually have a share named Music Library, I would say it contains a special character (a space character) that usually needs to be escaped to work properly. Google finds different variants of escaping spaces in share names – none of witch I’m sure it will work reliably here. I think it would be best if you could just change the share name on your NAS (Music_Library or MusicLibrary) so it no longer contains a space.
I tried Sven’s suggestion resulting in the same failing message.
As for Jack’s suggestion, I tried another share on the NAS with \johnnysp\music as well as other shared folder names that do NOT have spaces or any special characters in the folder names with he same failing result. Keep in mind Jack that \johnnysp\Music Library with the space worked perfectly for weeks. Any other thoughts appreciated, but I am beginning to think this may be on the Synology NAS side.
john
Update: It appears the editor will not allow double backslashes while in this edit. So in all my messages please realize when you see my post with a single backslash it is meant as double forward slash. Thanks.
Failing but really for the same reason (invalid path)?
To be sure while troubleshooting, I would always use URL notation (smb://host/share) and IP-Address instead of host name. Check on the NAS if SMB v2 connections are allowed. Share your related NAS settings if you like, check the DSM manual if unsure and take a look at Roon’s NAS setup guide also.
If only you had a time machine. Would make things so much easier.
Escape correctly using 3 backslashes (type \\\ to get \\) or format the string as preformatted text (symbol </>).
Yes Jack, still invalid path what ever path I try. Yet no problem reaching it from my PC. Also no problem playing music if I use DSAudio app from the road.
Included here is a screenshot of my Synology SMB settings.
What do you think if I start all over and re-format and reinstall Roon on the NUC? It found the NAS shares the first time automatically and maybe that needs to happen again via the install process. Thoughts?
Could be the NAS, could be the network, could be firewall… Unless I missed it, maybe the old reboot of the router, switch and NAS is a good place to start?
Also, I’m wondering if your NAS has a fixed IP or if it’s purely DHCP from the router?
Other than that, and before doing anything drastic, I would start by systematically verifying every variable:
Verify the IP address of the NAS, preferably from the router’s list of connected devices
Seen if you can ping the NAS from the ROCK, to establish that basic network connectivity is there. I’m not familiar with ROCK, but I am assuming that there is some way to do this (e.g. through ssh)
Validate the shares on the NAS. So the individual folder shares (Control Panel > Shared Folders).
Try to setup a share on the Windows PC to see if you can reach that from the ROCK.
Good things to try Sven, and I will, but first I want to figure out how to ping the NAS from the NUC Rock also per your suggestion. I have the NUC set up now with a monitor mouse & keyboard with ethernet to the router, but the usual Ping command does not work from the NUC’s OS. How can I ping from the NUC? What is the command? I am not too familiar with SSH and I have it turned off on the NAS.
Thanks!
Not sure what purpose this should serve. Is there a substantial suspicion that the ROCK OS installation is damaged?
Note: Roon isn’t handling network connection/share mounts by itself, this is all being delegated to the underlying OS and it’s components.
If the reason for the sudden change in your system is in fact a change in Roon, introduced in one of the latest updates, then a reinstall will not cure it (no new bug free version available) – but I miss all the other NAS users here complaining about the same loss of access. If it were a DSM update by Synology, i’d miss all the other Synology users here. Maybe rebooting all your devices (router, switche[s], access point[s] and computers is indeed a good next step?
Maybe try to find out when the changed behavior happend? Does it correlate with a Roon update, a DSM update, a configuration change on NAS, router, etc. or a network topology change perhaps? Also @s73nm made some good points.
