NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PS3 fails to see DLNA without ReadyNAS reboot
Hi all, I've found various threads on this issue but no solution so I'm hoping there's an answer that I've just missed. When first switched on, my Playstation 3 is only able to see the NAS drive th...
Happy New Year to all of you.
I'm using a quite different setup, a Buffalo LinkStation Pro with Debian Etch and minidlna checked out from Sourceforge's CVS at 2010-01-01. The LinkStation is connected to a TV of type Samsung LE 40 B 650 using a WiFi USB stick (off-topic: not a Samsung WiFi stick, it's made by Hama, one third of the Samsung price, same functionality:-).
Two remarks on that, the first one directly regarding this topic and the second one a bit off-topic regarding the Samsung TV using a WiFi connection.
Remark 1 on minidlna: Interestingly, I observe the same problem, and the same resolutions work for me, i.e. either restarting the minidlna daemon, or setting notify_interval to a pretty low value. Even more interestingly, I can use the default notify_interval of 900 without problems if I start the minidlna in debug mode, so it does not put itself into background. So I guess there is a problem with minidlna backgrounding itself, maybe the shortened interval lets the daemon return to its listen() loop earlier, or some other blocking takes place.
Remark 2 on Samsung TVs: When using a WiFi stick, the IP connectivity depends on if the TV is set to using DHCP or a fixed (manual) IP address. Using DHCP: When pressing the MEDIA.P button on the TV's remote (this button should connect the TV to the DLNA server), nothing happens, the TV will not setup an IP connection at all. Forcing an IP connection can be done by using the INTERNET connection of the TV. Using a fixed IP address instead of DHCP: After pressing the MEDIA.P button at least twice, the IP connection will be established to the DLNA server.
Keep on this good open source work, viele Grüße,
Heiko
I'm using a quite different setup, a Buffalo LinkStation Pro with Debian Etch and minidlna checked out from Sourceforge's CVS at 2010-01-01. The LinkStation is connected to a TV of type Samsung LE 40 B 650 using a WiFi USB stick (off-topic: not a Samsung WiFi stick, it's made by Hama, one third of the Samsung price, same functionality:-).
Two remarks on that, the first one directly regarding this topic and the second one a bit off-topic regarding the Samsung TV using a WiFi connection.
Remark 1 on minidlna: Interestingly, I observe the same problem, and the same resolutions work for me, i.e. either restarting the minidlna daemon, or setting notify_interval to a pretty low value. Even more interestingly, I can use the default notify_interval of 900 without problems if I start the minidlna in debug mode, so it does not put itself into background. So I guess there is a problem with minidlna backgrounding itself, maybe the shortened interval lets the daemon return to its listen() loop earlier, or some other blocking takes place.
Remark 2 on Samsung TVs: When using a WiFi stick, the IP connectivity depends on if the TV is set to using DHCP or a fixed (manual) IP address. Using DHCP: When pressing the MEDIA.P button on the TV's remote (this button should connect the TV to the DLNA server), nothing happens, the TV will not setup an IP connection at all. Forcing an IP connection can be done by using the INTERNET connection of the TV. Using a fixed IP address instead of DHCP: After pressing the MEDIA.P button at least twice, the IP connection will be established to the DLNA server.
Keep on this good open source work, viele Grüße,
Heiko
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
