search for: admin_shares

...am password change = yes map to guest = bad user include = /etc/samba/smb.conf.%i smb.conf.{SERVICE_IP} [global] interfaces = lo {SERVICE_IP} log file = /var/log/samba/log.%i max log size = 1000 keepalive = 60 deadtime = 10 [ADMIN] comment = Administrative Share path = /srv/ADMIN_SHARES read only = no [SITES] comment = ASchool Website Folders path = /srv/SITES shadow:basedir = /srv/SITES read only = no wide links = yes I was also going to suggest you read this: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs That was until I noticed this: shado...

...n users = @“DOMAIN\Admin” include = /etc/samba/smb.conf.%i smb.conf.{SERVICE_IP} [global] bind interfaces only = yes interfaces = lo {SERVICE_IP} log file = /var/log/samba/log.%i max log size = 1000 keepalive = 60 deadtime = 10 [ADMIN] comment = Administrative Share path = /srv/ADMIN_SHARES valid users = @“DOMAIN\Admin" [SITES] comment = ASchool Website Folders path = /srv/SITES shadow:basedir = /srv/SITES wide links = yes valid users = @“DOMAIN\Group1” sssd.conf [sssd] services = nss, pam config_file_version = 2 domains = DOMAIN.COM debug_level = 0x3ff0 #debug_level...

>> This makes no sense to me. Am I missing something obvious? > You may be, but how can we tell, we cannot see your smb.conf Complete smb.conf below: # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number

Because I'm a masochist, I decided to port my previous (and much older) Samba configuration running a (much older) Slackware implementation to a (much) new server (running Debian Jessie) without actually looking at how to migrate it. Great fun, lots of problems to solve now. The problem of the moment: /var/log/samba/log.smbd tells me it cannot find the domain info in the ldap backend.