Potential shares issue?

So, I’ll apologise upfront due to a limited lack of technical terminology regarding the WD my cloud, so please do correct me if i’m referring to something incorrectly.

I have a WD 3TB my cloud on: v04.04.02-105. The main use for this is the storing of video files which I can then stream using my WD TV media player.

Quite some time ago I underwent an upgrade to the firm ware, and since then I have been having issues viewing certain files. I can still see and access my cloud using my media player, but my previous files had vanished. I checked my dashboard, and the memory/storage stayed at the same level, so I understood this was potentially a permissions problem.

I added a new file to the cloud, this one file could now be viewed from my media device, but nothing else.Using my laptop, i then went to investigate further. My cloud is still listed as a Network device:

and when i go in via here, I can see all of my original folders. However, I do not seem to be able to adjust them or view the properties of them in any way:

The shares on my dashboard for these are all currently set to public, essentially to test that I can find them.

If I access my cloud via run/my network, files do appear there and show, the ability to view properties etc, but just not the folders with all my data in from before, the ones mentioned above.

If anyone has any ideas as to if I’ve set something up wrong, configured something incorrectly or just need to adjust something, if you could give me a heads up, that would be great, as I am at a loose end here and have run out of options.

Additionally, if anyone needs me to provide more info, just give me a shout.

Cheers,

If you look at the icon you are clicking on, it looks like a picture of the Lou-cloud with symbols representing media files.
You are accessing the media server folders. You cannot modify the media server folder from this area.
Look lower in your network browser. You should see the icon for Lou-cloud under network storage without the symbols for media types. You can modify your folders and files using this icon and not the media server icon.

1 Like

What I mean by network browser, don’t look under “this-PC” look under network from the links on the left column.

Look for and open the My Cloud entry under Computer when using Windows File Explorer.

What you should do is map the Share from the My Cloud to your PC. See the following link or read the My Cloud User Guide which explains how to map the My Cloud.

http://support.wdc.com/KnowledgeBase/answer.aspx?ID=2676

My Cloud User Manual: http://www.wdc.com/wdproducts/library/?id=439&type=25

Hi,

Thanks both for the help so far, much appreciated.

My initial screen shots I posted as I was trying to illustrate that my cloud was already mapped to my computer; it’s here were I can go and access my cloud as of now, but it does not have my previous device information contained within it. Here We can see that my original cloud seems to be mapped correctly, but I can not adjust any of the information within it.

Based on your past points though, i have just recognised something. If I double click into the the WD network location that says Lou-cloud, the icon in windows explorer changes to the media icon. I’m not sure how I could go about adjusting this mapping? The only mapping I have been able to successfully do is to my cloud in it’s current state without any of my past data, as shown on the right hand side of my above screen shot.

Additionally, just to show my actual network, I can see my cloud listed as both a media device and storage. Clicking on these (as you probably know) take me to either the Twonky server - which i had no previous/current knowledge of, and to my dashboard:

Sorry if I am missing something blatantly obvious, I’m just trying to desperatley wrap my head around what may have gone wrong and how I can fix it in the quickest easiest fashion.

Again, thanks for the help so far, hope someone will be able to shed some further light.

Cheers.

Are you using Windows 10? If so ensure its updated with the latest Microsoft updates. There was an update in March that fixed the issue of the NAS devices like the My Cloud not showing up under Computer. Sometimes some have to hit the refresh button on Windows File Explorer to have it properly populate the entries under the Computer section in Windows File Explorer.

The “Lou-cloud” entry under Network Locations, the one that is different than the mapped Shares, is being shown because Windows File Explorer in Windows 10 is displaying the Twonky Media Server connection embedded within the My Cloud. In other words Windows File Explorer is acting as a DLNA client and allowing one to access the DLNA media server (Twonky) on the My Cloud to stream any media content cataloged by the media server.

If one is having trouble with mapped Shares then try disconnecting/removing the mapped share and recreate the mapped share. Sometimes that fixes strange issues with mapped shares. Same goes for the “Lou-cloud” entry, try removing it then hit Windows File Explorer refresh and see if it is recreated and accessible.

Edit to add: If one removes the media server under Network Locations they can re-add it via the “Access media” button on Windows File Explorer menu while they have “This PC” selected.

That doesn’t appear to be a drive mapping: it is showing you the Twonky media server as a network location, I think.

You two mapped drives, Z: and V: are showing as networked file server storage devices.

I’m assuming in your second picture, that ‘Twonky server’ and ‘Dashboard’ both open up web browsers with the UIs for the Twonky media server, and MyCloud Dashboard.

I get the impression that Windows sometimes tries to be too ‘helpful’ in what it displays, trying to isolate the user from what’s going on underneath (Apple style). But only succeeding in presenting a rather confusing picture… It would be nice if it had a better image for the DLNA media server, but that WD icon is the one presented by Twonky to DLNA clients, to identify the library.

Thanks everyone for the help.

It seems the classic IT scenario of ‘turning it off and on again’ seems to have helped overall.