
Hi guys. I am having an issue with my fresh samba setup. I built a 14.04.1 LTS Ubuntu server and set up a single mount point (/media/data) and pointed 3 separate internal hard drives to it (eg it contains directories "music_drive", "tv_drive" & "movie_drive"). I turned "/media/data" into a samba share. Annoyingly permissions look fine but I cannot seem to be able to either see the share on my network from other machines or connect to it. Even using the servers IP address. Any advice? Or am I just missing something obvious. My config is below. samba.conf # # 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. #======================= Global Settings ======================= [global] passwd program = /usr/bin/passwd %u max log size = 1000 browseable = yes workgroup = RIMFALL passdb backend = tdbsam obey pam restrictions = yes map to guest = bad user unix password sync = yes os level = 20 server role = standalone server printing = cups load printers = no netbios aliases = ook preferred master = yes available = yes default = lspace panic action = /usr/share/samba/panic-action %d wins support = true netbios name = ook security = user server string = %h server (Samba, Ubuntu) passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes syslog = 0 dns proxy = no log file = /var/log/samba/log.%m usershare allow guests = 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. #### 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 ####### # 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. # 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(a)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 ########### # # 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 #======================= 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 ; 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 available = no writable = no printable = yes path = /var/spool/samba guest ok = no create mask = 0700 browseable = no # Windows clients look for this share name as a source of downloadable # printer drivers [print$] guest ok = no writable = no path = /var/lib/samba/printers comment = Printer Drivers # 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 [lspace] valid users = david, steff, tracey, smbguest, @sambashare guest account = comment = Lspace media share writeable = yes force group = sambashare path = /media/data read list = smbguest write list = david, steff, tracey

On Wed, 28 Jan 2015 21:31:20 +1300, David Nicholls wrote:
[global] workgroup = RIMFALL
Just a guess, don’t I recall that the workgroup has to be called “WORKGROUP” if you’re not running actual domain controllers? Also, may be worth trying the testparm(1) command to dump out what SAMBA really thinks your configuration looks like.

Ok. did a testparm... below is my output. looks like ive got an issue in my security area? Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) WARNING: Ignoring invalid value 'share' for parameter 'security' Processing section "[printers]" NOTE: Service printers is flagged unavailable. Processing section "[print$]" Processing section "[lspace]" Global parameter guest account found in service section! Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] workgroup = RIMFALL netbios aliases = ook server string = %h server (Samba, Ubuntu) server role = standalone server map to guest = Bad User obey pam restrictions = Yes 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 load printers = No preferred master = Yes dns proxy = No wins support = Yes default service = lspace usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d idmap config * : backend = tdb [printers] comment = All Printers path = /var/spool/samba create mask = 0700 printable = Yes print ok = Yes browseable = No available = No [print$] comment = Printer Drivers path = /var/lib/samba/printers [lspace] comment = Lspace media share path = /media/data valid users = david, steff, tracey, smbguest, @sambashare read list = smbguest write list = david, steff, tracey force group = sambashare read only = No On 28 January 2015 at 21:53, Lawrence D'Oliveiro <ldo(a)geek-central.gen.nz> wrote:
On Wed, 28 Jan 2015 21:31:20 +1300, David Nicholls wrote:
[global] workgroup = RIMFALL
Just a guess, don’t I recall that the workgroup has to be called “WORKGROUP” if you’re not running actual domain controllers?
Also, may be worth trying the testparm(1) command to dump out what SAMBA really thinks your configuration looks like. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
-- *Cheers...David Nicholls* *Computer SupportFaculty of Science and Engineeringx5006, fsen_csg(a)waikato.ac.nz <fsen_csg(a)waikato.ac.nz>*

On Sun, 1 Feb 2015 17:47:34 +1300, David Nicholls wrote:
[global] workgroup = RIMFALL netbios aliases = ook server string = %h server (Samba, Ubuntu) server role = standalone server map to guest = Bad User obey pam restrictions = Yes 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 load printers = No preferred master = Yes dns proxy = No wins support = Yes default service = lspace usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d idmap config * : backend = tdb
Interesting that testparm doesn’t show an “interfaces” line here. It does for me.

First, I just checked my SMB.conf for interfaces and found it commented that portion out (see below). Would that be why it's not showing up in testparm?: #### 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 ------------ I also got the output of "ifconfig" (below) - p2p1 being the active interface. I'm guessing the interfaces line above needs to be changed, but to what exactly? Another piece of info that might help with answers is a bit of info on the layout of my network... any wired machines, access points etc are on the 192.168.1.nnn range 192.168.0.nnn wirelessly connected devices lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 p2p1 Link encap:Ethernet HWaddr 74:d4:35:be:72:6d inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::76d4:35ff:febe:726d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 On 1 February 2015 at 18:47, Lawrence D'Oliveiro <ldo(a)geek-central.gen.nz> wrote:
On Sun, 1 Feb 2015 17:47:34 +1300, David Nicholls wrote:
[global] workgroup = RIMFALL netbios aliases = ook server string = %h server (Samba, Ubuntu) server role = standalone server map to guest = Bad User obey pam restrictions = Yes 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 load printers = No preferred master = Yes dns proxy = No wins support = Yes default service = lspace usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d idmap config * : backend = tdb
Interesting that testparm doesn’t show an “interfaces” line here. It does for me. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
-- *Cheers...David Nicholls* *Computer SupportFaculty of Science and Engineeringx5006, fsen_csg(a)waikato.ac.nz <fsen_csg(a)waikato.ac.nz>*

On Tue, 3 Feb 2015 20:49:24 +1300, David Nicholls wrote:
First, I just checked my SMB.conf for interfaces and found it commented that portion out (see below). Would that be why it's not showing up in testparm?
Actually, the doc says by default it listens on everything except 127.0.0.1. Did you try netstat? Another thing to look at is smbclient, the Linux SMB client. You can try using this to connect to your server, from the same or a different machine. Maybe that will give more illuminating error messages...

Well that looks like my problem then?: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp6 0 0 ::1:5432 :::* LISTEN tcp6 0 0 :::445 :::* LISTEN tcp6 0 0 :::5800 :::* LISTEN tcp6 0 0 :::139 :::* LISTEN tcp6 0 0 :::5900 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN Ive been banging away at this for a few weeks now and my external network conectivity seems to have gone just in the last day... I'm not quite sure what's going on. Is anyone over Ham East way and happy to drop by my place for 5 or 10 minutes? I suspect I'm just missing something subtle or simple. cheers... David On 3 February 2015 at 21:27, Lawrence D'Oliveiro <ldo(a)geek-central.gen.nz> wrote:
On Tue, 3 Feb 2015 20:49:24 +1300, David Nicholls wrote:
First, I just checked my SMB.conf for interfaces and found it commented that portion out (see below). Would that be why it's not showing up in testparm?
Actually, the doc says by default it listens on everything except 127.0.0.1.
Did you try netstat?
Another thing to look at is smbclient, the Linux SMB client. You can try using this to connect to your server, from the same or a different machine. Maybe that will give more illuminating error messages... _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

On Wed, 4 Feb 2015 18:48:30 +1300, David Nicholls wrote:
Well that looks like my problem then?:
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
No, those two look fine.
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
And by default you also get IPv6 as well. :) Maybe try smbclient?

Hi Lawrence, So you already have samba running. Try connecting to it from another computer on the same subnet ( 192.168.1.?). With your samba server on 192.168.1.200, verify that you can connect if you do: ping 192.168.1.200 and telnet 192.168.1.200 445 or telnet 192.168.1.200 139 If you can't ping at all then fix your connectivity first or use another computer. If you can ping and you can't connect via telnet then you may have firewall blocking the connection. If telnet says connected then the problem could be your samba config. In your testparm, your Global settings have issues. I suggest you start with a basic config file just like the Sample Passwordless Configuration in the following link: https://wiki.archlinux.org/index.php/Samba/Tips_and_tricks Don't forget to restart samba or reboot your server after the config change. Regards, Noel On Wed, Feb 4, 2015 at 7:28 PM, Lawrence D'Oliveiro <ldo(a)geek-central.gen.nz
wrote:
On Wed, 4 Feb 2015 18:48:30 +1300, David Nicholls wrote:
Well that looks like my problem then?:
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
No, those two look fine.
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
And by default you also get IPv6 as well. :)
Maybe try smbclient? _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

Ops, should have said Hi David. LOL On Wed, Feb 4, 2015 at 9:04 PM, Noel Villamor <noelrv(a)gmail.com> wrote:
Hi Lawrence,
So you already have samba running.
Try connecting to it from another computer on the same subnet ( 192.168.1.?). With your samba server on 192.168.1.200, verify that you can connect if you do:
ping 192.168.1.200 and telnet 192.168.1.200 445 or telnet 192.168.1.200 139
If you can't ping at all then fix your connectivity first or use another computer.
If you can ping and you can't connect via telnet then you may have firewall blocking the connection.
If telnet says connected then the problem could be your samba config. In your testparm, your Global settings have issues. I suggest you start with a basic config file just like the Sample Passwordless Configuration in the following link:
https://wiki.archlinux.org/index.php/Samba/Tips_and_tricks
Don't forget to restart samba or reboot your server after the config change.
Regards,
Noel
On Wed, Feb 4, 2015 at 7:28 PM, Lawrence D'Oliveiro < ldo(a)geek-central.gen.nz> wrote:
On Wed, 4 Feb 2015 18:48:30 +1300, David Nicholls wrote:
Well that looks like my problem then?:
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
No, those two look fine.
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
And by default you also get IPv6 as well. :)
Maybe try smbclient? _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

You created the samba password for your users david, steff and tracey? who were already users on your server? man smbpasswd sudo smbpasswd -a david Cheers, Roger On 28/01/2015 9:31 p.m., David Nicholls wrote:
Hi guys. I am having an issue with my fresh samba setup. I built a 14.04.1 LTS Ubuntu server and set up a single mount point (/media/data) and pointed 3 separate internal hard drives to it (eg it contains directories "music_drive", "tv_drive" & "movie_drive"). I turned "/media/data" into a samba share. Annoyingly permissions look fine but I cannot seem to be able to either see the share on my network from other machines or connect to it. Even using the servers IP address. Any advice? Or am I just missing something obvious. My config is below.
samba.conf
[lspace] valid users = david, steff, tracey, smbguest, @sambashare guest account = comment = Lspace media share writeable = yes force group = sambashare path = /media/data read list = smbguest write list = david, steff, tracey
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

Yeah. All the users should have the same password as their user name on the server. I got webmin to import the users and passwords. Encrypted though. The problem seems to be more around seeing and connecting to the share. On 29/01/2015 7:36 AM, "Roger Searle" <roger(a)stepahead.org.nz> wrote:
You created the samba password for your users david, steff and tracey? who were already users on your server?
man smbpasswd sudo smbpasswd -a david
Cheers, Roger
On 28/01/2015 9:31 p.m., David Nicholls wrote:
Hi guys. I am having an issue with my fresh samba setup. I built a 14.04.1 LTS Ubuntu server and set up a single mount point (/media/data) and pointed 3 separate internal hard drives to it (eg it contains directories "music_drive", "tv_drive" & "movie_drive"). I turned "/media/data" into a samba share. Annoyingly permissions look fine but I cannot seem to be able to either see the share on my network from other machines or connect to it. Even using the servers IP address. Any advice? Or am I just missing something obvious. My config is below.
samba.conf
[lspace] valid users = david, steff, tracey, smbguest, @sambashare guest account = comment = Lspace media share writeable = yes force group = sambashare path = /media/data read list = smbguest write list = david, steff, tracey
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

On Wed, 28 Jan 2015 21:31:20 +1300, David Nicholls wrote:
Annoyingly permissions look fine but I cannot seem to be able to either see the share on my network from other machines or connect to it. Even using the servers IP address.
Another diagnostic to try is netstat -nlt which will show which TCP ports have listeners on them. smbd should be listening on ports 139 and 445, with a bind address of 0.0.0.0 (i.e. visible outside the machine). Not sure if both are needed nowadays, but that’s what you get by default.
participants (4)
-
David Nicholls
-
Lawrence D'Oliveiro
-
Noel Villamor
-
Roger Searle