Just bought a WD MY Cloud (2TB). I installed it according to the instructions using my laptop with windows 7, got some error message during installation that file sharing was not possible (?), continued anyway. When done I can access the device, manage users, repositories etc but i can’t get it to show up in the Explorer. I can access it from my Android device, and when i started up another laptop (all on the same home network) it automatically detected MY Cloud and installed drivers so that i could access the folders using the normal file browser. This laptop runs Vista.
I have tried to uninstall, reboot and install again, the explorer finds the MYCloud both as storage device and MediaPlayer, but when i click the storage device nothing happens (the icons looks “strange” as well, i.e. not the same as on the Vista machine)
When using the ip number (in a browser), i will get directed to the web interface (192.x.x.x/UI) of the unit, this works perfectly fine, i can administer the setup, change settings, add and change users, see the resources and so on. I can also use SW from WD (“WD My Cloud”) to access the files, but I what I want is to be able to browse and access the files through the normal file explorer, this I can’t get to work.
I have tried to search and add My Cloud as network drive but when entering the IP, i get an error code and a message stating that the path cannot be found. Any ideas?
I works fine on the other computer (WIN XP)
I have a suspicion I do know what this is. The root cause is something by design is that one computing device can not sign-on to one server more than once at one time.
Let’s set the scene . . .
On the My Cloud the Public share is always accessible even if when the client (in this case the version of the Windows operating system [that you’ve not yet revealed]) sends a user-name that NAS does not know about. In that case the client is signed in as a guest. When that happens then you won’t be able to sign in using a valid user-name and password until you sign-out of the guest connection.
I think what Windows does is give an error message not related to the actual issue.
Someone else has a similar fault but here what it was is the ZoneAlarm firewall was blocking he computer’s access to NAS.
Also, is the Workstation service on your computer enabled and operational.
Anyway, what happens if you try these two commands on the command prompt. Use the IP address of your NAS on your LAN.
What happens? If there are error messages, what are those messages.
I have Windows 7 Home Premium (service pack 1) on the laptop
Thanks a lot for the help, when using the first command it says “Empty list” (translated from Swedish)
when using second command with IP of WD MY Cloud (on the same WLAN), i get (again translated from Swedish):
‘System error 53 has occured’
‘The network path cannot be found’
Ok. So it’s not an authentication issue. You may have already performed this. If so try again.
Shut-down the My Cloud fully then power-up the NAS, Give it time to fully start (should be less than 10 minutes, but give it 10 minutes) and try again. Sometimes it’s not the NAS that’s at fault, but the computer. If I had a machine with the same fault I could try and diagnose the issue as I do also have a My Cloud NAS, but now on Windows 10 Pro.
Have to think about this one. Maybe someone else on this community has a solution or ideas?
Good point, should not matter. I’ve had computers configured for a different workgroup and on Windows XP and Windows 7, never had a problem accessing the NAS by name. This is like the computer simply can’t see the SAMBA server on the My Cloud. Thomas tried to access the My Cloud’s Samba server by IP address and that eliminates NetBIOS name resolution from the problem.
It mattered on the Windows 7 PC I was using to try to connect to my drives yesterday. With the wrong workgroup name on the PC, it couldn’t see the drives. As soon as I set the workgroup to that used by my network, it found the drives and would connect to them by name.
I’ve tried some of the scenarios you described and I can’t get mine to fail to talk to the Samba server in the My Cloud. I changed the workgroup name in the NAS and also on the computer. The computer could still find the NAS. Always finds the NAS when using the IP address.
I’ve had the error you’ve described when I try access a NAS very soon after I start the computer. Once it discovers what’s on the network then it all recovers.
I tried to change workgroup name and restart but the behaviour is the same. I can still see MYCloud as a “storage device”, but when trying to open or access it still nothing happens
Free translation from Swedish:
“You can continue the installation but you may not be able to:
x Copy files to and from the unit
x Browse the shared folders of the unit
x Map a shared folder”
I suspect this is related to the error i see, but I don’t know what to do about it
I never used the set-up program. The problem everyone’s got is not know the exact configuration of your computer.
Something to try. Start your computer in Save mode with networking support and try access the My Cloud. Safe mode will just start Windows with just that’s necessary for the operating system to function and with networking.
Obviously not all that is in the article does not apply to the My Cloud NAS. The individual who asked for help is having the same problem, but trying to access another Windows computer.
I have a feeling that it may be something on your computer and not an issue with the WD My Cloud
Need to be tried with the OS started in safe mode with networking before it’s possible to proceed. to find out if it’s some other software interfering.
