Toddler wrote:
"An audit failure does not indicate a “problem” with the WDTV. All the WDTV is doing is logging in using cached credentials.
The audit failure event indicates your server denied the login, most likely due to a policy you’re enforcing on the server."
I’ve noticed your “blame anything other than WD” attitude in these forums, and it’s not helpful.
An audit failure in this case does indicate a “problem” with the WD TV Live, and I’ll make this really simple. Changing nothing at all on the server side, the WD cannot connect after it restarts. The server logs the following:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d Sub Status: 0xc0000064
Process Information: Caller Process ID: 0x0
Workstation Name: WDTVLIVE
Source Network Address: 192.168.1.124
Source Port: 49655
Again, changing nothing on the server side, if I clear and reenter the credentials on the WD TV Live, it immediately works. It’s not a policy on the server side. I’m a network engineer and Windows deployment expert. I know how to read a log file. I didn’t go into that level of detail because I didn’t expect to be asked for proof, but there you have it.
The WD TV Live should be logging in with cached credentials, but in my case, the credentials it is using after a restart seem to be incorrect. Obviously, the server will not log those credentials for security purposes, but maybe the WD engineers can provide a way to check those credentials on the WD TV Live side and see what is going wrong or what changes when I reenter them.
The info above was with the 1.05.18 firmware. I upgraded to the 1.06.04 firmware this morning, and it changed the behavior slightly.
On the 1.06.04 firmware, I can now put the SMP in standby (quick press of the power button) without having to reenter my credentials at startup. If I power off the SMP (three-second press of the power button), the server logs “unknown user name or bad password” at startup, and my shares are inaccessible until I reenter my credentials. On the 1.05.18 firmware, both standby and power off modes produced “unknown user name or bad password” and required me to reenter my credentials.
The engineers must have changed something in this firmware to have fixed standby, but power cycle is still problematic. As with the previous behavior, I can reproduce this at will.