+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Sinology reconnect (/showthread.php?tid=1818)
Sinology reconnect - pisuke74 - 10-16-2019
Hi. I've configured nas synology as upnp. After scan.. Works but after a while the synology disappear. I have to do a remount and a new rescan.. Where s the problem? Thanks
RE: Sinology reconnect - Tim Curtis - 10-16-2019
Just saying "it doesn't work" is not going to be enough to troubleshoot your issue.
RE: Sinology reconnect - pisuke74 - 10-16-2019
right Tim ..
so if i configure as a smb network moodeaudio identify my sinology..but after a while (scan a letter and b letter...) stop scan...
i ve tried upnp but have the same problem
via smb it's mounted at restart.. but only with 2 folder scanned
on sinology it's configured to accept smb 1 to smb 3
RE: Sinology reconnect - Tim Curtis - 10-16-2019
It sounds like some sort of network or NAS configuration issue. I don't own a sinology NAS so I'm not going to be able to help but maybe another Synolog user will reply.
RE: Sinology reconnect - pisuke74 - 10-16-2019
thanks. i will wait a synology user
RE: Sinology reconnect - Tim Curtis - 10-16-2019
In the meantime you could try some basic network diagnostics.
1) Run a 30 second ping test from the Pi to your NAS and see if there are any errors or %packet loss in the ping stats. Below is an example from one of my Pi's to my Router which also functions as a NAS.
Code:
pi@rp3:~ $ ping rt-n66u
PING rt-n66u.home (192.168.1.1) 56(84) bytes of data.
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=1 ttl=64 time=2.18 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=2 ttl=64 time=2.06 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=3 ttl=64 time=2.04 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=4 ttl=64 time=2.10 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=5 ttl=64 time=2.11 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=6 ttl=64 time=2.11 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=7 ttl=64 time=2.05 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=8 ttl=64 time=2.13 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=9 ttl=64 time=2.18 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=10 ttl=64 time=2.16 ms
64 bytes from www.asusnetwork.net (192.168.1.1): icmp_seq=11 ttl=64 time=2.15 ms
^C
--- rt-n66u.home ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 22ms
rtt min/avg/max/mdev = 2.043/2.115/2.184/0.055 ms2) Examine the stats for the network interface on the Pi and see if there are excessive number of retires or dropped packets. Example below from one of my Pi's using WiFi (wlan0)
Code:
pi@rp3:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:17:f7:00:a7:89 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1516 bytes 213588 (208.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1516 bytes 213588 (208.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.137 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::9f03:694a:d812:8ab9 prefixlen 64 scopeid 0x20<link>
ether 20:0d:b0:32:34:a2 txqueuelen 1000 (Ethernet)
RX packets 64864 bytes 55145615 (52.5 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 44359 bytes 5112613 (4.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0RE: Sinology reconnect - pisuke74 - 10-16-2019
thanks
all test done. no errors
RE: Sinology reconnect - Tim Curtis - 10-16-2019
Thats good :-) Prolly can rule out network.
Here is the command for the Samba scan
Code:
sudo smbtree -N -bRE: Sinology reconnect - pisuke74 - 10-16-2019
after this command nothing happens
RE: Sinology reconnect - Tim Curtis - 10-16-2019
That suggests several possibilities including (1) SMB broadcasts are being blocked by some network device or (2) the NAS is not advertising its Samba shares or (3) something else on the network is blocking SMB protocol.
You could try using the IP address of your NAS instead of its host name when creating the NAS config in moOde. If there are still issues then I would suspect something on the NAS.