Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 44

Thread: Configuring Samba

  1. #21
    Join Date
    Dec 2012
    Beans
    38

    Re: Configuring Samba

    Might I make a suggestion? You are following so many HowTo's that your smb.conf may be a mess. What would help is if you tell us what the current state of your system is and you can do that by posting the output of the following commands:
    Code:
    testparm -s
    Ok As below :

    Code:
    testparm -s
    Load smb config files from /etc/samba/smb.conf
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    Can't find include file /etc/samba/dhcp.conf
    Processing section "[printers]"
    Processing section "[print$]"
    Processing section "[disk1]"
    Processing section "[disk]"
    WARNING: The security=share option is deprecated
    Loaded services file OK.
    Server role: ROLE_STANDALONE
    [global]
        workgroup = JOEGROUP
        server string = Home server (Samba, Ubuntu)
        security = SHARE
        encrypt passwords = No
        map to guest = Bad User
        obey pam restrictions = Yes
        guest account = joe
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        usershare allow guests = Yes
        usershare owner only = No
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb
        guest ok = Yes
    
    [printers]
        comment = All Printers
        path = /var/spool/samba
        create mask = 0700
        printable = Yes
        print ok = Yes
        browseable = No
    
    [print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers
        valid users = joe
        read only = No
    
    [disk1]
        comment = media/disk1
        path = /media/disk1
        valid users = joe
        read only = No
        create mask = 00
    
    [disk]
        comment = Media disk0
        path = /media/disk
        read only = No
    Suggestion 2
    Code:
    net usershare info --long
    Code:
    joe@homeserve:~$ net usershare info --long
    [media]
    path=/media/disk1
    comment=
    usershare_acl=Everyone:F,
    guest_ok=y
    
    [disk]
    path=/media/disk
    comment=
    usershare_acl=Everyone:F,
    guest_ok=n
    
    [Tubby]
    path=/media/disk/Tubby
    comment=
    usershare_acl=Everyone:F,
    guest_ok=n

  2. #22
    Join Date
    Dec 2012
    Beans
    38

    Re: Configuring Samba

    My Samba.conf file is included below for close scrutiny , is this set up right?

    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]
    
    ## Browsing/Identification ###
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
        workgroup = joegroup
    
    # server string is the equivalent of the NT Description field
        server string = Home server (Samba, Ubuntu)
    
    # 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
    
    # If we receive WINS server info from DHCP, override the options above. 
        include = /etc/samba/dhcp.conf
    
    # This will prevent nmbd to search for NetBIOS names through DNS.
        dns proxy = no
    
    # 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
        log file = /var/log/samba/log.%m
    
    # Cap the size of the individual log files (in KiB).
        max log size = 1000
    
    # 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.
        syslog = 0
    
    # Do something sensible when Samba crashes: mail the admin a backtrace
        panic action = /usr/share/samba/panic-action %d
    
    
    ####### 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 = share
    
    # You may wish to use password encryption.  See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
        encrypt passwords = no
    
    # 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
    
    ########## 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
    
    # 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
        usershare allow guests = yes
    
        usershare owner only = false
        guest ok = yes
        guest account = joe
    
    #======================= 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
        writeable = yes
        valid users = joe
    # 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
    
    [disk1]
        comment = media/disk1
        path = /media/disk1
    ;    browseable = yes
        writeable = yes
        create mask = 0
        valid users = joe
    
    [disk]
        path = /media/disk
        writeable = yes
    ;    browseable = yes
        guest ok = yes
        comment = Media disk0

  3. #23
    Join Date
    Dec 2009
    Beans
    5,713

    Re: Configuring Samba

    I actually see may things that are wrong with it but you claim it works so I would leave it alone

    My theory is that these two mistakes cancelled each other out:
    security = SHARE
    encrypt passwords = No
    No one still living knows how share level security works though so it's just a guess on my part.

    Since you followed 2 ( maybe 3 ) different howto's you have multiple shares using 2 different samba methods on the same target folder:

    This is a classic samba share. It's accessible and writeable only to the user joe:
    [disk1]
    comment = media/disk1
    path = /media/disk1
    ; browseable = yes
    writeable = yes
    create mask = 0
    valid users = joe
    This is a Samba Usershare ( created through the file manager ). It's accessible and writeable to everyone and your Aunt Agnes:
    [media]
    path=/media/disk1
    comment=
    usershare_acl=Everyone:F, guest_ok=y
    2 different share names however so Samba will honor your wishes to both but not exactly sure what your intent is on the target directory: /media/disk1.

    Anyway, this was more of a rant really. You claim this all works so "don't fix it if it ain't broke" I always say. You seem to have bigger problems if you can't connect to the internet. Sorry , can't help you with that.
    Last edited by Morbius1; December 30th, 2012 at 05:18 PM.

  4. #24
    Join Date
    Apr 2011
    Location
    Santiago (Dominican Rep)
    Beans
    311
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Configuring Samba

    What all of this proves is: Never start using complex CLI instructions, if you have no clue, what you are doing. Insist on the use of the GUI in that case. If you had stayed with the Samba utility, none of this would have been necessary.

    I have 45 of years of experience with the CLI, starting from the IBM-360 main frame days. Nowadays even I, if I see a CLI instruction for Linux, that is longer then 1 page, I skip it as too complex and retarded and continue to search for simpler GUI solutions. Often there is a small program or script available that can assist you in that work like e.g. the Samba Utility.

    There is an unhealthy habit in the Ubuntu user community to brag about the use of the CLI. It is old fashioned and any normal user should try to avoid it, since its use is only justifiable in a limited number of cases.

    For any new user, clearly specify your desktop and version number and don't use any CLI that is more then a few command lines. Remember some of the people responding do not really master the CLI either and just repeat something that worked in their circumstances. Many of those prescriptions people refer to are based on releases that are two or more years old and if you can't understand it, you might mess up your system completely.

    Since the stone age of computing the big problem with the CLI have been the typos made by you or the typos made in the prescription given to you.
    Last edited by BertN45; December 30th, 2012 at 11:22 PM.
    Desktop: P-IV 3.2gHz, RAM= 1.5GB, Disk=80GB+500GB, LCD=22", Bought 2012 $90
    File Server: P-III 650mHz, RAM = 384MB, Disks 240 + 300GB, Bought 2005 $60
    File Server HP Vectra VL8i SFF, 2 cables connected: Ethernet and Power

  5. #25
    Join Date
    Apr 2011
    Location
    Santiago (Dominican Rep)
    Beans
    311
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Configuring Samba

    Quote Originally Posted by 90Ninety View Post
    Ok with the above gudie ( thanks Horbo http://ubuntuforums.org/showthread.php?t=1685718)

    Ican now access folders and drives on my sever from the Windows LAN PC's . I done this by entering the ip address of the Server into the windows PC -phew.


    Now another hurdle , since I have changed the network settings on the server, I can no longer load webpages , please see attachment in last post to see what Im doing wrong . Any reason why I cannot now use the web on the server?
    A web issue is completely independent from SAMBA file server. Don't touch smb.conf anymore. If you want http pages to be displayed from your server you have to install the Apache web server and ask for help with that. I propose you open a separate thread in that case.
    Last edited by BertN45; December 30th, 2012 at 11:18 PM.
    Desktop: P-IV 3.2gHz, RAM= 1.5GB, Disk=80GB+500GB, LCD=22", Bought 2012 $90
    File Server: P-III 650mHz, RAM = 384MB, Disks 240 + 300GB, Bought 2005 $60
    File Server HP Vectra VL8i SFF, 2 cables connected: Ethernet and Power

  6. #26
    Join Date
    Apr 2011
    Location
    Santiago (Dominican Rep)
    Beans
    311
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Configuring Samba

    If you can't load the internet pages onto your server, you have probably made an error at the moment you defined the static addresses, see my attachement. Be aware that there is a small chance your router might re-assign the same static address through DHCP again to another PC. It depends on the design of the wifi router. If that ever happens, you can change the range of DHCP addresses the router assigns and make sure your static address(es) are outside that range.

    I expect the issue is with the DNS addresses, I use the Google DNS server 8.8.8.8 and my wifi router DNS server.

    Don't look at my somewhat unusual net-mask.
    Attached Images Attached Images
    Last edited by BertN45; December 30th, 2012 at 11:32 PM.
    Desktop: P-IV 3.2gHz, RAM= 1.5GB, Disk=80GB+500GB, LCD=22", Bought 2012 $90
    File Server: P-III 650mHz, RAM = 384MB, Disks 240 + 300GB, Bought 2005 $60
    File Server HP Vectra VL8i SFF, 2 cables connected: Ethernet and Power

  7. #27
    Join Date
    Dec 2012
    Beans
    101

    Re: Configuring Samba

    Quote Originally Posted by 90Ninety View Post
    Ok with the above gudie ( thanks Horbo http://ubuntuforums.org/showthread.php?t=1685718)

    Ican now access folders and drives on my sever from the Windows LAN PC's . I done this by entering the ip address of the Server into the windows PC -phew.

    Now another hurdle , since I have changed the network settings on the server, I can no longer load webpages , please see attachment in last post to see what Im doing wrong . Any reason why I cannot now use the web on the server?
    You have used 192.168.0.1 (your gateway) as your DNs server on the samba server.
    However (assuming it is correct) the windows machine has 192.168.4.100 and 192.168.8.100 as DNS servers. Seems a little unusual to me, but try changing the DNS server setting (but leave the gateway as is) on the samba server to 192.168.4.100 and see if you can open web pages then.

    Quote Originally Posted by BertN45 View Post
    What all of this proves is: Never start using complex CLI instructions, if you have no clue, what you are doing. Insist on the use of the GUI in that case. If you had stayed with the Samba utility, none of this would have been necessary.

    I have 45 of years of experience with the CLI, starting from the IBM-360 main frame days. Nowadays even I, if I see a CLI instruction for Linux, that is longer then 1 page, I skip it as too complex and retarded and continue to search for simpler GUI solutions.
    I don't have 45 years experience, but I do have a degree in computer science, and I am the same: any solution requiring dozens of CLI commands gets ignored by me - I just can't be bothered.
    Last edited by Horbo; December 31st, 2012 at 01:15 AM.

  8. #28
    Join Date
    Dec 2012
    Beans
    38

    Re: Configuring Samba

    There is an unhealthy habit in the Ubuntu user community to brag about the use of the CLI. It is old fashioned and any normal user should try to avoid it, since its use is only justifiable in a limited number of cases.
    Very true , people seem to get an ego using CLI..

    Right next hurdle . I now have my Ubuntu 12.10 desktop server networked and talikng with the windows client machines . I went back a few steps , changed connection mode to DCHP (automatic) and it seems to have fixed itself . I will refrain from using manual/static IP settings for now

    At the moment I have a securtiy issue , the only way I can access my server is buy checking the 'Allow guest access' option on the drives . However if I uncheck and try to access the same drives again , I am prompted for my login details , which every time I enter , windoze tells me its the wrong details , Iam not too worried though .. However why arent my log in details working? I have two user accounts on the Ubuntu machine and have tried my log in details many times , for folder access what gives?

  9. #29
    Join Date
    Dec 2009
    Beans
    5,713

    Re: Configuring Samba

    the only way I can access my server is buy checking the 'Allow guest access' option on the drives . However if I uncheck and try to access the same drives again , I am prompted for my login details , which every time I enter , windoze tells me its the wrong details , Iam not too worried though .. However why arent my log in details working? I have two user accounts on the Ubuntu machine and have tried my log in details many times , for folder access what gives?
    Two different sets of credentials.

    Let's say you have a user on your Linux server box called: morbius. That user can log into the local box itself with username = morbius and a password = morbiuspw.

    The Samba server knows nothing of that user or password so you need to add morbius to the samba password database by using this command:
    Code:
    sudo smbpasswd -a morbius
    It will ask you for sudos's password first then it will ask you for the password you want to give morbius for samba purposes. It can be the same password morbius would use to log into the box itself or it can be something different - that's up to you since you are the System Administrator.

    EDIT: Since the conversation has moved somewhat to CLI vs GUI I apologize for offering a CLI solution for this issue but It's the one I'm more comfortable with personally. And there is one other thing I would point out:

    The OP is using 2 different methods to create samba shares. Some shares are in /etc/samba/smb.conf and some shares are in /var/lib/samba/usershares. Both will work but as you can see above they might conflict with one another. If you only use the Nautilus method to create shares then adding users to the samba database can only be done via CLI since the Nautilus method has no way of doing that.
    Last edited by Morbius1; December 31st, 2012 at 03:07 PM.

  10. #30
    Join Date
    Dec 2012
    Beans
    38

    Re: Configuring Samba

    Thanks Morbius , you're cool

    May aswell close this thread , as I will open an unrelated one next


    Thanks guys , Ubuntu's really pushed me out the comfort zone but I am beginning to see its potential

Page 3 of 5 FirstFirst 12345 LastLast

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
  •