Samba Share Access Denied – Fix Access Issues on Windows 10

linux-networkingsambawindows

I'm trying to configure samba to share folders on my network publicly, however I also want private folders. I have ran into a problem where when I create the samba account access to all the shares are denied if your login as a samba user.
I'm connecting from a windows 10 PC
The file system is running Devuan 2.0.0 (a fork of Debian)

Here is what is contained in the samba.conf

[global]
    workgroup = WORKGROUP 
    dns proxy = no
    map to guest = Bad User
    log file = /var/log/samba/log.%m
    max log size = 100
    server role = standalone server
    passdb backend = tdbsam
    obey pam restrictions = yes
    unix password sync = yes
    passwd program = /usr/bin/passwd %u
    pam password change = yes
    map to guest = bad user
    usershare allow guests = yes
    unix extensions = no
    
[Public]
    comment = pubic share
    hosts allow = 1.1.1.100/24, 127.0.0.1
    hosts deny = 0.0.0.0/0
    path = /mnt/Niflheim/Public
    public = yes
    read only = yes
    guest ok = yes
    guest only = no
    
[Private]    
    comment = home share
    hosts allow = 1.1.1.100/24, 127.0.0.1
    hosts deny = 0.0.0.0/0
    path = /mnt/Niflheim/Home
    valid users = USER, @USERGROUP
    read only = no
    browsable = no
    writeable = yes
    writeable list = USER

As an example if I create a samba account called USER and login as that then I can't access any shares but if I don't login all public shares are available.

Best Answer

This just turned out to be a problem with my computer and nothing wrong with the smb share. Their is something wrong with how my computer is communicating with my dns server,

Just fixed it by reinstalling windows

Related Solutions

Linux – Problem connecting to a Samba server with share mode security

I think that you need to re-examine whether share-mode security is what you actually need for this problem. Share mode security means that a password is used to authenticate to a share, not a username/password combination.

If you want to allow multiple users (logging in as themselves) access to modify the files then you need to use user level security.

If you want to allow anybody that knows the magic password to see the share, then share mode security is right for you.

See the Samba Documentation for more information on share level security.

Samba Permissions – I’m going to throw it!

This might help. I do something similar, but only one share is open to the group's users. Other shares are read-only except for a single maintainer user. The [global] section of my smb.conf is almost identical to yours, except I don't use the force create/directory mode directives (in my case, they'd interfere with the other shares).

Here's the share definition:

[shared stuff]
        comment = blah, blah, etc
        path = /path/to/share
        write list = @sambagroup
        force group = +sambagroup
        read only = yes
        directory mask = 0775
        create mask = 0664
        guest ok = yes
        invalid users = root
        case sensitive = True
        default case = lower
        preserve case = yes
        short preserve case = yes

The important stuff here are these:

read only = yes -- by default, read only.
guest ok = yes -- guests can browse.
write list = @sambagroup -- Authenticated members of sambagroup can write.
force group = +sambagroup -- The + means that the force only applies to existing members of sambagroup. They're already the only ones who can write. I think, without the +, guest is given sambagroup credentials, which is not wanted (particularly with the write list directive above).
directory mask = 0775
create mask = 0664

These do exactly what you want yours to do: "drwxrwxr-x" on directories, "rwxrwxr-x" on files, and newly created files are owned by the user and sambagroup. The maintainers of the other shares get the same permissions as everyone else when working in shared stuff, and permissions & groups are normal when they work in the other shares.

My smb.conf has been working with only minor tweaks through several different versions of Samba, and currently is used with Samba 3.2.5. I never had it running on Ubuntu 8.04, but it ran on Ubuntu 7.04 for a long time before getting migrated to a recent Debian Lenny install.

Related Topic