dcb917 wrote:
Well in this case the issue had nothing to do with Windows 8 as it turned out so I stand by my comment.
The real issue here is that these forums are filled with people complaining about WDTVs and networking issues. Do you really think cmd line work to jack with the master browser, turning off home groups, turning on/off services, ip assignments, etc etc are par for the course and reasonable to get these things to work? We can ridicule Apple and MS for how bad their networking is, but at the end of the day isn’t that pretty myopic? Blaming the main OEMs that you HAVE to support to be successful? How many of these boxes would WD sell if they dropped support for MS? Lol.
The other thing is that I have all kinds of things connected to my network that are a lot more sophisticated than the WD box…none of them took the gymnastics that WD took to get working…and the real issue is that anytime I introduce a new device to the network I have to remember about how easy it is to break the WD. I bought 2 WDs, but after that got smart and went with Roku/Plex, better and an easier to set up.
I still use my WDs as they now work, buy you guys are in denial if you think there are not serious networking issues with them. Maybe you’ll believe me when WD rolls out the replacement product and you see it networks like a champ. Then you can sit around here and tell newbies how hard it was in the old days.
You said it was “utter rubbish” to claim that Windows 8 should be considered as the possible cause for the problems. I stand by my position that that is ridiculous. The fact that Win8 did not happen to be the cause in this particular case is completely irrelevant. You can easily find many cases on this forum where Windows most definitely was the cause of the problems. Most Windows users do not understand Windows file sharing and file security settings, so it is far from unlikely that bad Windows settings are to blame for issues.
I have encountered absolutely zero problems with the two SMPs that I have on my network. Absolutely zero. Took me literally less than 5 minutes to have my first SMP streaming from my (existing) Samba server. Wired networking auto/DHCP, change workgroup, select Windows/SMB server. Done. Yeah, what a lot of gymnastics, huh? Of course I am knowledgeable about computers and networking (CS PhD), so had a properly setup network with carefully selected and properly functioning network gear. This is clearly not the case for many people–as the source of the problem for the OP in this thread demonstrates yet again.
The fact that you seem to be suggesting that any networked device like the WD TV units ought to be able to function in spite of any set of incorrectly setup and/or functioning network equipment shows that you do not understand the basics of network protocols. It is trivially easy to render a LAN severely non-functional. My experience with every networked multimedia device that I have owned is that the vast majority of problems users report on the forums are related to network issues, with the vast majority being due to improperly setup or functioning network gear. Are you saying I won’t be able to find any people reporting network-related issues with Roku devices? I doubt that is true.
Saying that users shouldn’t have to deal with what machine is the master browser and similar network setup details is all fine and good, but it displays your ignorance of the fact that these are inherent elements of protocols like SMB, so there is no choice but to deal with them. Wecome to the realities of networking: it is often not plug-and-play and almost none of the protocols were designed to be configured by non-technicals users–as is frequently being done today. If you don’t like that fact, then stick with using an external drives plugged directly into your media players.