Results 1 to 5 of 5

Thread: Able to access SMB shares on Ubuntu from Windows...but not from Android =(

  1. #1
    Join Date
    Feb 2015
    Beans
    32

    Able to access SMB shares on Ubuntu from Windows...but not from Android =(

    Hey everyone !

    So i have tried to research as much as possible without asking on the forum..only because there have been so many posts about samba !

    Anyways, my samba works now after a bit. Here are the working :

    1. Able to access share from Windows computers/tablets
    2. Able to share my RAID device (dev/md0)

    The cons :

    1. Unable to access from any android device using andsmb or es file explorer.
    2. Crashes my ubuntu sign-on every other time (sambashare) user apparently.

    Anyways, here is the output of my smb.conf :
    Code:
    #======================= Global Settings =======================
    
    
    [global]
    
    
    ## Browsing/Identification ###
    
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    	workgroup = network
    
    
    # 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
    
    
    #### 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 #######
    
    
    # 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
    
    
    ########## Domains ###########
    
    
    #
    # The following settings only takes effect if 'server role = primary
    # classic domain controller', 'server role = backup domain controller'
    # or '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
    
    
    ############ 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
    
    
    # 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
    
    
    # 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
    	username map = /etc/samba/smbusers
    	security = user
    	encrypt passwords = no
    	guest ok = yes
    ;	guest account = nobody
    
    
    #======================= 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 directory 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
    # This might need tweaking when using external authentication schemes
    ;   username = %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
    
    
    [NetworkArray]
    	path = /media/saad/NetworkArray/NetworkArray
    	writeable = yes
    ;	browseable = yes
    	username = saad
    	guest ok = yes
    I am looking for a no-user name needed access to my share across my network. That is the configuration i had before my SSD failed on me. Currently on the windows machines i am accessing the shares by
    \\NAS\ then entering \ as username with password blank. I am able to access the NetworkArray share on the server without any issues.

    Would appreciate the help !
    Last edited by PaulW2U; July 14th, 2015 at 06:17 AM. Reason: Added code tags to improve readability

  2. #2
    Join Date
    Feb 2015
    Beans
    32

    Re: Able to access SMB shares on Ubuntu from Windows...but not from Android =(

    Any ideas ? Thanks !!

  3. #3
    Join Date
    Nov 2008
    Location
    Boston MetroWest
    Beans
    16,326

    Re: Able to access SMB shares on Ubuntu from Windows...but not from Android =(

    Can you log in as user saad using AndSMB? That works for me.
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  4. #4
    Join Date
    Feb 2015
    Beans
    32

    Re: Able to access SMB shares on Ubuntu from Windows...but not from Android =(

    Quote Originally Posted by SeijiSensei View Post
    Can you log in as user saad using AndSMB? That works for me.
    Nope. Just tried. Just says connecting and it sits there. CD / OK lS / and nothing happens.

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

    Re: Able to access SMB shares on Ubuntu from Windows...but not from Android =(

    I don't think I can help you since I don't know this can be possible:
    1. Able to access share from Windows computers/tablets
    With this in your smb.conf:
    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    usershare allow guests = yes
    username map = /etc/samba/smbusers
    security = user
    encrypt passwords = no
    guest ok = yes
    ; guest account = nobody
    Even is a guest accessible system that should be set to yes.

    If you are going in there anyway you might want to make this change:
    [NetworkArray]
    path = /media/saad/NetworkArray/NetworkArray
    writeable = yes
    ; browseable = yes
    valid users = saad
    guest ok = yes
    The "username" option isn't used any more so I don't know if Samba would just ignore it.

    Unless you meant to say "force user = saad".

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
  •