Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
    • Posted in
    • Tags

    Accessing Samba Shares using winbind

    Posted on

    I have a RHEL 6 box setup successfully using winbind. I can SSH over to the Linux box and logon using my AD account. I can also see AD users and groups using wbinfo and etc.

    I also have SAMBA up sharing out a directory. I can browse to this server and see the directory share via my Windows 7 workstation however when I click on the share it says "access denied" I cannot figure out why my AD account is getting access denied on this share.

    Below is my global setting and my share config.

    Any help would be appreciated!

    #======================= Global Settings =====================================

    [global]
    #--authconfig--start-line--

    # Generated by authconfig on 2013/11/05 12:07:43
    # DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--)
    # Any modification may be deleted or altered by authconfig in future

    workgroup = myworkgroup
    password server = domain controller
    realm = MYDOMAIN.COM
    security = ads
    idmap config * : backend = tdb
    idmap config * : range = 16777216-33554431
    idmap config MYDOMAIN:backend = rid
    idmap config MYDOMAIN:range = 100000-199999
    idmap config MYDOMAIN:base_rid = 0

    # idmap backend = rid
    # below line a test
    # idmap config * : backend = rid
    template shell = /bin/bash
    winbind use default domain = true
    winbind offline logon = false
    # additional testing - next three lines made no difference
    # winbind separator = +
    # winbind enum users = yes
    # winbind enum groups = yes

    #--authconfig--end-line--

    # ----------------------- Domain Members Options ------------------------
    #
    # Security must be set to domain or ads
    #
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    #
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    #
    # Use password server option only with security = server or if you can't
    # use the DNS to locate Domain Controllers
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *

    security = domain
    passdb backend = tdbsam
    realm = MYDOMAIN.COM

    password server = domaincontroller.mydomain.com

    [testdir]
    path = /testdir
    write list = "MYDOMAIN+Domain Users"
    browseable = yes
    guest ok = yes

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat