PS3 fails to see DLNA without ReadyNAS reboot

Thank you very much for working this out. It has been bugging me (and my wife who in turn has also been bugging me) for some time :D

Not sure why Netgear changed this from the default of 30 seconds but changing it back works a treat!

msomekh wrote:

Well, I guess leaving it long enough solved the problem! :lol: Despite quite a few hits but no no feedback on the forum I hunted around for configuration files and finally found one that explained and help me resolve the issue. The file /etc/minidlna.conf defines a number of useful properties. The default value for notify_interval is 900 seconds and therefore I'm assuming that ReadyDLNA only broadcasts its availability every 15 minutes! Changing this to something more sensible (in this case 25 seconds) makes it available immediately after turning on the PS3. 34c34 < notify_interval=25 --- > notify_interval=900 Given that this is something that has stumped a few people, would it be possible to default the value to say 30 seconds and/or to expose the property in the Frontview add-on? Anyway, I hope this helps others who thought they were not able to get the NAS working properly for streaming to the PS3.

ohhhh, this is the same issue I'm having.
Now how to I edit the /etc/minidlna.conf file?

bthom70 wrote:
ohhhh, this is the same issue I'm having. Now how to I edit the /etc/minidlna.conf file?

I used msomekh's method http://www.readynas.com/forum/viewtopic.php?f=76&t=35289#p197407 - just make sure you read it all (especially the warnings about enabling root ssh access). It worked a treat :)

I've been struggling to apply this using my Mac.

I can't find the /etc/ folder except in the zipped backup file in the admin share.

I've tried the command line approach but I can't seem to access the right address because when I put my ReadyNAS Duo's IP in Terminal I get the error, 'command not found'.

I'd really like to get this sorted out because it has been driving me insane having to constantly either reboot the ReadyNAS Duo or restart the ReadyDLNA service.

Could some patient Mac using person walk me through this, please?

flamesong wrote:
when I put my ReadyNAS Duo's IP in Terminal I get the error, 'command not found'.

Forgive my ignorance if I'm wrong (I've never used a Mac) but to me that sounds as if you entering the wrong command, hence 'command not found' rather than some sort of message telling you the IP address is wrong.

A quick google turned up this information for SSHing on a Mac - once again, I have never used a Mac so I can't verify this is correct, but it looks correct to me. That plus this might have been what you were doing, in which case I have no idea... the site that I got this information from did mention creating a '.ssh' directory, but I don't know where that comes into this, hence I haven't noted it here. For those who are curious, my source was http://www.panix.com/help/sw.macosx-ssh.html, merely the first Google result.

With a terminal window open, type this command:

ssh -l root readynasip

where 'readynasip' is the IP address of your ReadyNAS. 'root' is the username you're logging in under, as the 'root' user has full access.

You'll then be prompted for your password, which will be the same as what the password for the 'admin' login was when you enabled SSH access - if you've changed your 'admin' password since then, the 'root' password will be the old admin one.

As many have already pointed out in this thread and others, accessing and making changes to your NAS as the 'root' user is serious business - don't play with anything you don't understand, as you can do serious, irreparable damage to your NAS.

Good luck :)

As this thread was extremely helpful for me to solve (or at least get rid of) the problem - thanks to everybody - I would like to tell you about my case, hoping this to be of some help for others.

I run a quite complex network within my house, with quite a number of PC's & notebooks (Win7 and Vista), streaming clients (Philips Streamium NP 1100, PlayStation 3, Nintendo Wii, 2 HD TV receivers of different make, Samsung TV and a multi media harddisk with NAS function - which is not used) and a ReadyNAS Duo. The network is established by Netgear Powerline equipment (a mixture of 80, 200 and 500 Mbit adapters), a WLAN router which is also connected via Powerline and an internet modem router with integrated 4-port switch, and a couple of Ethernet-switches. The Powerline stuff is used because the clients and NAS are spread over 3 floors and the basement with concrete ceilings inbetween, thus no access with WLAN to every piece of equipment.

Until recently it worked without any problem, whenever I started any of the streaming clients the ReadyNAS was recognized immediately.

Then all of a sudden I had the problem - similar to the one described by the others here - that after a restart of the PS3 there was no connection to the ReadyNAS and even a manual search for media servers on the PS3 did not bring any success. Of course not knowing about the 900 seconds issue I was impatient and restarted the the NAS (later on I just disabled and again enabled the ReadyDLNA service) after which the connection was established automatically, after a new reboot of the PS3 was lost again.

After reading through the first pages of this particular thread, I observed the sequence of 15 minutes (900 seconds) intervals after which the ReadyNAS got automatically connected to the PS3, but again after reboot of PS3 I had to wait for the alive signal of te ReadyNAS.

The problem only appeared with the PS3, all the other streaming clients, like the NP 1100 had no problem in finding the ReadyNAS.

Not wanting to fiddle around with the config of the NAS or the ReadyDLNA (in order to reduce the interval of the alive signal sent by the ReadyNAS) I followed Skywalkers conclusion of the combination of PS3 and network equipment beeing the cause of the problem (obstruction to the SSDP search packets sent by the PS3).

To finally make you understand the reason for the problem and the "solution" I have to add the following quite excessive story, sorry:

The PS3 (together with the wii, the TV and one of the HD receivers) is connected to the network via a Netgear Powerline XAV5004 which is a 500 Mbit Powerlan adapter with integrated 4-port switch. Previously the PS3 was linked via the predecessor model, the XAV1004 which is pretty the same (also with integrated 4-port switch) but at 200 Mbit standard. I had decided to replace the equipment recently because I had tested HD video streaming with a single port 500 Mbit adapter (XAV5501) and I was able to stream higher qualitity videos than with the XAV1004 and therefore ordered the XAV5004. But I had made the test with the single port adapter from a (power) wall socket which is 1 meter beside the one to which the XAV 1004 was connected (because the "original" wall socket is de facto inaccessible, but the XAV 5004 is using the same cable as the XAV 1004 therefore it was an option). After I received the new XAV 5004 I plugged it in instead of the XAV 1004 and realised that the performance was - disappointingly - not increased compared to the old XAV 1004. I plugged the new XAV 5004 to the other wall socket (from which I made the test) and the performance was improved. The conclusion can only be that either the wall socket which I have to use for the connector gives less performance or the power cable of the old and the new appliance are not compatible. As there was no option to use the better performance wall socket or replace the cable (I would have had to remove half of the living room furniture to get access to that stuff), I accepted the fact that there would be no improvement and put the XAV 5004 back to the original wall socket. The old XAV 1004 was used with the power cable of the new XAV 5004 in another room of the building, replacing an old 80 Mbit adapter with integrated 4-port switch.

Now I realised that this above mentioned replacement of the 4-port adapter was the only change I had made to my system within the last weeks (apart from a firmware update of the PS 3). I tried the following several times, consisering all possible combinations to be really sure:

I changed the network connection to the single port adapter plugged into the other wall socket, rebooted the PS3, ReadyNAS was recognized immediately. When I connected back to the 4-port adapter plugged into the original wall socket, I again had to wait for the 15 minute cycle to elapse before the ReadyNAS was beeing recognized (again no success by using the "search for media server" function).

This is a clear proof that Skywalkers theory of something within the network (probably the swich) is preventing the search packets sent by the PS3 from being received by the ReadyNAS! - at least in my case.

Then I took the power cable from the old XAV 1004 plugged it into the other wall socket and connected it to the XAV 5004 and surprisingly it also worked! Conclusion: The cause is not the switch (i.e. the XAV 5004), it is the wall socket?!

But it had worked before, when the 200 Mbit adapter-switch was installed and connected to the same wall socket! Therefore I tried the old XAV 1004 - and BINGO - since then it works again. Whenever I turn on the PS3 the ReadyNAS is found immediately, in any constallation I tried so far (and believe me I tried a lot).

I connected the XAV 5004 in the other room, where it is used by the Philips NP1000 (which is a network audio streaming device and internet radio, which also needs the ReadyDLNA Service). And here it works well, the NP1100 als findy the ReadyNAS immediately.

Final conclusion: The cause can be a switch or router, but it also can be - as it was in my case - a more complex combination of circumstances like type of switch and wall socket! I.e. a very tricky thing which can get very complex, don't give up trying out all possibilites you have. But it definitely does not seem to be the fault of the ReadyNAS or the ReadyDLNA Service.

Good luck.

It looks like I am having the same problem with my Samsung LED TV 'discovering' my NAS Server on my network as well. I'm not familiar with Terminal Services on a Mac unfortunately, would someone be kind enough to guide me through step by step how to get to the step where I can edit the config file? I'm worried I might muck up everything by attempting to do this on my own without proper instructions - the bit about the SSH part scares me!

Thanks in advance to any kind soul out there who might be able to help! :)

If you read EBM's post, you'll see that changing the NAS config with SSH might not help anyway. DLNA discovery depends on the reception of broadcast packets. If those are blocked by your network, changing the notify interval won't help.

Does the TV ever discover the NAS? If both devices have been on for an hour, then it should have seen at least 4 broadcast packets. So if it doesn't see it, then likely something else is wrong.

Maybe you can tell us how the TV is connected to your network.

BTW, you are right to be nervous about SSH, it is quite possible to break things. Since in some cases, a factory default is the only way to recover you should make sure you have a complete backup before you begin.

Hi I had this problem years ago when I got my 1st Duo v1.

The issue was with the router.

I was pulling my hair out - the whole purpose was to stream vids to my tv (via a ps3 at the time) and get rids of all the disks underneath the tv.

I'm still using the same router (fibre is coming soon so this will go then)

Problem - I can see my NAS on my pc but it virtually never showed up on my PS3.

At the time I ended up buying a netgear gs105 5 port switch (about £25) and connected the switch between the router and the nas. Basically the ONE thing plugged into the router now is the connection between the switch. All other network connections go directly into the switch. Nas, Ps3, laptops etc.

I can see the nas everytime on every device I have.

Over time my home network has expanded but I've worked on the same principle.

So I have 3 netgear gigabit switches (2x8 and 1x5) - still only use ONE connection on my router - hooking it up to one of the switches.

I've connected each of the switches via cable.

I've now connected the PS3 Wired via a homeplug (Develo) to a switch - this sees both the v1 and v2 duo dlna services 100% all of the time

I've a Panasonic Gt30 (Built in dlna client) - this see's both v1 and v2 duos 100% of the time.

All my pc's see both duos on wired and wireless.

I've hooked up a android tablet and phone (wireless) and these both see the dlna services on both readynas all of the time.

If I plug one of the nas into the router I get the original hit and miss. This confirms what Skywalker is saying in that it must be network related.

I've not rooted or the "hidded" settings on either nas drive - they are both on the latest firmware.

The only issues ive had other than this are:-

Duo v1 stuttering playback on Bluray files (10gb+) - resolved enablign jumbo frames on the v1 and using a wired connection

MKV playback on an android device - see my other post to do this

protected cinavia MKV playback to Panasonic Tv (this tv's dlna checks for cinavia) and PS3 - fixed but is it ok to post a working solution on here??

Streaming MKV to PS3 - re-encode

Rather than start a new thread needlessly, I wanted to ask a similar question.

My PS3 is able to access the ReadyNAS no problems through DLNA, and I can see all the folders. However, when I update the folders, add more video/music files in the same folders it can't see the new files. It only sees the files I first added.
Similarly when I delete the files the folders don't update on the PS3 - the name remains (obviously can't be accessed).

I've tried re-starting the ReadyNAS drive to no avail. Any other suggestions?

I have the ReadyNAs Duo V2, with the latest firmware.