Glad to hear that local access is up and running.
Now if I could just find my local user name and password! Ugh!
Glad to know it is working for some! I have managed to enable local storage as the instructions stated and all went well until step 11. Windows file explorer network error âWindows cannot access \MYCLOUD-*****â. I dont get a chance to enter a username or password.
Has anyone got a fix? Help!! Many thanks
Hi @PatO :
Did you signed in web âSign whit local passwordâ before access by File Explorer?
you will find all your passwords in your browser backup. if you are using chrome or ms edge, just open a new tab and search âpasswordsâ. it will be there somewhere.
Iâm back on local access . I am however moving on to google drive for my cloud.
enough of being so dependent on small companies who canât take care of their own security, let alone mine. for all we know our data has been stolen by some 3rd world brigade in EstoniaâŠor Macedonia.
Probably not an issue - - - â But this is CERTAINLY a good time to
- Change all your passwords
- Ensure you have a good data backup.
You might have to reset the drive. this wont delete anything but only reset password
Anyone getting the following error when trying to login via IP address or hostname?
{âkeyâ:ânotFoundâ,âmessageâ:âNot Foundâ}
Have the same problem
It wonât let you IP access.
The only way is to establish local access on the same network, is:
1-Restart the drive
2-Open a browser tab and type http://MYCLOUD-xxxxxx( xxxxxx is your driveâs 6 digit serial number)
3-On the WD discovery page that comes up, turn on the "local Access " button.
4-Set your âlocal access ID and passwordâ which is different to your WD ID and password.
5-Check the drive in your explorer under âNetworkâ , not under drives.
6-You should have local access at the point, unless you want to go ahead and map it as a new drive.
You wonât be able to do this from another network You have to be on the same network as the drive.
Good luck.
That is if you allow google to save your passwords.
I am considering the same. I use Home duo as a local server with mirrored backup. Using it as a backup-only seems to defeat the purpose. But, going for a week without primary files was a great loss of time.
Finally, Back up and running. Now, I will have to consider options as to where to place important files.
I am sure this was hard on WD staff and I appreciate them getting local access back. ButâŠ
Sam, thanks for the help, but that doesnât work for me either. I have fully patched Windows 10 PC/Laptop, and have tried using Chrome, Firefox and Edge.
I can ping itâs IP address successfully across my network, but as soon as I try going to either http://MyCloud-xxxxxx or 192.168.1.x, (where x is allocated by my router and is the only local network I have) I still get that error message -
{âkeyâ:ânotFoundâ,âmessageâ:âNot Foundâ}
I have reset the drive, rebooted both PC and laptop, and turned off VPN. The router recognizes it , so it has to be an issue in the webpage that I am trying to launch.
Thanks
True.
Like I said, I have not decided what to do with my MCH yet, but I will most likely not ever rely on it for retrieval. I will most likely end up using it as a clod backup onlyâŠIF AND WHEN WD decides its a good time to come back onlineâŠOtherwise this thing is gonna have to be used as a local backup which defeats the purpose because I am the last person on the planet to wait to come how so I can consciously back my files up, manually and WD does not offer a choice to automatically back files up when my devices are on my home network.
Very strange, but there is another contributor here who seem to know about networking, more than any of us. Hopefully he/she will see this post and try to help.
Good luck.
Geordie,
âxxxxxxâ should not be anything else other than the serial number of your drive. Did you verify it by looking at the nameplate on the underside of your drive.? Just a thought.
Sam,
Yes, the full serial number is 8 characters, so I have been trying http://MyCloud-last6. Anything else gives me an error that the site cannot be reached, but that gives me the NotFound error message, so it is getting to the drive and trying to run something which just doesnât work, but I donât know what it is
I also brought up File Explorer and was able to map a drive to \MYCLOUD-Last6\Public which is empty. Looks as if this problem has been intermittent since at least 2017, which gives me no faith in the software
Ok, so in my case and before WD came up with this method to turn on âlocal accessâ, I could see the drive under my "network" (I use W11 which is the same as W10 for the most part).
When I opened the drive I could see 2 folders, one is called âPublicâ and the other is called âTimeMachineBackupâ and they were both empty .
After setting up local access (http://mycloud-xxxxxx), I can still see the same 2 empty folders PLUS a 3rd folder called âMyCloudLocalâ which contains all my files.
I installed this drive back in 2020 and since then itâs firmwear has been automatically updated by WD quite a few times and I know they were planning to end support for MCH, this summer before everything went south.
So I am wondering if your MCH was updated with the last firmwear. If all is the same as mine, then you should be able to see at least the aforementioned 2 folders, when you click on its name, under ânetworkâ (Iâm assuming that you are using windows and not iOs).
I originally had one the older MyCloudâs, which stopped being any use when WD moved from OS3 to OS5 (I think it was). This one I have now is a ârefurbishedâ 8TB, which could mean anything, but gives me no clue as to when it was rectified or what version of firmware it is running.
Using Explorer, I do not see it under network, and the only directory of those three I can map to is the public directory; I thus assume that the others are visible only after setting local access on.
I did have recollections of having to enable SMB1.0 in Windows, but that was possibly to do with the two usb drives hanging off my router; I uninstalled that and rebooted, but nothing improved. I also tried installing/uninstalling some of the WD utilities in case it needed something somewhere, but that didnât help.
I understand they are reeling from the recent hack, and believe that because I had had an account for several years, that has probably been compromised. However, they should have had a fully tested/working version of alternative access as part of their disaster recovery procedures. I have put in a support ticket, and maybe they will come up with a viable solution before I lose patience in this and just return it.
Thanks again for the help