NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Duo - Minidlna - Very, very slow discovering service
Model: ReadyNAS Duo [X-RAID] Serial: 24M3117Y01978 Firmware: RAIDiator 4.1.16 [1.00a043] Memory: 256 MB [2.5-3-3-7] I have had the NAS for a while and it has been running minidlna fine ...
....also, the NAS is on timer so reboots each day - so the minidlna service is also obviously restarted daily....
Try enabling ssh on the duo, and looking at notify_interval in minidlna.conf.
The default is 30 seconds (so if it is commented out, that is how often the server sends out a NOTIFY message). That's a reasonable value. But it might not be commented out (and might be set to something more like 15 minutes). If that's the case, try using the default.
Also, see if something on the NAS is interfering with the service (either a nearly full OS partition, or a high CPU load). By default, the NAS puts it's DLNA cache on the OS partition - which isn't great, because that partition is quite small (2 GB on a NAS running 4.1.x firmware). You might want to move that cache to a folder on the C volume.
The NOTIFY is an unsolicited advertisement. The other mechanism is that the DLNA client broadcasts a query ( M-SEARCH ), and the DLNA server responds to that query. It sounds like the M-SEARCH might be being blocked by your network infrastructure - which is puzzling, since that doesn't seem to be happening with the fedora-hosted server. You might try toggling the UPNP service in your router and see if that helps (turning UPNP off if it is on, or vice versa).
Another option might be to mount the duo shares on your Fedora, and just use it's server. Though you'd need to script that since you are using the power timer on the NAS.
There are some upnp developer tools out there, including https://www.meshcommander.com/upnptools. I haven't used them, so I don't know how helpful they would be.
Thanks for the reply.
The issue seems to be some form of timing as the panasonic smart music apps eventually pick up the NAS and once 'acquired' seem fine. So I have the panasonic TV and speaker ok and the roberts radios ok. Just the Onkyo is being stubborn and just won't see anything apart from my laptop minidlna server and that's working fine as starting and stopping the service on my laptop reflects ok on all the clients.
Starting and stopping the NAS minidlna works ok'ish now apart from the Onkyo - which would tend to point at the Onkyo more ...
The notify interval was set to 900 (but so is the minidlna conf on my laptop) - so I've set that to 30 without much luck. 'Top' is showing nothing manic on the NAS - it's doing bugger all - and I've still got 1,4 GB of the 1.9 in the root fs. So all seems ok on the NAS.
I've toggled the UPNP settings on the BT HHUB - and made sure they were saved - no joy.
I have turned the Onkyo off and on from source rather than just to/from standby - and that's done nothing.
Frustrating as hell as all this has been working fine for years! I'll check the Onkyo to see if I've had any auto firmware updates on that (not sure if I can see that though - I think it just shows the firmware version and not the date updated).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
