I’ve noticed your “blame anything other than WD” attitude in these forums, and it’s not helpful.
Not true at all. I’ve opened more ISSUE REPORTS than almost any other user. Note that I’m the TOP Kudo’d in the Issue Report section for the SMP, and #3 for the Hub.
When I find problems, I blame WD. When other users can find problems that I can’t reproduce, I’ll still investigate and see if I can find the cause. (See the three Networking bugs I’ve found and reported, that don’t affect me, but do affect other users.) I am the one who troubleshot, found the Samba Bug in the WDTV that cuased failed logins to Windows 7 boxes running Windows Live two years ago, and worked with them to get it fixed.
I’ve been around here long enough to know that in 90% of cases, it *IS* something other than the WD that’s causing problems.
So that accusation up there falls flat.
Look. We both are runing identical client software. We’re running different SERVER software. I am using four different NAS platforms, with two different OS’s, and three different SAMBA builds (on the Linux boxes) and Microsoft CIFS. All told, I have about 25 TB of storage on the wire.
I have *NEVER* had any login issue, on *ANY* WD network platform with the one exception I described a the top of this post.
My QNAP and WD (Linux) NAS boxes, nor my Windows 7 box, have NEVER reported a failed login. EVER… going back almost 2 years and countless upgrades and patches to all the platforms involved.
So, what is your theory that would explain why YOUR WD can’t keep logins straight, but 99% of the other users can? If WD’s consistently munge login attempts, I would expect that EVERYONE would be reporting this.
Short of a hardware problem, or some fairly bizarre firmware interaction, there’s no reason why different boxes would behave differently at the network protocol level. But there are COUNTLESS reasons why the SERVER would behave differently. Especially when people are running SERVER builds of Windows, which has enhanced security policing.
The only way to narrow down the cause if these failed logins would be to get a Wireshark capture of the whole process and compare the Before & After. Since you’re a network engineer (as am I) and a windows expert, that should be a trivial excercise.