NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
UteDohrs
Feb 18, 2014Aspirant
ReadyNAS OS 6.1.6FINAL no ReadyDLNA after Cold-Start
No ReadyDLNA after a cold-start (Power OFF/ON)
ReadyDLNA is "green" acktive in Services, but AV-Receiver and TV can't see the RN104 in Network.
After toggle "TiVo-Server" from ON/OFF or OFF/ON AV-Receiver and TV can see and use the volumes from RN104.
This bug is old and not fixed.
Every morning i have to start my PC... to go on RN104 Website... and toggle this TiVo-Server option.
Where is the context ???
I don't want to use a TiVo-Server (dont know what it is ??) but i have to use its options....
> It does NOT help > same problem as before !
Sorry but i don't agree that this is a problem on my side !
it IS a BUG since 6.1.3 !!!
ReadyDLNA is "green" acktive in Services, but AV-Receiver and TV can't see the RN104 in Network.
After toggle "TiVo-Server" from ON/OFF or OFF/ON AV-Receiver and TV can see and use the volumes from RN104.
This bug is old and not fixed.
Every morning i have to start my PC... to go on RN104 Website... and toggle this TiVo-Server option.
Where is the context ???
I don't want to use a TiVo-Server (dont know what it is ??) but i have to use its options....
Skywalker wrote:
UteDohrs wrote: Also usefull for my DLNA problem ??
No, not likely. His issue was the server never appearing, rather than only appearing after unsolicited SSDP announcements. Your issue continues to look like multicast SSDP packets getting dropped in your network. If you want a workaround for that, you can configure the DLNA service on the NAS to send out very frequent unsolicited SSDP alive announcements. This isn't recommended on a normal network, but it will probably help your situation. You can execute this command from an SSH command line:echo notify_interval=10 > /etc/minidlna.conf.local
> It does NOT help > same problem as before !
Sorry but i don't agree that this is a problem on my side !
it IS a BUG since 6.1.3 !!!
11 Replies
Replies have been turned off for this discussion
- SkywalkerNETGEAR ExpertIn reviewing the code, we did find one situation where multicast packets may not make it to the multicast group if the network comes up late (like with a very slow DHCP server or something along those lines). You can follow the instructions at viewtopic.php?f=22&t=75457 to update the package, which includes a fix for this.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!