Mapped shares disconnect after computer reboot

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

I have followed the instructions at

http://wdc.custhelp.com/app/answers/detail/a_id/10623/session/L3RpbWUvMTQyODYxMDUzMS9zaWQvNENVVnVzam0%3D

to map a network share to my device successfully. The problem is the mapped shares disapear after the sytem is rebooted. I can map a network drive on my local network fine and it is persistant, but not available remotly. I have also tried, with no success, to manually map the shares to the URL that the generated shares use: \wdmycloud-device#######.wd2go.com@SSL

Ideas on how to make these mapped shares persistant?

2

not sure if theres a way to make remote shares persistent

3

Remote mapping is session-based and does not remain connected after the session ends.

4

That honestly makes the device a lot less usable. Is there a way that the shares can be remapped more easily thatn opening a browser window, logging in twice and selecting them?

5

@Angate,

Not really less usable but you need to understand that WD needs to step up security when it comes to remote access else it will not be less usable but useless. Just imagine a normal user login using public terminal and make the share drive persistent but forgot to unmap when they leave?

I’m not siding any sides but if you really know your stuffs and insist on this…see the trick below, note it doesn’t void any warranty as no changes made to your nas.

1) Find out which port your webDav is being mapped on the router from the WD DashBoard settings, usually HTTP(9080) or HTTPS(9443).

2) The tedious part is to find out your username and password. WD substitute them with userid as username and MD5 hash as the password. Think this is in case if your credentials got compromised, at least your actual username/password remain unknown (not hard to figure out though :P). I’ll not explain again, please refer to my old post on how to get the username and password for webdav here: http://community.wd.com/t5/WD-My-Cloud/enable-webdav/m-p/835652/highlight/true#M26331

3) By now you should have known that those hash tags below is your deviceID. Choose either one of the steps below:

a. Just browse from the browser and supply the credentials from point 2 above when prompted (check remember credential as you wish):

https://wdmycloud-device#######.wd2go.com:9443/Public_

b. Map persistently using the console or gui (you can also use URL instead of share paths):

net use * \\wdmycloud-device#######.wd2go.com@SSL@9443\Public_ /persistent /user username *|password

Edited: Or another way is to install OwnCloud which you can map your internal NFS or path or external SFTP/FTP or whatever and assign custom credentials. See my signature for details, but this may void your warranty…

6

I do understand your point about making sure the drive is not mapped on a public terminal. We are setting this up for employees that need access to the drive in a consistent wayb from their work laptops wether they are in the office or out. I will try the method provided, I greatly appreciate your help.

7

setup a seperate VPN connection to your network, map the drive by IP address. this should work with any work resources

Personal opinion the mycloud is not a bad low end device but I would never consider it in a commercial environment, get somthing with better performance and reliability