- WD Community
- News & Assistance
- New to Community
- Forum Feedback
- Software & Apps
- WD Software
- WD Mobile Apps
- Software & Accessory Ideas
- WD TV Live Streaming
- Live Streaming Discussions
- Live Streaming Firmware
- Live Streaming Ideas
- Live Streaming Issues
- WD TV Live Hub
- Hub Discussions
- Hub Firmware
- Hub Themes
- WD TV Live Hub Ideas
- WD TV Live Hub Issue Reporting
- WD TV Play
- WD TV Play
- Live & Live Plus
- Live Discussions
- Live Firmware
- Elements Play
- Elements Play
- External Drives
- Mac Externals
- PC Externals
- Portable Drives
- External Drive Ideas
- Network Devices
- Networking Devices
- Live Duo
- My Book Live
- Other Network Drives
- Network Product Ideas
- Internal Drives
- Desktop & Portable
- Internal Drive Ideas
- Nuevo a La Comunidad
- Los Productos de WD
- Software y Accesorios
- Reproductores Multimedia
- Unidades de Red
- Unidades Externas
- Unidades Internas
- Neu in der Community
- WD Produkte
- WD Programme
- WD TV Media Player
- Netzwerk Laufwerke
- Externe Laufwerke
- Interne Laufwerke
- Annunci e Novita'
- Nuovo per La Comunita'
- Prodotti WD
- Programmi & Accessori
- Riproduttori Multimediali
- Dischi di Rete
- Dischi Esterni
- Dischi Interni
- WD TV Legacy
- Hub Network
- Live Networking
- WD TV HD
- WD TV Mini
- WD Photos
- Other Software & Accessories
- Hard Drives
- WD ShareSpace
- Other Externals
- Other Internal Drives
05-02-2012 11:25 AM
I have a similar error message when i log onto my 2TB WD my book live NAS.
I recently upgraded my mac book pro HD with a complete new install, so thank fully my documents folder were symbollically linked to my NAS.
However, now when i go to log in, i get the same errror:
"The folder “Documents” can’t be opened because you don’t have permission to see its contents."
At first i was a little wierded out by the 'daapd' user. Who the heck was that? the dude who sold me my drive? nope. Cause I did a fresh partition and install of the OS.
BUT I did login remotely via web WD2GO site AND i might add, i can see my documents just fine thank you. But try to connect LOCALLY on my home LAN, nada, nope, no thing...
WD please chime in and help your stranded deciples! before we go Judas on you ; )
05-24-2012 01:30 PM
this is my first post here. Got a 2tb MBL. It works great with win 7 32 and 64 bit. Mac and Ipad.
There does not seem any way to elegantly back up the contents of MBL to an external drive.
All the files are on the MBL, they can be read, added to, deleted, but when it comes to copying them to another external drive the permissions are screwed.
Also I cannot change the permissions or ownership of the files on the MBL.
I think the MBL operating system is Linux so unless you know this you have had it.
I was going to buy another one to mirror the two (I am paranoid about backups) (and rightly so ).
But the MBL would appear to be a low cost central storage for your data you have safely duplicated elsewhere and thats it.
Not a professional answer for storage and backup of mission critical data.
It's good, very good, but could be so much better, I wonder why not........
best of luck all.
06-17-2012 09:36 AM
My first post here too.
Just encoutered this problem and I managed to fix it by logging into the server as a Guest.
• On a Mac I ejected the Public Share.
• Command+K to bring up your Connect to Server Window.
• Enter your server address: e.g. afp://MyBookLive.local
• Click the Guest instead of Registered user login.
I'm guessing logging in as a guest applys the correct permissions. I was able to copy files to my Shared Videos folder after this change. Before, as a registered user, I got the error message about not having the right permisssions.
Hope this helps.
07-08-2012 12:01 AM
I tried the last suggestion and even logging as Guest in my mac but didn't help. I'm running OS X Lion. However, I fixed the problem by enabling SSH through the web interface: http://mybooklivedevicename/UI/ssh, then logging through the terminal into the shares, and apply 777 to all the public folder, this allowed me to modify all my files without any problem anymore.
Hope this helps.
07-08-2012 02:55 PM
Yesterday I purchased a WD My Book Live, and set up a number of folders and today find all folders with a daapd user as the only one with read and wright privileges. In contacted tech support and I was directed to restore the drive but when I ask will this happen again I was advised it was a complicated issue with Apple Lion's operating system and it may occur again????
Does anyone have a solution other than Pako144 setting up SSH and working in the terminal, its just a little above my comfort level after reading the warning.
who is daapd and how do I deleat them as a user.
I hate to restore and have it happen again, I am just not sure I can trust the drive after today.
"Failure to understand the SSH protocol can result in rendering your network server inoperable, as well as allowing unauthorized users access to your network. "
07-08-2012 06:19 PM
I have a wdlive 3tb which has developed the same issue in the past few weeks and it is driving me MENTAL!
Contacted tech support a week ago but still havent heard back.
Everything worked fine in the beginning but suddenly i got denied access to the shared folders (even though they're under Public). I have automatic updates turned on so if it's a firmware issue that might have triggered the change, that might be how it happened. I am now on 02.11.09-053
I have 2 macbooks, one running osx lion 10.7.4 and the other snow leopard 10.6.8 and the issue is identical so i don't think it's Lion's fault...
Also my samsung and LG home theatre systems can still play the files in the shared folders fine.
I never set up any usernames/passwords or the WD2go service, my macs always connect as guest and can still access the folders i created through the Finder but not the default Shared Music/Pictures/Videos
I also have that daapd user with the same permissions as stated previously but can't even connect to the nas with the admin/admin login, even after resetting the drive.
I can't do a quick or full restore either since i can't get the data off to back it up first
Another annoying issue i've had since day 1 is that whenever i click on the Users or Shares tab in the dashboard i get
an internal server error and i am unable to view/add/change any of the relevant content.
If anyone has any ideas or updates on this please post!! Looks like quite a few people on here would be really grateful for it!
07-09-2012 05:14 PM
OK, still haven't found a solution to the account permissions issue but managed to move my files out of the shared folders so at least i can try a quick/full restore now after i back them up.
So for anyone who is in the same predicament; download the movie database program "My Movies Free" from the app store and install. Click on the 'folder import' button up the top, click on 'folder' again in the popup window and navigate to the 'shared videos' folder on your WDlive, which strangely enough displays all the files that i can't access through finder fine?! Now open a regular Finder window and navigate to a folder on the WDlive that you can access or create a new one and just drag the files from My Movies window into your finder et voila...
Hope it helps someone!
07-13-2012 11:40 PM
I've been helping a friend troubleshoot their MBL for a few weeks and found several threads here discussing this same issue. Finally pieced all the information together to come up with a solution that worked.
Symptoms: Friend was using Mac OS X Snow Leopard. Both OS and MBL confirmed on latest software/firmware. Drive that was previously fully accessible ended up with the Public folder accessible but clicking inside it: "The folder “Shared Videos” can’t be opened because you don’t have permission to see its contents." Drive was accessible by opening finder and using smb://drivename.local but not through the normal mac share method.
2. Added ssh to the url: http://drivename.local/UI/ssh
3. Checked the box to turn on ssh
4. Opened a terminal window, connected via ssh using the UI-supplied password
5. Navigated to the public folder. Ownership of the public folder was "root" and group "share". Ownership of the problematic subfolders was "root" and group "root".
6. executed the command "chgrp -R share Public" to change ownership of all files under public to the "share" group.
7. Closed terminal window. Turned ssh back off. Drive behaves normally.
8. Opened beverage of my choice.
Good luck to any who this might help, and to the WD folks who read this and can figure out why the group ownership went wonky in the first place!
07-18-2012 04:28 PM
Pff, so not impressed with WD costumer service! It took them 15 (!!) days to reply and their solution was
a) try and reconnect through the OS (really??)
b) update the firmware (djeez, didnt think of that either)
c) do a full restore (great, that's what i was trying to avoid, duh)
Anyway, by the time i read their email (and the previous post) i had already started the full restore. This eventually solved my dashboard errors and at first sight the permission issues as well (although that daapd is still there). I changed the acces level for 'everyone' and 'staff' to 'read & write" as well instead of 'read only' and started to fill my nas up again. Everything worked fine until this morning when i reconnect after transferring about 1,5TB of files overnight and i can't drop any more cause the folder access has somehow gone back to 'read only'
I'm about to try dbwiddis' solution now but I'm getting stuck on how to connect exactly cause i have no experience with terminal, so can you please explain step 4 a bit more? Thanks so much in advance!
07-18-2012 05:16 PM
WDcat, just replied to your PM but will post general info here for linux savvy.
When you log in via ssh, you are in the user default directory ~
You need to change to where your public directory is. I think (based on memory) that's /DataVolume/shares (case sensitive) so you would, after the login prompt, type:
That should get you to the directory where the Public folder is. You can use ls -al in that directory, and looking at various subdirectories (e.g., ls -al Public) to see what the permissions issue might be. For me, Public had the right user and group, but some of the subdirectories had the wrong group "root" instead of "share".