I get the same issue if I turn off the SMP and turn it back on. My media server logs an incorrect username/password coming from the SMP. Go into the setting where it says “clear network credentials” or something like that, then try to access a share and reenter the username and password. Suddenly it works. Seems like the cached credentials are getting corrupted somehow on the SMP. In my case, it works for days just as long as I don’t turn off the SMP.
Pardon me, but that is **bleep**+, not your answer the behaviour of the box!
I was trying to be helpful and tell you what my WD is doing, similar to your report. If you’re going to be rude about it, then this is the last reply you’ll get from me.
Toddler no offense intended on you! Sorry about that. I am just simply angry that I spent about 2 days with this, in the beginning fabulous, but now mad box.
I tried to say that by stating “not your answer the behaviour of the box” I forgot to add: Tanks for your reply!
Fact is that me and as far as I know some other people are facing that kind of problem and having no final solution.
So far till my last post with having C++ uninstalled the box works.
I am continuing to monitor that thing!
If YOU have any other hints they are absolutely welcome!
Oh ja and I am in networks for over 10 years so this things gives me a headache because I tried everything I know for now.
My server here is perfectly running with no clients having problem except this little thing!
To make it more precise. The solution you suggested did not work for me! I cleared all login data still the incorrect usernamen and password. That´s what driving me nuts. I simply wont get any access.
Still running, am getting the feeling that this is related to C++ 1:28 pm, runnning for about 2 hours…
I’ve mentioned this in some other posts, but I’ll mention it here too since we’re in several threads now.
If you’re willing to grab a Wireshark capture of the login problems, I’ll dig into it and file an issue report with WD with the details if I can find anything weird in it…
The Live ID thing was a problem over a year ago, but WD fixed that.  Can’t remember how long ago, but it seems like it was around the end of 2010…
I also had the problem, that I can’t login to my laptop but all works fine with my pc. Both are installed the same way with windows 7. But then I found out, that the problem on the laptop was a longer device-name than 8 characters. I changed the name from janina-pc to janni-pc, then it worked
I also had the problem, that I can’t login to my laptop but all works fine with my pc. Both are installed the same way with windows 7. But then I found out, that the problem on the laptop was a longer device-name than 8 characters. I changed the name from janina-pc to janni-pc, then it worked
THAT is interesting.
SAMBA allows for 15 characters in a system name. The longest I have on my network is 14 characters, and it works.
OKKKAYYY, here we go again, some installer (though I just installed 2 proggies yesterday and updates are off) got me to C++2008 installed on the server, before it was 2005.
Bang today in the morning the usual incorrect password and username.
Deinstalled the C++ again and that second the login worked!
I am doing wireshark today and will psot the results!
I am doing try and error with C++ installed or not!
I’m thinking your issue is quite different than Toddler’s.
Toddler was saying that he can login fine until he shuts the box off, then it doesn’t work when re-powered until he CLEARS the login and tries again, then it will work.
Does yours behave the same way?  … or was yours failing CONSTANTLY?
The IRPStackSize thing is a big issue with Windows 7 Boxes.  I had adjusted my registry for that a while back for a different reason.  It’s all over Google.  :)  It’s most definitely a server-side issue.
No my behaviour is that the box is running but, all of a sudden gets stuck an tells me no media in the folder or is loosing access to the files.
Mi box told me wrong user + pass this morning after beeing shut down over the night, then again after shutting it down manually. So kind of similar to Toddler. Additionally it shut down after a period of time.
Mine isn´t failing constantly but from time to time. The thing is, it is failing from time to time not after 60min or so.
I’d need to see the raw pcap file to know for sure…  But if that’s the case, it’s definitely a server-side problem.  Nothing the WD can do about that.
That’s a VERY early failure; even before the WD sends UserID / Password info.  The WD is asking “What protocol dialect are you expecting so I know how to talk to you?”  The server says “Sorry, I can’t answer.  I don’t have enough memory to figure it out.”
The WD tries twice (in your screencap) and it fails each time, and the WD gives up. Â 4 seconds later, you manually tried again, and got the same error.
After that screen I set the StackSize up to 60, and since then no more error! That could be it!
The weired thing is that the WDTV Live says wrong User and Password not: No connection possible or Error connecting or else!. That´s what confuses me!
They could probably do a better job with error messages.
But basically the SAMBA stack is all that knows what the failure was.  The WD “Application” itself probably just got a “Permission Denied” from the MOUNT request, and that’s enough to throw an error.
It probably uses that same error message regardless of the failure type…
