Results 1 to 7 of 7

Thread: Samba Share for Windows Backup

  1. #1
    Join Date
    Jun 2007
    Beans
    41

    Samba Share for Windows Backup

    I've been working on this for a couple hours and can't get it to work. I'm running 12.04 server and installed Webmin (slick). My goal is to create a shared directory in /home/backups/machine backups/ (with the 's' in backups as not to bother the built-in 'backup' user). I'll create folders for each of my other machines in that directory and back up my machines there.

    All is well up to the point of authentication from other machines. I've read tutorial-after-tutorial and can't get write access to the folder. I'd like that share to be writeable by all three machines (1xWin7, 2xMacOS), either by IP address or by putting in credentials for the backups user. I'm open to other suggestions here, but don't want just anyone that visits my network to have access.

    Right now I can browse the folders inside the 'machine backups' folder, but have no write permissions. Permissions are 755, so I assume I have to somehow map my windows user to an Ubuntu or Samba user (those are already converted). But, I may be incorrect there.

    I'm sure this is simple and I'm misunderstanding the tutorials or am just a moron. Either way, can someone help me out?

  2. #2
    ahallubuntu is offline Chocolate-Covered Ubuntu Beans
    Join Date
    Jul 2005
    Beans
    2,050

    Re: Samba Share for Windows Backup

    ~
    Last edited by ahallubuntu; July 3rd, 2013 at 02:24 AM.

  3. #3
    Join Date
    Jun 2007
    Beans
    41

    Re: Samba Share for Windows Backup

    EDIT 1: Never mind the following. I got it. I had to download PSCP and do it from the command prompt.

    EDIT 2: Well, I have it and you can still ignore the next paragraph, but it's just one long line of text. There has to be a better way for me to get this to you.

    I just realized I don't know how to download the file. I have it open in pico through putty, but don't know how to get the file to my Windows box. After that, I'll be glad to oblige. I'd really like to learn to do this through Webmin, but realize seeing the file will show what's going on. So, how do I retrieve it? (sorry for the noobish question)
    Last edited by beengone; February 4th, 2013 at 06:34 AM.

  4. #4
    Join Date
    Jun 2007
    Beans
    41

    Re: Samba Share for Windows Backup

    Got it. Just had to open in a different editor. At this point I'm able to create a folder inside /machine backups, but no inside folders within that folder. Also, you'll note that it's set to access from only one machine and that I've tried to map users. Progress, but now I'm afraid I'm leaving a lot open I shouldn't (and i still can't get it working). Doh. I won't touch the options until I hear back so we're not shooting at a moving target. Back at it tomorrow.... Thank you!

    Code:
    #
    # 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 of configurable options most of which 
    # are not shown in this example
    #
    # Some options that are often worth tuning have been included as
    # commented-out examples in this file.
    #  - When such options are commented with ";", the proposed setting
    #    differs from the default Samba behaviour
    #  - When commented with "#", the proposed setting is the default
    #    behaviour of Samba but the option is considered important
    #    enough to be mentioned here
    #
    # NOTE: Whenever you modify this file you should run the command
    # "testparm" to check that you have not made any basic syntactic 
    # errors. 
    # A well-established practice is to name the original file
    # "smb.conf.master" and create the "real" config file with
    # testparm -s smb.conf.master >smb.conf
    # This minimizes the size of the really used smb.conf file
    # which, according to the Samba Team, impacts performance
    # However, use this with caution if your smb.conf file contains nested
    # "include" statements. See Debian bug #483187 for a case
    # where using a master file is not a good idea.
    #
    
    #======================= Global Settings =======================
    
    [global]
    	log file = /var/log/samba/log.%m
    	protocol = NT1
    	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    	obey pam restrictions = yes
    	username map = /etc/samba/user.map
    	map to guest = bad user
    	encrypt passwords = yes
    	passwd program = /usr/bin/passwd %u
    	passdb backend = tdbsam
    	dns proxy = no
    	netbios name = ubuntu
    	server string = %h server (Samba, Ubuntu)
    	unix password sync = yes
    	workgroup = WORKGROUP
    	os level = 20
    	security = user
    	syslog = 0
    	usershare allow guests = yes
    	panic action = /usr/share/samba/panic-action %d
    	max log size = 1000
    	pam password change = yes
    
    ## Browsing/Identification ###
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    
    # server string is the equivalent of the NT Description field
    
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable its WINS Server
    #   wins support = no
    
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ;   wins server = w.x.y.z
    
    # This will prevent nmbd to search for NetBIOS names through DNS.
    
    # What naming service and in what order should we use to resolve host names
    # to IP addresses
    ;   name resolve order = lmhosts host wins bcast
    
    #### Networking ####
    
    # 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
    
    
    
    #### Debugging/Accounting ####
    
    # This tells Samba to use a separate log file for each machine
    # that connects
    
    # Cap the size of the individual log files (in KiB).
    
    # If you want Samba to only log through syslog then set the following
    # parameter to 'yes'.
    #   syslog only = no
    
    # We want Samba to log a minimum amount of information to syslog. Everything
    # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
    # through syslog you should set the following parameter to something higher.
    
    # Do something sensible when Samba crashes: mail the admin a backtrace
    
    
    ####### Authentication #######
    
    # "security = user" is always a good idea. This will require a Unix account
    # in this server for every user accessing the server. See
    # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
    # in the samba-doc package for details.
    #   security = user
    
    # You may wish to use password encryption.  See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
    
    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.  
    
    
    # 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.
    
    # 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).
    
    # 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'.
    
    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    
    ########## Domains ###########
    
    # Is this machine able to authenticate users. Both PDC and BDC
    # must have this setting enabled. If you are the BDC you must
    # change the 'domain master' setting to no
    #
    ;   domain logons = yes
    #
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of the user's profile directory
    # from the client point of view)
    # The following required a [profiles] share to be setup on the
    # samba server (see below)
    ;   logon path = \\%N\profiles\%U
    # Another common choice is storing the profile in the user's home directory
    # (this is Samba's default)
    #   logon path = \\%N\%U\profile
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of a user's home directory (from the client
    # point of view)
    ;   logon drive = H:
    #   logon home = \\%N\%U
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the script to run during logon. The script must be stored
    # in the [netlogon] share
    # NOTE: Must be store in 'DOS' file format convention
    ;   logon script = logon.cmd
    
    # This allows Unix users to be created on the domain controller via the SAMR
    # RPC pipe.  The example command creates a user account with a disabled Unix
    # password; please adapt to your needs
    ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
    
    # This allows machine accounts to be created on the domain controller via the 
    # SAMR RPC pipe.  
    # The following assumes a "machines" group exists on the system
    ; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
    
    # This allows Unix groups to be created on the domain controller via the SAMR
    # RPC pipe.  
    ; add group script = /usr/sbin/addgroup --force-badname %g
    
    ########## Printing ##########
    
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    #   load printers = yes
    
    # lpr(ng) printing. You may wish to override the location of the
    # printcap file
    ;   printing = bsd
    ;   printcap name = /etc/printcap
    
    # CUPS printing.  See also the cupsaddsmb(8) manpage in the
    # cupsys-client package.
    ;   printing = cups
    ;   printcap name = cups
    
    ############ Misc ############
    
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    ;   include = /home/samba/etc/smb.conf.%m
    
    # Most people will find that this option gives better performance.
    # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
    # for details
    # You may want to add the following on a Linux system:
    #         SO_RCVBUF=8192 SO_SNDBUF=8192
    #   socket options = TCP_NODELAY
    
    # The following parameter is useful only if you have the linpopup package
    # installed. The samba maintainer and the linpopup maintainer are
    # working to ease installation and configuration of linpopup and samba.
    ;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
    
    # Domain Master specifies Samba to be the Domain Master Browser. If this
    # machine will be configured as a BDC (a secondary logon server), you
    # must set this to 'no'; otherwise, the default behavior is recommended.
    #   domain master = auto
    
    # Some defaults for winbind (make sure you're not using the ranges
    # for something else.)
    ;   idmap uid = 10000-20000
    ;   idmap gid = 10000-20000
    ;   template shell = /bin/bash
    
    # The following was the default behaviour in sarge,
    # but samba upstream reverted the default because it might induce
    # performance issues in large organizations.
    # See Debian bug #368251 for some of the consequences of *not*
    # having this setting and smb.conf(5) for details.
    ;   winbind enum groups = yes
    ;   winbind enum users = yes
    
    # Setup usershare options to enable non-root users to share folders
    # with the net usershare command.
    
    # Maximum number of usershare. 0 (default) means that usershare is disabled.
    ;   usershare max shares = 100
    
    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    
    #======================= Share Definitions =======================
    
    # 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 director as \\server\username
    ;[homes]
    ;   comment = Home Directories
    ;   browseable = no
    
    # By default, the home directories are exported read-only. Change the
    # next parameter to 'no' if you want to be able to write to them.
    ;   read only = yes
    
    # File creation mask is set to 0700 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0775.
    ;   create mask = 0700
    
    # Directory creation mask is set to 0700 for security reasons. If you want to
    # create dirs. with group=rw permissions, set next parameter to 0775.
    ;   directory mask = 0700
    
    # By default, \\server\username shares can be connected to by anyone
    # with access to the samba server. Un-comment the following parameter
    # to make sure that only "username" can connect to \\server\username
    # The following parameter makes sure that only "username" can connect
    #
    # This might need tweaking when using external authentication schemes
    ;   valid users = %S
    
    # Un-comment the following and create the netlogon directory for Domain Logons
    # (you need to configure Samba to act as a domain controller too.)
    ;[netlogon]
    ;   comment = Network Logon Service
    ;   path = /home/samba/netlogon
    ;   guest ok = yes
    ;   read only = yes
    
    # Un-comment the following and create the profiles directory to store
    # users profiles (see the "logon path" option above)
    # (you need to configure Samba to act as a domain controller too.)
    # The path below should be writable by all users so that their
    # profile directory may be created the first time they log on
    ;[profiles]
    ;   comment = Users profiles
    ;   path = /home/samba/profiles
    ;   guest ok = no
    ;   browseable = no
    ;   create mask = 0600
    ;   directory mask = 0700
    
    [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
    
    # A sample share for sharing your CD-ROM with others.
    ;[cdrom]
    ;   comment = Samba server's CD-ROM
    ;   read only = yes
    ;   locking = no
    ;   path = /cdrom
    ;   guest ok = yes
    
    # The next two parameters show how to auto-mount a CD-ROM when the
    #	cdrom share is accesed. For this to work /etc/fstab must contain
    #	an entry like this:
    #
    #       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
    #
    # The CD-ROM gets unmounted automatically after the connection to the
    #
    # If you don't want to use auto-mounting/unmounting make sure the CD
    #	is mounted on /cdrom
    #
    ;   preexec = /bin/mount /cdrom
    ;   postexec = /bin/umount /cdrom
    
    
    [machine backups]
    	guest account = backups
    	force user = backups
    	comment = Client machine backups
    	writeable = yes
    	public = yes
    	path = /home/backups/machine backups
    	allow hosts = 192.168.1.3

  5. #5
    ahallubuntu is offline Chocolate-Covered Ubuntu Beans
    Join Date
    Jul 2005
    Beans
    2,050

    Re: Samba Share for Windows Backup

    ~
    Last edited by ahallubuntu; July 3rd, 2013 at 02:24 AM.

  6. #6
    Join Date
    Dec 2009
    Beans
    5,304

    Re: Samba Share for Windows Backup

    Do you really want the users of 3 machines to have write access to every other users backup files?

    BTW, this is how Samba will interpret your share definition:
    [machine backups]
    comment = Client machine backups
    path = /home/backups/machine backups
    force user = backups
    read only = No
    guest ok = Yes
    hosts allow = 192.168.1.3
    ** It will throw out the "guest account" line since it doesn't belong in a share definition and besides you already have a default guest account called "nobody"

    ** As stated above the "hosts allow" line makes no sense since it limits access only to the host machine located at 192.168.1.3.

    ** It's the "force user" line that has me perplexed since all remote users will be converted to the same Linux user and thus will have access to everyone else's files.

    ** Finally, your use of PSCP ( I'm assuming this is some kind of SSH or SFTP client ) will make a mess of things as far as ownership and permissions if you access the same folder as the one you defined in samba.

    Why not create 3 different shares at 3 different directories:
    path = /home/backups/machine backups/WinXP
    path = /home/backups/machine backups/OSX1
    path = /home/backups/machine backups/OSX2

    Use the "valid users" line to limit access only to the user on that machine for that particular share. For example:

    Code:
    [WinXP-BU]
        comment = Client machine backups
        path = /home/backups/machine backups/WinXP
        valid users = bob
        read only = No
        guest ok = No
    Where "bob" is the WinXP user that's doing the backup.

    Then make bob the owner of the folder:
    sudo chown bob "/home/backups/machine backups/WinXP"

  7. #7
    Join Date
    Sep 2013
    Beans
    Hidden!
    Distro
    Ubuntu 13.04 Raring Ringtail

    Re: Samba Share for Windows Backup

    Here is what I did to get my Samba share work, I used Ubuntu Server 12.04 BE sure to make a Samba user so that you can have a valid user to enable valid user while you declare a share:

    Code for creating a Samba user:
    smbpasswd -a fred #This can be either the name of the client machine you are going to back up, or what ever you like, but for simplicity use the client machine name.
    type in the password for this user
    confirm password
    Done!

    Code for declaring share:
    [Share]
    comment = Samba Backup
    path = /windows/backup/machine-x
    valid user = fred
    guest ok = no
    read only = no
    writable = yes
    browseable = yes
    create mask = 0766 #You may also mark this as 0777 if you are having writing issue, but this comprises security...

    Be sure to make the security = user in the [global] section, now when you try to access this share from your Windows machine you will have to login with the credentials with what you declared in the smbpasswd -a fred code. I believe you will enter the credentials from Windows like:
    Username: linux-server\fred
    Password: password

    Also, be sure to restart Samba by issuing:
    service smbd restart
    service nmbd restart

    This worked pretty well for me but if you still have troubles with writing files to the folder from the Windows machine, go back to the Linux server and make sure that the path that you set up for the machines to back up to is owned fred or what ever name you choose. This means you may also have to create this user on the server by doing: useradd and look up on how to create this user without creating the home directory if you want to just have the user on the machine without a backbone.

    Anyway, good luck!

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •