NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't stream from DLNA without a reboot
I've been using the DLNA successfully for a while now with my ReadyNAS NVX Pioneer. I'm not sure if my problems started after the latest radiator update or before that. When I attempt to stream a video file from my PS3 I get a message that the file can't be accessed. Rebooting the ReadyNAS solves the problem and I can watch the video. When I try again on a different file the next day, I get the same error. Once again, rebooting fixes the problem temporarily.
Different message, but same result from the Xbox 360.
Is anyone else seeing this issue? Obviously rebooting everyday isn't really how id like everything to be running. Any suggestions?
Different message, but same result from the Xbox 360.
Is anyone else seeing this issue? Obviously rebooting everyday isn't really how id like everything to be running. Any suggestions?
19 Replies
Replies have been turned off for this discussion
- Sorry, haven't logged in here in a while. When it is in this state the command "netstat -ap | grep minidlna" will show you where its sockets are connected. Maybe it is one particular device which is misbehaving.
steve - Here's the result. I'm not sure how to interpret this.
tcp 0 0 *:8200 *:* LISTEN 2682/minidlna
udp 0 0 ReadyNAS:40992 *:* 2682/minidlna
udp 0 0 *:1900 *:* 2682/minidlna - Well if you are in that state when you ran this, then I think it means that minidlna has done it's thing but the sockets are still tied up in the OS. Try this:
netstat -nat | awk '{print $6}' | sort | uniq -c | sort -n
This will produce output like this:
1 established)
1 Foreign
13 ESTABLISHED
20 LISTEN
26 TIME_WAIT
My guess is when you are wedged you will see lots of TIME_WAIT connections. I believe that can happen if a client (some device in your house) is not following the right disconnect sequence.
steve - Nope.
1 established)
1 Foreign
8 ESTABLISHED
12 LISTEN - Hmm. Well. Clearly it's something to do with minidlna since all those sockets were listed. Maybe netgear could suggest some verbose logging or something to see what the server is doing. Those last two outputs were when the server was wedged right?
- Somehow missed that you had responded. I kept checking and didn't see it. Yes, those last two outputs are from it being clogged, wedged, hung up and not working.
- Looking at logs, the only guess (and it is a guess) that I can make is the Xbox is opening a connection like every 10 minutes to check in while on. Every time it does this it is on a new socket or port (not sure which) that doesn't get closed again. I'm not sure if this is Netgear's fault or Microsofts. Either way, I'd like to report it to Netgear, but don't know the procedure to do this when the NAS is out of warranty.
- Maybe PM Skywalker.
- I opened a support case.
Edited: I misread the response originally. They want me to reset with a paper clip. I'll try tomorrow when I'll have time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
