Hi Noris,
The router is a Verizon Fios Quantum and I’m using a Verizon Fios Network extender and Motorola MM1000 moca adapter. Both of these are connected to the Quantum router via the same coax cable run and are on the same network.
The NAS and Roon Rock are using 2 different switches. Both are connected to the switches via ethernet cables. The NAS switch is connected directly to the Fios Network extender and the Roon Rock switch is connected directly to the moca adapter.
I am able to access the NAS shares via Hostname from computers, both Windows 10 & Ubuntu 18.04, connected to both switches and via WiFi. I can also use J River MC25 to play music with no problem and it’s library access the NAS using Hostname rather than IP address.
I am also seeing frequent problems with the ROCK losing connection to the Windows 10 pc on the same switch as the NAS. The Windows 10 pc is also connected via ethernet. I’m working on rebuilding the Roon database for my music and as a result have not been doing much listening to the system connected to the same switch as the ROCK, so I don’t know if there are instability issues there as well.
Prior to the most recent Roon update my system worked flawlessly. To say I am disappointed with Roon at the moment is an understatement.
1 - Router: UniFi Security Gateway
2 - NAS and ROCK are direct Ethernet to the same switch
3 - Yes, the rest of the network can see the NAS folders with //diskstation/
Thank you for providing that information. I have gone ahead and activated diagnostics mode for your accounts and what this action will do is automatically upload a log set to our servers for analysis.
I have submitted these to QA for review and when I have any new information to share I will be sure to update you here. If connecting via IP address is working as expected, I would suggest to use this method for the time being.
In a separate thread Noris was helping me get my files back into Roon with my original edits. Something Noris said clicked and I tried something that worked. You will have to relink your NAS to Roon using the IP address but before you import the files by adding a folder remove the old folder/file location from Roon storage. For example, belore adding the folder CD’s using the IP address of your NAS remove the hostname version of the folder \MusicNAS\music > CD’s. It’s worked for me to get all of my metadata edits back. As a caution make sure you do a backup before trying this.
I appreciate your patience while QA has been reviewing the diagnostics from your Cores.
@Mario_Bucco/@Daniel_Blount/@Phil_Jeremiah - We have reviewed the diagnostics and it appears that the behavior of the NAS failing to connect via Hostname occurred before your ROCKs have been updated to the latest OS, so it is possibly not related and a red-herring.
@Mohammed_Samji - We have diagnostics mode activated but your Core seems to have not delivered any log set so we cannot confirm if this is the same surrounding factor.
In either case, QA would like to perform a test here to gather some other useful information. Can I please ask you all to try to add the share via a .local hostname and let me know if this works?
Please keep in mind that this would only be a test to hopefully gather some more information surrounding this issue, and this is not suggested to be a permanent workaround if it works.
From what I have gathered in the case notes it would be as follows:
Also “We have reviewed the diagnostics and it appears that the behavior of the NAS failing to connect via Hostname occurred before your ROCKs have been updated”; I’ve had a few weekends away recently and usually switch of the NAS drives but not always the ROCK. It could be that the fail to connect that you see in the log files are while I’ve had the NAS drives switched off.
Hi Noris,
I just tried and it works. I haven’t added any specific music folder but \MusicNas.local\music does show as a valid network share and all the subfolders show up.
Regards,
Mario
Thank you for confirming that the .local address works as expected. I have reached out to QA regarding this update and they have suggested that we take a look at a few surrounding factors to see if we can get the original hostname to work again:
We have done some research and this issue may occur when NTP time servers are out of sync. Can you please verify the following aspect?
Navigate to “DSM> Control Panel> Regional Options> NTP Service” then enable NTP. Then in the same window go to the “Time” tab and set the server address to your domain controller (DO NOT use any of the pull-down options!!!) click Apply then click “Update Now” to synchronize with the NTP server.
There is an option to clear SMB cache under ‘File Services > SMB/AFP/NFS > SMB > Advanced Settings > Clear SMB cache’. Can you please give this a try and let me know if you are able to connect via regular hostmane after clearing this cache? Note: Do not use the .local share name but rather the original one after performing this cache clear.
After both of the above tests, can you reboot your NAS and verify if rebooting the NAS triggers any change in behavior?
Hi Noris,
I’m not sure what you mean by “set the server address to your domain controller”. To be honest I don’t know what the domain controller is.
Since I use this NAS with things other than Roon and everything other than Roon works fine with using the hostname, I’m reluctant to make changes that could adversely affect that. At this point I’ve restored my library using the IP address and Roon is working fine now.
Hi Noris,
Ok, now that I know what the domain controller is I tried it following your earlier directions. In the NAS when in TIME when setting the server address to my router’s address I received a message from the NAS that there was an error. I went ahead and followed your directions and completed all the steps. I was not able to add ||MusicNAS\music in Roon storage. It came up unexpected error. I rebooted the NAS as you requested and again was not able to add \MusicNAS\music. I got the same message in Roon, unexpected error.
I’m willing to try to help you folks resolve the issue but I don’t want to brick my NAS.
Since Mario tried ntp fix and it didn’t work, I assume I don’t need to.
I did try clearing the SMB cache and that didn’t work.
Im general, like Mario I don’t want to tweak my NAS. It works with every other device in my home outside of my Roon Rock. I really would love to see a fix from Roon… Since this didn’t repro before build 175.
Mohammed, you might try the NTP fix, that I got an error message from the NAS when entering the router IP as the server address doesn’t mean you will also. It’s also easily reversible.
Noris, I forgot to add I also cleared the SMB cache after resetting the NTP.
