CentOS cifs mount point fails after reboot. permission denied error 13

centoscifsmountsamba

I'm using CentOS release 5.10
I have a mount point setup in /etc/fstab that was working, but now it doesn't. After a reboot the mount point doesn't exist and running sudo mount -a results in:
mount error 13 = Permission denied

The entry in my fstab looks like this:

//my.server/my\040Folder/MY\040SUBFOLDER/other\040folder       /var/ftp/virtual_users/myfolder cifs username=mydomain\134myuser,password=mypassword  1 1

I've tried mounting manually in the command line using this:

$ sudo mount -t cifs "//my.server/my Folder/MY SUBFOLDER/other folder"   /var/ftp/virtual_users/myfolder --verbose  -o username=myuser,password=mypassword,domain=mydomain

My result is:
mount.cifs kernel mount options: unc=//my.server\my Folder,ip=192.168.150.100,ver=1,rw,username=myuser,domain=mydomain,prefixpath=MY SUBFOLDER/other folder,pass=********

mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

I can successfully log in with smbclient:

$ smbclient "//my.server/my Folder" -U myuser -W mydomain

and from there I can cd into the MY "SUBFOLDER/other folder" directory.

After much google searching, many fixes involved setting the Security mode. I tried ntlm,ntlmi,ntlmv2,ntlmv2i but none of the options changed the output.

There is a mount entry for another folder on this same server, which is working, but it doesn't go down to a sub folder:

//my.server/other /var/ftp/virtual_users/other cifs username=mydomain\134myuser,password=mypassword,nobrl,noperm  1 1

I also tried adding the noperm and nobrl options to my problem mount, but no changes.

The System Admin of the windows server (my.server) verified that myuser has full control of all the folders I'm trying to access.

Best Answer

While I was not able to resolve the situation completely, I discovered I was able to mount the share by itself:

//my.server/my Folder

It was the prefix path that was causing the issue. This worked without any modifications to the parameters or user. Why this worked before with the full path and no longer works now is something I'd love some insight on.

From there I modified the process that uses that mount location, and changed the root directory from '/' to '/MY SUBFOLDER/other folder/' and everything worked from there.