It runned for a few minutes, one or two, all pings were <1ms, a few went to =1ms then it just started spamming “General Failure” and pow, Request Timed Out.
When you’re viewing or listening to media, are you using “Media Server” or “Network Shares?”
Does this happen on ALL media, or is there a pattern?
IN ADDITION to the PING test above, try it again with an ADDITIONAL ping running, where the destination is your router’s IP address (do this in a second CMD window.)
When the WDTV “fails,” IMMEDIATELY go to the SETTINGS / NETWORK and do a CONNECTION TEST.
Alright, so it was a bit different this time, the WDTV “crashed” when the network dropped, I couldn’t go back to the Home menu or do anything, it was frozen on the movie. At some time it decided to return to the media page but I couldn’t do anything except power cycle.
It almost does the same thing on and on : for larger files it takes about 3 to 4 minutes to crash, on the ping windows, it’s General Failure at the same time for both devices, then time out.
For SD files, it takes more time but in the end, it still drops.
It’s really strange because it does not stutter at all or lag or anything, it’s just dropping at some point…
Thanks for the support!
Every time I get a new gadget, I get bad lucks and it doesn’t work… eh… story of my life…
You say when it fails, BOTH the ROUTER and the WDTV stop pinging?
If so, then the fault is either your computer or your network, and the WDTV is just a victim.
It is NOT unusual for the WDTV to completely crash like you describe if the share goes away during a stream. It’s a bit of a bug, but actually is more inidication that your network is unstable.
You didn’t answer my other questions, though: Are you using SHARES, or MEDIA SERVER? Does it happen on ALL MEDIA, or is there a pattern? Also, if the WDTV doesn’t crash, go do the Connection Test I described.
Also, you could test this: Take your router out of the path. Use a simple Hub or a Crossover Cable to hook your WDTV DIRECTLY to your PC. You will likely need to set the IP addresses for the PC and WDTV manually if you do this test.
I’m just annoyed because I just bought this device, and it had the same bug with my old router (WRT54G), and now, I’ve spent 100$ on this new router and it still does the same ■■■■ and it seems like I’m not the only one in this situation…
Ok, PBEAR, I made an assumption; apparently an invalid one. My Apologies!
I assumed that, since you said that BOTH the WDTV and the ROUTER go unresponsive to pings at the same time, that the router WAS rebooting itself. So, that’s not the case, huh?
Well, then it may be an IP Stack issue on the PC, so let’s move in that direction.
IMMEDIATELY During a failure (when PINGs are going unresponsive) issue the command