Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I have a home server with samba. with windows i can access and make folder(always with permission 777) like guest( no password ) without problem. But with linux, when i mkdir i can not modify this folder again. i lose already 5h to try to fix this please help me

mount my share:

sudo mount -t cifs -o guest //192.168.1.100/3TB /mnt/3TB

ls -al /mnt/3TB

drwxrwxrwx 16 root root    0 15 apr 18.55 3TB

mkdir test && cd test && ls -al

drwxr-xr-x  2 65534 65534 0 15 apr 19.13 .
drwxrwxrwx 17 root  root  0 15 apr 19.13 ..

65534 is the id for user nobody

AND HERE THE PROBLEM: mkdir test2 PERMISSION DENIED

testparm

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[2TB]"
Processing section "[3TB]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        workgroup = SAMBA
        server string = %h server (Samba, Ubuntu)
        map to guest = Bad Password
        obey pam restrictions = Yes
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        usershare allow guests = Yes
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb

[2TB]
        comment = 2TB
        path = /mnt/2TB
        read only = No
        guest ok = Yes

[3TB]
        comment = 3TB
        path = /mnt/3TB
        read only = No
        create mask = 0777
        directory mask = 0777
        guest ok = Yes

EDIT: seems working if i mount with this argv: operm

Client does not do permission checks. This can expose files on this mount to access by other users on the local client system. It is typically only needed when the server supports the CIFS Unix Extensions but the UIDs/GIDs on the client and server system do not match closely enough to allow access by the user doing the mount. Note that this does not affect the normal ACL check on the target machine done by the server software (of the server ACL against the user name provided at mount time).
share|improve this question
add comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.