Roon ROCK cannot connect to my NAS

What is going on here?

Roon Core Machine

ROCK on Iintel NUC core i7 8th gen with 256GB SSD

Networking Gear & Setup Details

DLink DNS 323 NAS w/ two mirrored 2TB drives
Actiontec T3200M Wif-Fi Modem (telus)
SMB1 enabled in Windows

Connected Audio Devices

SMSL M400 connected to ROCK via USB
iFi Zen DAC connected to Windows 10 workstation
Chromecast Audio on WiFi
Riopee Pifi streamer over Wifi

Number of Tracks in Library - 45,000

Description of Issue

Hi, everything was working fine a couple of weeks ago, and now Roon cannot connect to my NAS. I can connect to the NAS perfectly from the desktop. When checking the NAS, i found one of the drives had failed, and it was replaced. I’ve tried entering the path as and SMB share, with the IP Address, and as shown below:

The NAS is a little long in the tooth, would and upgrade to something like a Synology make any difference?

Nobody knows. Could you please fill out the remaining questions in the posting template? It will help other members and the support to help you faster. And welcome to the community!

Networking Gear & Setup Details

Your network gear (model of routers/switches), if on WiFi/Ethernet, and if you are using a VPN

Connected Audio Devices

Specify what devices you’re using and their connection types, like USB/HDMI/Chromecast, etc.

Number of Tracks in Library

Tell us how large your music library is, eg. “30,000 tracks”

Description of Issue

Tell us about the problem you’re having in as much detail as possible. Screenshots are always appreciated!

1 Like

\ Networking Gear & Setup Details

Actiontec T3200M Wifi Modem (Telus)
DLink DNS-323 NAS with two mirrored 2TB drives

Connected Audio Devices

SMSL M400 DAC usb to Roon Rock
iFi Zen Dac connected to Win 10 Desktop
Riopee Pifi stream via Wifi
Chromcast Audio - wifi

Number of Tracks in Library

45,000

Description of Issue

NAS was connected up until a couple of weeks ago.One of the drives had failed and was replaced.
Have tried to reconnect network share via network path, SMB path, IP address. All five “invalid network path” error. NAS is visible on the network on my Win 10 destop without any issues. SMB1 is enalbled.
ROON is running 2.0 with all of the latest updates.

No idea why things stopped working!

grafik
Click on the picture to open the guide.

Note: In general, please make sure that your NAS/share works correctly with other machines before attempting to use it with Roon. Follow the guide to trouble shoot errors – and don’t forget to:

Make sure to include screenshots of what you’re entering into Roon, screenshots of the share settings, and a detailed description of your networking setup.

OK, seems there’s an issue with ROCK seeing any shares. I copied my files to my desktop and shared the folder, but that doesn’t work either.

Surely you’d need a username at least for the desktop share.

I shared it with “everyone”, so would that really be necessary?

“Everyone” is everyone known to the computer (by [user]name and authenticated by password).

Might as well try that, but the share on the NAS worked without a username - until it didn’t. My theory is that one of the latest ROON software updates is the cause.

hmm… I just learned that the DLINK dns 323 does not support SMB 2.x
Is this important?

Hi @Craig_Thompson ,

Have you make any progress on this issue since your post? Have you tried IP Address method connection? I would try adding the username & password to see if that changes the behavior.

Hi Noris,

I did try connecting the NAS with the IP method, and with a username and password. The NUC is still not seeing the NAS.I have made some progress, though. As a workaround I’ve copied my files to a portable drive, connected to the USB input of the NUC.
I still haven’t figured out what stopped working, and now that I have my local files back, not terribly interested in becoming a network engineer to figure this out. There are too many variables with ROON, Windows, an old NAS, Bitdefender, etc. etc.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.