After Update To 2.2.8, No CIFS Shares Accessable

Hi Paul

By chance, were you able to get it going with AD integration?

I followed your instructions and it worked fine logging as ‘admin’

However, I cannot  connect to the device or any share using an AD user account.

Winbind seems to be OK, using getent passwd, etc.

I disjoined the device and joined the domain again. No difference.

Any help would be greatly appreciated

Cheers

I don’t know about anyone else but I dealt with this issue for a couple hours today and was about to throw my WDShareSpace out the window before I realized that the permissions were messed up on my shared foldes after I upgraded my firmware.  I SSH’d into the WDShareSpace, issued a ‘su’ command using my password and navigated to my shared folders ‘cd /shares’.

Upon doing a quick check, my shares were reporting drwxrwxr-x.

So I did a quick chmod 777 on my share to test with, mounted the share, tried to write a new file there and it worked just fine using either the built in accounts or my Domain Accounts (which was the issue).  Problem solved.

But what about all the subdirectories and files?  You have to set the permissions on them individually.  I guess this is going to depend on what you have on yours, with mine it is simply pictures so two quick commands fixed me.

find . -type d -exec chmod 777 "{}" ;

and

find . -type f -exec chmod 666 "{}" ;

Of course your second command may vary and you may have to add additional arguments to different file types.  Sorry this might not be an idea fix for everyone, but it worked for me.

I don’t know about anyone else but I dealt with this issue for a couple hours today and was about to throw my WDShareSpace out the window before I realized that the permissions were messed up on my shared foldes after I upgraded my firmware.  I SSH’d into the WDShareSpace, issued a ‘su’ command using my password and navigated to my shared folders ‘cd /shares’.

Upon doing a quick check, my shares were reporting drwxrwxr-x.

So I did a quick chmod 777 on my share to test with, mounted the share, tried to write a new file there and it worked just fine using either the built in accounts or my Domain Accounts (which was the issue).  Problem solved.

But what about all the subdirectories and files?  You have to set the permissions on them individually.  I guess this is going to depend on what you have on yours, with mine it is simply pictures so two quick commands fixed me.

find . -type d -exec chmod 777 "{}" ;

and

find . -type f -exec chmod 666 "{}" ;

Of course your second command may vary and you may have to add additional arguments to different file types.  Sorry this might not be an idea fix for everyone, but it worked for me.