Announcement

Collapse
No announcement yet.

Samba setup on Kubuntu

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Samba setup on Kubuntu

    Greetings,

    I came to Kubuntu from Mepis. Mepis offered a shared folder by default and several setup tools to allow you to fine tune Samba. I did install the various Samba utilities and packages in Kubuntu and I also installed Webmin to try and help setting Samba properly but Samba still does not seem to work properly. Win7 and MacosX users can see me but not log into my shared folder nor can they use my printers.

    This is the content of my etc/samba/samba.conf file that I edited manually:

    #
    # 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
    load printers = yes
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    obey pam restrictions = yes
    create mask = 0775
    null passwords = yes
    map to guest = bad user
    winbind trusted domains only = yes
    encrypt passwords = yes
    winbind use default domain = yes
    passwd program = /usr/bin/passwd %u
    passdb backend = tdbsam
    dns proxy = no
    server string = %h server (Samba, Ubuntu)
    printing = cups
    path = /home/michel/michelshare
    default = michelshare
    unix password sync = yes
    workgroup = workgroup
    os level = 20
    printcap name = cups
    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

    # 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

    # 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.

    ############ 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 =======================

    # 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.

    # 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 = 0775

    # 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

    [michelshare]
    guest account = nobody
    writable = yes
    path = /home/michel/michelshare
    guest ok = yes
    browsable = yes
    create mode = 0666
    public = yes
    guest only = yes
    directory mode = 0666


    # 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]
    browseable = no
    printable = yes
    path = /var/spool/samba
    create mask = 0700
    comment = All Printers
    public = yes
    guest only = yes

    # 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
    This is very frustrating and is making me loose a tot of valuable time. Your help would be appreciated.

    Michel

    #2
    Michel:

    I had the same issues coming from Xandros....

    Do you have, or can you get a copy of your Samba config file from Mepis? A visual comparison may show you what you need to change.

    Frank.
    Linux: Powerful, open, elegant. Its all I use.

    Comment


      #3
      I already did that and this is the result. I also reviewed a lot of Samba setup info online but still ....

      Michel

      Comment


        #4
        I'm in the Ottawa airport at the moment. I think I may still have some notes from years ago on that, but it will have to wait
        until I can unpack my laptop....

        Frank.
        Linux: Powerful, open, elegant. Its all I use.

        Comment


          #5
          There were some discrepancies with the guest user account. I had nobody but Webmin showed that samba was using guest for the guest account, a remnant from the various tweaks using Garmin and other samba utilities!

          I managed to hook up with the Mac Pro. The issue was also with Mac OSX 10.7 and it's lack of Samba support. Now I can exchange files both ways. I can hook up with Win 7 but still have issues with printer sharing.

          Michel
          Last edited by michel; Sep 27, 2012, 03:05 PM.

          Comment


            #6
            Michel:

            I found the file from years ago that helped me set SAMBA up correctly. Permissions should be 0777 if you want the machines logging in to be able to write files, not 0666, and there are a couple of other things that you want to do, as highlighted in yelllow in the attached ODT file.

            This is a long article taken from the Ubuntu forum in 2005, but I think is still current. A lot of it you may have done already. My personal notes are at the very bottom of that article.

            I also started using SWAT some time ago, and find it easier than the KDE tools, which keep changing. I mostly use the simple view in SWAT, but its been a long time since I needed or used SAMBA, so my memory may fail me.

            If SWAT (Samba Web Administration Tool) is not installed, then get it from the repos. SWAT does not 'run' as such, but is a web tool that you point your browser to. It will rewrite your Samba config file for you, so you may want to make a backup first, or just rename your current Samba config file first, and let SWAT create a blank one for you with all the defaults in place. Sometimes it is easier starting with a clean slate.

            You enter SWAT from the address bar of your broswer with the following:

            localhost:901

            On my machines, I have the root account enabled, so I use the root account, and provide the root password. I'm not sure what yours will ask for.

            Hope this helps.

            Frank.
            Attached Files
            Last edited by Frank616; Sep 27, 2012, 07:31 PM.
            Linux: Powerful, open, elegant. Its all I use.

            Comment


              #7
              Michel:

              I can hook up with Win 7 but still have issues with printer sharing.
              Sharing which way? Getting the Linux box to print to the printer on the Windows machine, or vice versa?

              Will your printers connect directly to the LAN you use? If so, that is the easiest way to allow both the Windows and Linux machines to use the same printers. If the printer is on the Windows machine, and you want to print to it from the Linux box, then printer sharing must specifically be turned on in Windows. The same is basically true if trying to print in the other direction. For that, you have to specifically make your printer on your Linux box public, or shared in your samba config file.

              Frank.
              Linux: Powerful, open, elegant. Its all I use.

              Comment


                #8
                All is well now. Thanks for your help.

                Michel

                Comment


                  #9
                  Michel:

                  All is well now.
                  Great!

                  Frank.
                  Linux: Powerful, open, elegant. Its all I use.

                  Comment

                  Working...
                  X