I am getting the same problem. The suggested thread is far from a concise solution. What I have found is that you can turn on the public access and the problem goes away. This is far from an optimal solution as well. Even more confusing in this thread the exact opposite fix is reported:
A good solution would be for WD to fix the problem, let everyone know that it is fixed and then provide a simple and concise set of instructions on how to use the solution. It would by nice if WD would weigh in here. References to this issue go back at least to 2012.
