1. There will definitely be a successor to the WD Live SMP â thatâs life with technology.
2. The question is when?  Who knows?! I think sometime well before Christmas, so they can become Xmas presents! Most major new gizmos appear late summer to early fall. (Unless the target date slips and they are late!)
A new device where networking just works would make the forum for that device a pretty quiet place:stuck_out_tongue:
Hmmm, not a chance â most network problems are not caused by the player; they are caused by improper setup by the USER, or sub-standard wireless connection, and anything else BUT the player.
Given that I have gigabit ethernet and a Cisco 300-28P switch and no other device has a networking issue outside of the WD SMP I find that a most curious thing for you to say.
That said, the WD SMP is far superior to its immediate predecessor which remains a complete joke still, after many firmware updates.
But I guess its my fault this is the single device that takes a few minutes to find the server that other devices take a few milliseconds to find. How amusing.
Given that I have gigabit ethernet and a Cisco 300-28P switch and no other device has a networking issue outside of the WD SMP I find that a most curious thing for you to say.
But I guess its my fault this is the single device that takes a few minutes to find the server that other devices take a few milliseconds to find. How amusing.
I guess I should then say, how amusing that you think it isnât your equipment/setupâs fault, since the SMP functions flawlessly in my network (and many other peopleâs), which uses different gear. My file server is found instantly, I can play 60+ Mbps files, etc. If the SMP just doesnât work properly, how is it that it works perfectly for me? Luck?
Mikeâs point is completely valid. There are a large number of reasons why the WD units might not function âproperlyâ within a particular network. People should remember that setting up and maintaining networks is something people train for and get employed to do. It is quite ridiculous then to think that people with little/no knowledge of computer networking should be able to buy a bunch of cheap networking gear, from a range of manufactureres, throw it together, and everything will definitely function flawlessly.
I also didnât suggest the device didnât play large files over the network merely that it takes a disproportionate amount of time to connect to the network the first time after a reboot. Devices running Windows XP, Vista, 7, 8, 8.1 Preview, Mac OS X, Ubuntu and Android donât have this problem.
Perhaps my Cisco 300-28 ~$500 gigabit switch is âtoo cheapâ. Or maybe my expectations are high and yours are not. Or maybe the 802.3ad Dynamic Link Aggregation (dual gigabit) connection to the server is causing mystery issues that donât occur with other devices⊠1,650~ mbps of throughput with 2 or more clientsâŠ
The âgen 2â device was worse, you couldnât even access the network for several minutes after booting the machine and unlike the SMP that sits there running hot whilst âin standbyâ you never got that opportunity with that device. I reported that issue years ago and many firmware updates have come since then.
I think his point was that all his other gear functions OK with his network except his WD player.
Oh I got that. My point was, so what? Meaningless. Computer networking is nothing like, say, your electrical wiring, where if only one appliance doesnât work then you can absolutely definitely know it is that applianceâs fault. Different networking gear can involve different protocols, packet sizes, throughput requirements, Ethernet settings, etc., etc. It is trivially easy to have one network component cripple a different componentâs ability to function on the network. This means that you cannot just automatically assign blame to the one network component that âisnât working right.â In fact, you can easily find many, many cases of postings on this board where people got on blaming their WD units and then later found it was some setting or other hardware in their network that was causing the problems. Finally, if it is the SMP that is âdefective,â as is being claimed, why does it work âperfectlyâ in my network? You donât think this difference could possibly have anything to do with the rest of the components/settings in our respective networks??
I think your version of âperfectâ is merely a lower set of expectations and a higher tolerance for the failings of the device. Donât get me wrong, I enjoy the thing and thatâs why I preserve with the unit â but when a device takes a minute to detect SMB shares, well then the programmer has made some mistakes.
I think your version of âperfectâ is merely a lower set of expectations and a higher tolerance for the failings of the device. Donât get me wrong, I enjoy the thing and thatâs why I preserve with the unit â but when a device takes a minute to detect SMB shares, well then the programmer has made some mistakes.
You are free to believe whatever you want to believe. I was giving you my opinion as a CS PhD/prof with fairly extensive networking experience. Blame whatever you likeâmakes no difference to me. My SMP detects my SMB server and shares instantaneously on my network. (I am done in this thread.)