Re: samba trouble

>> The stop option doesn't appear to work
>> delboy@ladmo:~$ sudo /etc/init.d/samba status
>>    * nmbd is running
>>    * smbd is running
>> delboy@ladmo:~$

>> The reload option seems to work.
>> delboy@ladmo:~$ sudo /etc/init.d/samba reload
>>    * Reloading /etc/samba/smb.conf smbd [ OK ]
>> delboy@ladmo:~$

>> # server string is the equivalent of the NT Description field
>>       server string = %h server (Samba, Ubuntu)

>> # This will prevent nmbd to search for NetBIOS names through DNS.
>>      dns proxy = no

>> # The specific set of interfaces / networks to bind to
>> # This can be either the interface name or an IP address/netmask;
>> # interface names are normally preferred
>>      interfaces = 127.0.0.0/8 eth0

>> # Only bind to the named interfaces and/or networks; you must use the
>> # 'interfaces' option above to use this.
>> # It is recommended that you enable this feature if your Samba machine is
>> # not protected by a firewall or is a firewall itself.  However, this
>> # option cannot handle dynamic or non-broadcast interfaces correctly.
>>      bind interfaces only = yes

>> # This tells Samba to use a separate log file for each machine
>> # that connects
>>      log file = /var/log/samba/log.%m

>> # Cap the size of the individual log files (in KiB).
>>      max log size = 1000

>> # Do something sensible when Samba crashes: mail the admin a backtrace
>>      panic action = /usr/share/samba/panic-action %d

>> # Server role. Defines in which mode Samba will operate. Possible
>> # values are "standalone server", "member server", "classic primary
>> # domain controller", "classic backup domain controller", "active
>> # directory domain controller".
>> #
>> # Most people will want "standalone sever" or "member server".
>> # Running as "active directory domain controller" will require first
>> # running "samba-tool domain provision" to wipe databases and create a
>> # new domain.
>>      server role = standalone server

>> # If you are using encrypted passwords, Samba will need to know what
>> # password database type you are using.
>>      passdb backend = tdbsam

>>      obey pam restrictions = yes

>> # This boolean parameter controls whether Samba attempts to sync the Unix
>> # password with the SMB password when the encrypted SMB password in the
>> # passdb is changed.
>>      unix password sync = yes

>> # For Unix password sync to work on a Debian GNU/Linux system, the following
>> # parameters must be set (thanks to Ian Kahan
>> <<kahan@informatik.tu-muenchen.de> for
>> # sending the correct chat script for the passwd program in Debian Sarge).
>>      passwd program = /usr/bin/passwd %u
>>      passwd chat = *Enter\snew\s*\spassword:* %n\n
>> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

>> # This boolean controls whether PAM will be used for password changes
>> # when requested by an SMB client instead of the program listed in
>> # 'passwd program'. The default is 'no'.
>>      pam password change = yes

>> # This option controls how unsuccessful authentication attempts are mapped
>> # to anonymous connections
>>      map to guest = bad user

>> # Allow users who've been granted usershare privileges to create
>> # public shares, not just authenticated ones
>>      usershare allow guests = yes

>> # Un-comment the following (and tweak the other settings below to suit)
>> # to enable the default home directory shares. This will share each
>> # user's home directory as \\server\username
>> [homes]
>>      comment = Home Directories
>>      browseable = no
>>      writable = yes

>> [printers]
>>      comment = All Printers
>>      browseable = no
>>      path = /var/spool/samba
>>      printable = yes
>>      guest ok = no
>>      read only = yes
>>      create mask = 0700

>> # Windows clients look for this share name as a source of downloadable
>> # printer drivers
>> [print$]
>>      comment = Printer Drivers
>>      path = /var/lib/samba/printers
>>      browseable = yes
>>      read only = yes
>>      guest ok = no
>> # Uncomment to allow remote administration of Windows print drivers.
>> # You may need to replace 'lpadmin' with the name of the group your
>> # admin users are members of.
>> # Please note that you also need to set appropriate Unix permissions
>> # to the drivers directory for these users to have write rights in it
>> ;   write list = root, @lpadmin