Synology 1817+ and Synology 918+ both core servers are running OK. They both can’t add a network path. The message always show unexpected error. \IP\folder name OR smb://IP/folder name. Same address was tested under MAC and Windows. Both OK. I even tried \IP or smb://IP both showed ‘invalid network path’, which is tested OK in MAC OS X and WINDOWS.
1817+ or 918+ locates at the same VLAN of network folder source. network should be no problem at all.
Hello @bin_xiao,
Can you please post a screenshot of the SMB settings and the error that Roon is displaying? You should be able to add the network path’s using these instructions. What kind of network share are you trying to add? Are you trying to link the NAS to each other or to a library located on another computer?
Thanks,
Noris
I’ve tried the mac version and windows version core. they both can add the a network share from my another computer or NAS. But even the mac and windows version, the network share don’t accept the \\192.168.1.100\ or \\192.168.1.100, you have to add the Directory，that means you can’t use the root Directory to share. Mac and Windows Core only work when you use \\192.168.1.100\music
The only difference is the RED error message “Unexpected Error” shown
Hello @bin_xiao,
We’re going to do some testing on our end to see if we can reproduce similar issues with pointing one Synology to another, but are you absolutely certain that the IP address is valid on both of your Synology drives? Can you please check in the Router or use FING to verify this fact?
Thanks,
Noris
2 locations. I am a network pro. 15 years in IP Network for Telecom Carrier.
First location: layer 3 switching , router 192.168.10.1 - 192.168.10.2 Layer3 switch 192.168.20.1/24 - Wired ROON on synology 918+ , audio devices , ROON controller computer and SSID for mobile devices.
Second location: Router on stick, VLANs on Router sub-interface. router 192.168.1.1 – same native VLAN – ROON on synology 1817+, audio devices, ROON controller computer and SSID for mobile devices.
All synology NAS updated to newest firmware.
Hello @bin_xiao,
Thanks for letting me know that info. We took a look on our end and have not been able to reproduce this issue so I am thinking that this could be networking related. I have two follow up suggestions:
Can you please manually send us the logs from your machine that you are using to connect to that share? You can follow these instructions to get it over to us (if you don’t have Google Drive or Dropbox just let me know and I will provide an alternate upload method).
Are you able to connect to that share from outside of Roon but still on the same machine? As in are you able to SSH into the NAS and are able to mount the same folder?
Please let me know this info when possible.
Thanks,
Noris
Hello Noris,
The following link is logs: https://drive.google.com/file/d/1_U9aNJ62QIrqvuRjMcAZjXIEFluYSU_T/view?usp=sharing
I can share from outside of ROON both on the NAS and other computers or mobile phones. I even mount the share folder on synology correctly from the 2 computers, you can see from log. I can read, write on the NAS mount folders.
share1: \192.168.20.100\temp
share2: \192.168.20.187\Movie
Hope these can help you to find the solution.
Hello @bin_xiao,
Thank you for sending us those logs. I have started a case for you with our QA team and have asked them to take a look. I will be sure to let you know what they say once this request reaches their queue and appreciate your patience until then. Thanks!
– Noris
Hello @bin_xiao,
I spoke to QA today regarding your case and we believe that the proper way to verify if this issue is OS dependent or localized to your NAS would be to try mounting that share from the other NAS, and not on another computer.
If you are able to mount the 2nd storage location from the NAS that Roon is installed on it would give us a much better data point rather than mounting it from two other computers.
Thanks,
Noris
Both computer smb folders were mounted on the NAS that Roon installed, not in the ROON but under the synology DSM 6.2
I think the case is not only on my ds918 , the same on my friend’s 1817 as mentioned above already. base the SMB / Other version ROON tests and network double check, I think the problem is ROON spk on the synology NAS. maybe just some codes are not compatible with SMB 1.0 to SMB 3.1, which are used in different windows version. I discovered the KODI also has the problem with SMB versions. when the SMB version not the 1.0 the KODI can’t read the SMB from NAS or Computers by default. Maybe the case was not discovered widely because not many people use multi NAS or computers SMB when centralized music files are in the single synology NAS, which ROON is installed.
Hello @bin_xiao,
Can you please let me know which of your NAS’ are making use of SMB v1 and which one is making use of SMB v3.1? It is not clear from your post, but that could be the reason why this issue is occurring. If you switch SMB versions for the NAS that is using the incompatible version, does it help?
Thanks,
Noris
I am not sure about ROON core (synology) whether the SMB version cause the malfunction of network share. It should be run tests.
What i am sure is kodi SMB problem caused by SMB version. By default, the QNAP NAS use the SMB v1-v3. The Windows 7 use SMB 2.x , and Windows10 use SMB 3.x. The KODI 17 was installed on MACBOOK, when the QNAP set to minimum SMB version to SMB 2.0, the MAC KODI cannot read the NAS network folder from QNAP. But macosx , win7 and win10 can read network folder from QNAP. When you switch back to minimum SMB version 1, the MAC KODI network folder came back. It’s the case what i found using KODI.
I think maybe the ROON CORE synology has the unexpected error similar to that case. Your R&D or QA should do tests if that error can’t be fixed from the ROON LOGS I provided. or maybe that just synology software somewhere incompatible problem with the ROON CORE or some linux lib files missing. Because that’s not only my particular ds918+ also my friend’s ds1817+ both running the DSM 6.2. We both have to switch to PC ROON CORE and keep PC 24h running.
Hello @bin_xiao,
I had a meeting with the devs today and they have noted that this isssue is most likely due to your network. On our end, Roon is reporting the following:
01/07 09:37:31 Debug: [roon/cifs] domount: PASSWD="******" /bin/mount.cifs "//192.168.20.100/temp" "/mnt/RoonStorage_40d52741ec4847acac13a336f46b64bfd37e8804" -o guest,nounix,iocharset=utf8,user="xb",domain="WORKGROUP",vers=1.0 01/07 09:37:31 Debug: [roon/cifs] returned 112: mount error(112): Host is down
And the logs are also a very strange local IP for the DS918 of [ “172.17.0.1” ]. I’m not quite sure why this would be happening if everything is on the same VLAN but I would suggest taking another look at the network here.
Thanks,
Noris
Thanks for reply. I think that’s not only my synology problem only.
I just use the 2 NICs port on 918+, different VLAN, already give the default route to 192.168.20.1.
There is no any problem of 918+ mount SMB folder to DSM system itself from Win7/Win10 computers. The error only happened in ROON.
ALL are default settings of synology except NIC IPv4 addresses, GW and default route. The openswitch is enabled by default, if virtual machine used. The ‘172.17.0.1’ is just the docker container address for NAT by synology default setting.
The following 2 parts I copied from SSH: 1 for route display , 2 for interface display (just use * for MAC for my privacy)
root@sunkoda_ds918:~# route -v
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.20.1 0.0.0.0 UG 0 0 0 ovs_eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 ovs_eth0
192.168.137.0 0.0.0.0 255.255.255.0 U 0 0 0 ovs_eth1
root@sunkoda_ds918:~# ifconfig -a | more
docker0 Link encap:Ethernet HWaddr *************
inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3437 errors:0 dropped:0 overruns:0 frame:0
TX packets:929163 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4672765 (4.4 MiB) TX bytes:93267528 (88.9 MiB)
docker3da Link encap:Ethernet HWaddr *************
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:925648 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:87298032 (83.2 MiB)
dockerc52 Link encap:Ethernet HWaddr *************
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:925658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8759 (8.5 KiB) TX bytes:87299529 (83.2 MiB)
eth0 Link encap:Ethernet HWaddr *************
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:982001449 errors:2 dropped:0 overruns:0 frame:2
TX packets:5120539528 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92642665135 (86.2 GiB) TX bytes:7709585784784 (7.0 TiB)
eth1 Link encap:Ethernet HWaddr *************
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8394350 errors:0 dropped:0 overruns:0 frame:0
TX packets:2317231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2247254130 (2.0 GiB) TX bytes:324257140 (309.2 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:139754154 errors:0 dropped:0 overruns:0 frame:0
TX packets:139754154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:34362058868 (32.0 GiB) TX bytes:34362058868 (32.0 GiB)
ovs-syste Link encap:Ethernet HWaddr *************
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ovs_eth0 Link encap:Ethernet HWaddr *************
inet addr:192.168.20.20 Bcast:192.168.20.255 Mask:255.255.255.0
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:971347223 errors:0 dropped:0 overruns:0 frame:0
TX packets:164457829 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:78210355343 (72.8 GiB) TX bytes:7424601848726 (6.7 TiB)
ovs_eth1 Link encap:Ethernet HWaddr *************
inet addr:192.168.137.137 Bcast:192.168.137.255 Mask:255.255.255.0
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:531712 errors:0 dropped:0 overruns:0 frame:0
TX packets:942216 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:150827366 (143.8 MiB) TX bytes:90089802 (85.9 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tap021132 Link encap:Ethernet HWaddr *************
inet6 addr: ************************ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:850075 errors:0 dropped:0 overruns:0 frame:0
TX packets:3744368 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:162248609 (154.7 MiB) TX bytes:1262095841 (1.1 GiB)
I confirm to report that error becasue of SMB version in windows. The ROON and synology ssh cmd both use the MOUNT command, even plus vers=1.0 vers=2.0 or vers=30 option under ssh cmd of synology manually, the roon core error is still there. The MOUNT command of synology cmd mode or ROON is only compatible SMB 1.0 version which is not support by Windows since 2017 in default installation.
After I install extra SMB 1.0 version windows additional software package in control panel, the synology ssh cmd mode and ROON core can add network folder from win10.
Although enable SMB 1.0 from windows end is the easiest way, I still hope ROON can improve the code on synology core, like synology DSM FILE STATION can mount remote any windows version’s network folder in default setting.
Hello @bin_xiao,
Thanks for letting me know that the issue was due to the SMB version of Windows that you had installed.
I’ll discuss with the team to see if we can do anything to improve here but glad that you resolved the issue.
– Noris
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
