PS3 fails to see DLNA without ReadyNAS reboot

Sent you a PM.

Hi!

I've got a similar problem. My setup is like this:
Streamium MCi300 ((-)) WiFi-router (Speedtouch ST585) --- GB-ethernet-switch --- ReadyNAS NV+ (RAIDiator 4.1.6 and latest DLNA-Server; DLNA, iTunes and UPnP enabled).

IP-Range is 10.0.0.x, all devices get their IP by DHCP (managed by the router), netmask is 255.255.255.0. There are some Linux-boxes (wired and wireless), an iPhone (wireless) and a Windows7-PC (wired) on the net as well. Access to all resources on the NV+ (shares, printer) by wire and wireless is possible.

The Streamium device does not find the UPnP Mediaserver on the NV+, even after a long time of searching. However, it does find it if the W7-PC is started (right after Windows shows the login-prompt).

I already tried to shorten the notify-interval and it did not change anything, so I changed it back to the default-value.

I would appreciate any suggestions.

Thanks and a merry X-mas.

Peter

Thank you so much. This was driving me nuts and your 900 to 25 second solution works a treat. It even works via "Homeplugs" (Ethernet over electricity circuit).

System:
ReadyNas Duo - BT Home Hub 2.0 - Homeplugs (direct connection too) - PS3

Had to work hard to understand the "putty" program but got there in the end.

Merry Christmas!!

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

Help! I've just got a Duo but having a similar problem with my PS3 not picking it up. Here's the problem. When the PS3 is first switched on it doesn't pickup the Duo, after 5 minutes or so, it then sees it. If I then PlayTV on the PS3, when I quit this, the PS3 seems to loose the Duo. I have to wait another 5-10 minutes for it to pick it up. If I use the search for media server button it doesnt find the Duo, in fact, when the Duo is showing and I search for media serve, it Duo is lost and the PS3 says no servers to be found.

I think making the change to the 900 sec to the interval could work? The instructions from msomekh look great but this is using putty and I've a mac. I've read that I can do this through Terminal but adding program commands is all new territory and am obviously keen not the screw anything up. Can someone talk me though how to edit the 900 sec through a mac.

Thanks

setup - PS3----BT Homehub------Duo

Me too, I am fairly new to SSH and am willing to give it a try as it sux to have to wait 10 minutes for my DUO to show up.

I am also on a mac and installed the SSH add on but I cant seem to log onto the NAS and wouldnt know how to edit a file. Anyone willing to talk us through it?

Cheers

T

If you get to the command line, just use this command:

sed -i 's/notify_interval=900/notify_interval=30/' /etc/minidlna.conf

If you have a switch on your network with ICMP snooping enabled, you can also try disabling that.

Thanks for that, however I cant even log on.

I tried ssh admin@myip

It asked for my password but then I get the following error message:

admin@192.168.1.33's password:
Linux nas-CD-CD-C9 2.6.17.8ReadyNAS #1 Tue Jun 9 13:59:28 PDT 2009 padre unknown
Connection to 192.168.1.33 closed.


What am I doing wrong?

UPDATE: Ok, after searching the forum some more I logged in as root@myip and used your command line and it worked!!!!

Thanks a lot!

Just want to say thanks for the information in this thread.

For months I've been trying to get my XBOX 360 and other systems connected via DLNA, which would only work after a reboot. Making the suggested change has now made it work and I'm finally able to stream everything off the ReadyNAS.

Ben

I hope this is fixed in the next update for non-geeks like us. I don't want to use SSH etc and risk hosing my Duo.