Cifs "mount error 13 = Permission denied" CIFS SUCKS - Page 2

kushalkoolwal · 05-12-2008, 07:32 PM

Quote:

Originally Posted by mastfaraz

Solution

Most of people got this Permission Denied access when mounting a
Windows Shared folder

following mounting ->

usually : mount -t cifs //<MachineName>/<Shared Folder> /mnt/Shared -o username=<username>,password=<password>
give you error 13.

correct : mount -t cifs //<MachineName>/<SharedFolder> /mnt/Shared -o username=<DomainName>/<username>,password=<password>

Yes! the only deference is "domain name:<DomainName>" is missing. In case of No Domain try to put your <MachineName> there.
cifs does not locate domain itself (I guess).

This is my first Post on web.

Damn good work man!!! It works

humbletech99 · 05-13-2008, 04:24 AM

I'm absolutely positive that it was not a permissions problem such as just not qualifying the username with the domain, but rather the fact that this was 3 years ago and some samba servers I had didn't support cifs then (they were 2.x series). If you look up, I did mention in the original post that the credentials used were exactly the same in both cases of the smbfs and cifs lines.

kushalkoolwal · 05-13-2008, 05:49 AM

Quote:

Originally Posted by humbletech99

I did mention in the original post that the credentials used were exactly the same in both cases of the smbfs and cifs lines.

I beg to differ. The credentials are not the same. In the solution posted, we are including the "DomainName" whereas you didn't included that.

humbletech99 · 05-13-2008, 05:53 AM

no no, you misunderstand, the original problem was that when passing the exact same credential string the connection would work with smbfs and not cifs. This was due to the older samba servers.

The problem you are describing is in fact a different and trivial problem of you just not qualifying the username with the domain.

send2amitgandhi · 10-01-2008, 08:37 AM

Yes boss superb it is really appropriated, without using Domain name it is creating huge difference here.

Thanks,

-- Amit Gandhi

Quote:

Originally Posted by mastfaraz

Solution

Most of people got this Permission Denied access when mounting a
Windows Shared folder

following mounting ->

usually : mount -t cifs //<MachineName>/<Shared Folder> /mnt/Shared -o username=<username>,password=<password>
give you error 13.

correct : mount -t cifs //<MachineName>/<SharedFolder> /mnt/Shared -o username=<DomainName>/<username>,password=<password>

Yes! the only deference is "domain name:<DomainName>" is missing. In case of No Domain try to put your <MachineName> there.
cifs does not locate domain itself (I guess).

This is my first Post on web.

skeldoy · 10-27-2008, 09:26 AM

Quote:

Originally Posted by humbletech99

actually, you know what, I take it all back, cifs is way way way better than smbfs.
smbfs doesn't complain because it silently fails in many cases. This is worse, because you then find out that what you were doing hasn't worked.
Anyway, I don't have any probs at the moment on this.

I just made the same realization that you did, but this thread didn't help me. I needed to do:
mount.cifs //SERVER/SHARE /mnt/point -o domain=THEDOMAIN,user=user,pass=pass
in order to make it work.. not really sure why DOMAIN\user didn't work. I agree now that it is better than SMBFS, but there should be more specific error-messages. I wasted a couple of hours before I realized that the cifs-mount-command differed from the smbfs and then I used a couple of hours trying different combos to get it working. Really stupid to waste peoples time like this. But I agree that CIFS is looking better than SMB in terms of stability. Still.. Annoying differences are still annoying.

humbletech99 · 10-27-2008, 09:34 AM

Quote:

Originally Posted by skeldoy

not really sure why DOMAIN\user didn't work.

Did you try DOMAIN/user instead?

skeldoy · 10-31-2008, 06:32 AM

Quote:

Originally Posted by humbletech99

Did you try DOMAIN/user instead?

yeah, but for some reason it did not work. I am starting to wonder if there is something weird with my character-set that prevents the / from being interpreted such by the mount.cifs, but I cannot find anything like that in the code. Can anyone confirm that DOMAIN/user is working or is it DOMAIN//user or DOMAIN\\user or DOMAIN\user?

humbletech99 · 10-31-2008, 06:42 AM

DOMAIN/user works for me.

So does DOMAIN\\user and just "user" when using smbclient.DOMAIN\user will not work because of shell escaping.

djbon2112 · 12-25-2008, 10:57 AM

EDIT: Sorry, I actually managed to post in the wrong thread >.<

caverdave · 10-29-2009, 12:24 PM

I was having this problem too. I was trying to connect to a Windows XP Pro share as my local username. But I was using the company domain:

mount.cifs -t smbfs //<machine>/<share> /mnt/<dir> -o username=<user>,domain=<xxx.com>

When I changed it to
mount.cifs -t smbfs //<machine>/<share> /mnt/<dir> -o username=<user>,domain=<machine>

it worked.

I was doing it the first way in a slightly older version of Samba and it worked fine, which was frustrating.

erhhung · 11-03-2009, 06:56 AM

I followed the directions at:

http://lists.olug.org/pipermail/olug...er/015520.html

which says pretty much exactly what's been said here. I finally found out why I got the mount error 13 problem using cifs and an external credentials file. This is my entry in /etc/fstab:

//denali/music /mnt/denali/music cifs nosuid,nodev,noexec,credentials=/etc/samba/auth.smb,uid=500,gid=500,file_mode=0664,dir_mode=0755 0 0

The file /etc/samba/auth.smb contains only 2 lines:

username=foo
password=bar

But the key thing is that this file must not contain any extra white space before or after those 2 lines, i.e., the file should end right after the last password character without a newline! I had a newline and it caused the error. I had tried adding the domain name prefix to the username and that didn't help. Perhaps smbfs is more forgiving about how it reads credentials, but cifs should not be so picky, but it is.

Hope this helps.