# required a share to be setup on the samba server (see # profile directory from the client point of view) The following # It specifies the location of the user's # classic domain controller', 'server role = backup domain controller' # The following settings only takes effect if 'server role = primary # This option controls how unsuccessful authentication attempts are mapped # when requested by an SMB client instead of the program listed in # This boolean controls whether PAM will be used for password changes Passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*. # sending the correct chat script for the passwd program in Debian Sarge). # parameters must be set (thanks to Ian Kahan for # For Unix password sync to work on a Debian GNU/Linux system, the following # password with the SMB password when the encrypted SMB password in the # This boolean parameter controls whether Samba attempts to sync the Unix ![]() # If you are using encrypted passwords, Samba will need to know what # running "samba-tool domain provision" to wipe databases and create a # Running as "active directory domain controller" will require first # Most people will want "standalone sever" or "member server". # domain controller", "classic backup domain controller", "active # values are "standalone server", "member server", "classic primary Defines in which mode Samba will operate. Panic action = /usr/share/samba/panic-action %d # Do something sensible when Samba crashes: mail the admin a backtrace # through syslog you should set the following parameter to something higher. # We want Samba to log a minimum amount of information to syslog. # If you want Samba to only log through syslog then set the following # Cap the size of the individual log files (in KiB). # This tells Samba to use a separate log file for each machine ![]() # option cannot handle dynamic or non-broadcast interfaces correctly. # not protected by a firewall or is a firewall itself. # It is recommended that you enable this feature if your Samba machine is # Only bind to the named interfaces and/or networks you must use the # This can be either the interface name or an IP address/netmask # The specific set of interfaces / networks to bind to # This will prevent nmbd to search for NetBIOS names through DNS. # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both # WINS Server - Tells the NMBD components of Samba to be a WINS Client # WINS Support - Tells the NMBD component of Samba to enable its WINS Server # Windows Internet Name Serving Support Section: Server string = %h server (Samba, Ubuntu) # server string is the equivalent of the NT Description field # Change this to the workgroup/NT-domain name your Samba server will part of Samba is version 4.11.Īlso, make sure you have avahi working, TM doesn't work for me without it. Howdy, I haven't seen your issue, but happy to share my working smb.conf. None of the guides I read mentioned having to download the vfs modules for Samba, but I've done this. Has anyone had this issue and could offer some advice about how to get this working? I've rolled back to my previous config so I don't have my last smb.conf but as an example of what I have tried, I took the config from this thread in it's entirety, changing only the share path and user and it still failed in the exact same way. ![]() I tried many configs following the advice of others with similar problems (error 13 when trying to mount after the initial backup) but none of the suggestions have worked so far. So the existence of the backup is the root problem. If I delete the sparsebundle containing the backup I can be mounted fine again. But if I try to mount the Time Machine folder it disappears. If I connect to the server in Finder with the correct login I can see the shares so authentication is working. I can create the initial backup no problem (from a Sierra machine) but subsequent backups fail instantly with an error that the backup disk isn't available. While the setup went fine I have this issue that I can't seem to fix. As Samba now has support for TM I wanted to see if I could switch to using it for both my Windows and Mac backups so I could retire Netatalk. I've been running netatalk on my T50 for the last few years for Time Machine backups.
0 Comments
Leave a Reply. |