I can’t access my WDMC via SAMBA

Model: WD My Cloud 3TB
Firmware: 4.01.03-421

A few days ago, after my WDMC reboots, there are something wrong on the Authorization/Authentication of the WDMC.

I can view the share folder and access the contents in my WDMC via the “WD My Cloud App at my Smartphone” normally.

But I can’t view the share folder and can’t access the contents in my WDMC via the “Windows shared folder from PC” or “ES File Explore App. from Smartphone”

Of course I gave the read & write permission to that account to the share folder. But I can’t view the folder icon itself.

To view the folder and access the contents via SAMBA (from PC or ES File Explorer), I should only set the property of share folder to “PUBLIC”.

What Should I do to Fix it?

any error messages?

are you possiably connecting to a public share 1st? always connect to a private share 1st

no need to use public shares 

I assume you tried another reboot? if not,do it

try a system only restore

There was no error message.

Just Empty when i try to access my WDMC via samba as shown in below image.

I tried reboot,  manual firmware update, and  system only restore.

But those doen’t work.

had the same issue…fixed it from this post…

http://community.wd.com/t5/WD-My-Cloud/SAMBA-Deamon-failed/td-p/728978

MY samba restart results are:

ophlicloud:/etc/init.d# ./samba restart
[ok] Stopping Samba daemons: nmbd smbd.
[…] Starting Samba daemons: nmbd smbd9620 (process ID) old priority 0, new priority 0
. ok

My testparm results are:

ophlicloud:/etc/init.d# testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The “idmap uid” option is deprecated
WARNING: The “idmap gid” option is deprecated
WARNING: The “null passwords” option is deprecated
Loaded services file OK.
WARNING: cache directory /var/cache/samba should have permissions 0755 for browsing to work
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        realm = WORKGROUP
        server string = WD My Cloud
        map to guest = Bad User
        null passwords = Yes
        passdb backend = smbpasswd:/etc/samba/smbpasswd
        log file = /var/log/samba/log.smbd
        max log size = 50
        enable core files = No
        max protocol = SMB2
        min receivefile size = 16384
        unix extensions = No
        deadtime = 30
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=2048000 SO_SNDBUF=2048000
        load printers = No
        os level = 5
        preferred master = Auto
        domain master = No
        dns proxy = No
        idmap config * : range = 10000-65000
        idmap config * : backend = tdb
        force group = share
        read only = No
        acl check permissions = No
        create mask = 0775
        force create mode = 0775
        directory mask = 0775
        force directory mode = 0775
        smb encrypt = No
        use sendfile = Yes
        delete veto files = Yes
        veto files = /.nflc_data/.wdmc/.twonky/

And My “overall_share” file is EMPTY!!

If that’s, in fact, the complete output, it’s pretty clear that SAMBA has no SHARES defined – not even PUBLIC.

Between these two lines:

WARNING: The “null passwords” option is deprecated
Loaded services file OK.

… you should see all your SHARES listed.

I would recommend doing a backup of your data, and doing a Quick Restore.

If i set some share folder to “PUBLIC” in the web admin UI,

then Only these folders shown in the “overall_share” files like this:

## BEGIN ## sharename = music #
[music]
path = /shares/music
comment = share not found
public = yes
browseable = yes
writeable = yes
guest ok = yes
map read only = no
## END ##
## BEGIN ## sharename = minso #
[minso]
path = /shares/minso
comment = share not found
public = yes
browseable = yes
writeable = yes
guest ok = yes
map read only = no
## END ##

And I can’t use the “User Access” control in the UI for other share folders (which not set to “PUBLIC”) :

a system only restore will fix the overall_share file and not lose shares and data

Edit:

Also when you re-configure the users and permissions proceede slowly, 1 step at a time and let it finish before the next. it allows you to proceede and stack operations bu does not handle it well

The operation response in the dashboard UI is too slow to endure. So I didn’t wait util an operation completed because the ui seems to work well for the multi-request.
I will try it step by step.