NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NV+ video streaming problem
I just nought myself an NV+ NAS.
I'm surprised that its so noisy :(
Don't know where to put it, you can hear the noisy allover the house :( :(
I have a probkem when streaming videos to my samsung tv.
It stops after 20 minutes, then I can start it again and forward to where it stopped, and then again it stops after 20 minutes.
Why does it do that???
I'm surprised that its so noisy :(
Don't know where to put it, you can hear the noisy allover the house :( :(
I have a probkem when streaming videos to my samsung tv.
It stops after 20 minutes, then I can start it again and forward to where it stopped, and then again it stops after 20 minutes.
Why does it do that???
10 Replies
Replies have been turned off for this discussion
- Normally the fan starts up loud, and then gets quiet. Once it quiets, I can hear it in the same room, but not throughout the house.
Frontview (health) shows you the fan speeds and disk temperatures. You should probably post them - if the fan never slows down, then you might have a hardware issue in the chassis. - No help here???
Really annoying that the streaming stops after 20 minuts...
And not really useful. - +1, except mine is a duo, between 10-30 minutes it stops and I have to come back and get to where I was.
- It would be fantastic if someone from netgear would comment on this!
Plastic fantastic!
Lots of fine specifications, but nothing works the way it should.
I have also tried to get the iTunes server to work, without luck. - I went through some of the UpnP logs from my Duo, it's showing the following:
[2011/11/19 08:57:47] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/19 08:59:36] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/19 08:59:51] upnphttp.c:958: warn: HTTP Connection closed unexpectedly
[2011/11/20 09:26:24] upnphttp.c:953: error: recv (state0): Connection reset by peer
Again, happens every 20-30 minutes or so. The TV firmware has not changed, the only thing that has changed was the .18 update on my duo. - Unsure if any of these are related or not, but maybe the Jedi's can make some sense out of it.
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:32] minissdp.c:331: error: sendto(udp_notify=10, 192.168.0.122): Invalid argument
[2011/11/05 18:08:34] minidlna.c:153: warn: received signal 15, good-bye
[2011/11/05 18:08:43] minidlna.c:896: warn: Starting ReadyDLNA version 1.0.22.
[2011/11/05 18:08:43] minidlna.c:991: warn: HTTP listening on port 8200
[2011/11/06 18:27:47] minidlna.c:153: warn: received signal 15, good-bye
[2011/11/06 18:29:03] minidlna.c:896: warn: Starting ReadyDLNA version 1.0.22.
[2011/11/06 18:29:03] minidlna.c:991: warn: HTTP listening on port 8200
[2011/11/08 17:24:20] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/09 18:39:17] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/12 17:08:32] minidlna.c:153: warn: received signal 15, good-bye
[2011/11/12 17:08:41] minidlna.c:896: warn: Starting ReadyDLNA version 1.0.22.
[2011/11/12 17:08:41] minidlna.c:991: warn: HTTP listening on port 8200
[2011/11/12 19:05:47] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/13 16:02:56] upnphttp.c:953: error: recv (state0): Connection reset by peer
[2011/11/14 22:12:30] minidlna.c:153: warn: received signal 15, good-bye - Has anyone found any solutions?
- Bump for a DLNA fix.
- Hi
might not be related, but have you tried the 'no smb disconnect' addon? Could be this. - d14blo, UPnP-AV/DLNA and SMB are two separate things. Unless SMB/CIFS is being used there is no point to using the add-on you refer to.
Would suggest opening tech support case.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
