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…
