Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Troubleshooting samba authentication problems

  1. #11
    Join Date
    Jun 2013
    Beans
    14

    Re: Troubleshooting samba authentication problems

    The output of ifconfig |grep inet on Falcon is the following:

    Code:
              inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::21f:d0ff:fe99:c809/64 Scope:Link
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
    If I run smbtree from a different computer than falcon, the falcon section is:

    Code:
    \\FALCON                        falcon server (Samba, Ubuntu)Connecting to host=FALCON
    resolve_lmhosts: Attempting lmhosts lookup for name FALCON<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name FALCON<0x20>
    resolve_wins: Attempting wins lookup for name FALCON<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name FALCON<0x20>
    Connecting to 192.168.0.3 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=NONE
    Got challenge flags:
    Got NTLMSSP neg_flags=0x608a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
                    \\FALCON\IPC$                   IPC Service (falcon server (Samba, Ubuntu))
                    \\FALCON\accounting             ATS Accounting File Server
                    \\FALCON\projects               ATS General File Server
                    \\FALCON\print$                 Printer Drivers

    There are indeed many other computers on the network, but only a few are intended to be operational Samba servers and many others are windows laptops (TESTOPS-PC) and other "junk". VF8 is a CNC mill that apparently has some sort of samba server running. BRNDD1EFA is a printer. MFG is an operational Ubuntu Samba server (with user authorization enabled) which works great. The "open" share on falcon is operational and works great. Practically speaking, I'm the "administrator" of all this junk.
    Last edited by RyanBiggs; July 6th, 2013 at 02:14 AM.

  2. #12
    Join Date
    Jul 2008
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Troubleshooting samba authentication problems

    Quote Originally Posted by RyanBiggs View Post
    There are indeed many other computers on the network, but only a few are intended to be operational Samba servers and many others are windows laptops (TESTOPS-PC) and other "junk". VF8 is a CNC mill that apparently has some sort of samba server running. BRNDD1EFA is a printer. MFG is an operational Ubuntu Samba server (with user authorization enabled) which works great. The "open" share on falcon is operational and works great. Practically speaking, I'm the "administrator" of all this junk.
    I see the IP address now. It's 192.168.0.3.

    Any host that is sharing directories (a share) is a Samba server. It doesn't matter what hardware it is using. This includes the printer which is most likely sharing only printer drivers.

    I'm curious so let's make another of those big 'ol long replies. Post the output of
    Code:
    cat /etc/samba/smb.con
    I wonder if you need to explicitly allow users using: valid user = falcon, <other names> or: valid user @<a common user group>. I just noticed that you have not done that when you removed the: guest only = yes -- I'm a bit confused with all the postings -- am I correct in my thought here?

  3. #13
    Join Date
    Jun 2013
    Beans
    14

    Re: Troubleshooting samba authentication problems

    Any host that is sharing directories (a share) is a Samba server. It doesn't matter what hardware it is using. This includes the printer which is most likely sharing only printer drivers.
    Sure, I follow you there...

    I did try adding a "valid users" entry in smb.conf, as you can see in the following. Still no joy connecting to the guest ok = no ("accounting") share with that user (rbiggs):

    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 = ATS
    
    
    # server string is the equivalent of the NT Description field
       server string = %h 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
    
    
    # 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 = user
    
    
    # You may wish to use password encryption.  See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
       encrypt passwords = true
    
    
    # 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
    ;   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
       usershare allow guests = yes
    
    
    #======================= 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
    [projects]
        comment = ATS General File Server
        path = /srv/falcon/projects
        browsable = yes
        create mask = 0755
        guest ok = yes
        read only = no
    
    
    [accounting]
        comment = ATS Accounting File Server
        path = /srv/falcon/accounting
        browsable = yes
        create mask = 0755
        guest ok = no
        read only = no
        valid users = rbiggs

  4. #14
    Join Date
    Jul 2008
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Troubleshooting samba authentication problems

    Did you restart the smbd daemon?

    Code:
    sudo service smbd restart

  5. #15
    Join Date
    Jun 2013
    Beans
    14

    Re: Troubleshooting samba authentication problems

    Did you restart the smbd daemon?
    Yes, but I usually do so with

    Code:
    sudo restart smbd
    sudo restart nmbd
    I did try

    Code:
    sudo service smbd restart
    just to be sure. Not sure if there's any difference in practice...

  6. #16
    Join Date
    Jul 2008
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Troubleshooting samba authentication problems

    There is no difference. Either way seems to work.

    I have a feeling that the file system permissions are going to be the culprit. I don't see anything wrong with the smb.conf file. I wuld check the permissions along the entire path from / to /srv/falcon/<the directory>. The user should have execute permission along the entire directory path in some way as either the user or a member of the group or at least the others execute bit should be set. Note this is only on the directories in the path. The files permissions are another thing entirely.

  7. #17
    Join Date
    Jun 2013
    Beans
    14

    Re: Troubleshooting samba authentication problems

    I wuld check the permissions along the entire path from / to /srv/falcon/<the directory>. The user should have execute permission along the entire directory path in some way as either the user or a member of the group or at least the others execute bit should be set.
    That was my thought early on as well, but the execute permissions were all set -- just to be extra sure, I set the directory permissions wide open (0777) from srv on down just to be sure (yeah I know, bad idea lol). Still no dice.

    Pretty mysterious. Is there a way to see more detail about what is going wrong in the authentication process? The Samba logs I looked at didn't seem to indicate much. I also might think about connecting from another Ubuntu box instead of Windows but need to look into how best to do that. mount -t cifs, or is there a better way to test?

  8. #18
    Join Date
    Jun 2013
    Beans
    14

    Re: Troubleshooting samba authentication problems

    OOPS --now this is a "sorry to waste your time" moment -- I was trying with two different Windows computers, neither of which could get into the share. Somewhere along the way, I must have fixed the problem (unix permissions perhaps?), but those two computers still won't log in though they ask for credentials on each attempt. But I went and tried some completely different Windows computers, and they work!

    It's another question why the Windows PCs don't see the share as-is, but I bet they will after a reboot. I should have known Windows was more likely the problem than Linux!

    Thanks for all the help redmk2, and sorry again to have you on a wild goose chase!

  9. #19
    Join Date
    Jul 2008
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Troubleshooting samba authentication problems

    Quote Originally Posted by RyanBiggs View Post
    OOPS --now this is a "sorry to waste your time" moment -- I was trying with two different Windows computers, neither of which could get into the share. Somewhere along the way, I must have fixed the problem (unix permissions perhaps?), but those two computers still won't log in though they ask for credentials on each attempt. But I went and tried some completely different Windows computers, and they work!

    It's another question why the Windows PCs don't see the share as-is, but I bet they will after a reboot. I should have known Windows was more likely the problem than Linux!

    Thanks for all the help redmk2, and sorry again to have you on a wild goose chase!
    Doh! I don't know how many times I've been caught like you. I try and remember that if I'm dealing with Windows that the first thing you do is reboot the dang thing! At least you finally resolved the issue.

Page 2 of 2 FirstFirst 12

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
  •