Need to restart samba to access a shared folder

Xi0N · 2011-10-09 15:18:28

So, that is what happens to me just now, i have to restart samba once the system boots up so i can access any share.

# 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 (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba, 
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the 
# Samba-Guide which is generated daily and can be downloaded from: 
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash) 
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# 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]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = share
   map to guest = Bad User

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;hosts allow = 192.168.5. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = nobody

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# 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.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes 

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# 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

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
;[homes]
;   comment = Home Directories
;   browseable = no
;   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
;[printers]
;   comment = All Printers
;   path = /var/spool/samba
;   browseable = no
;# Set public = yes to allow user 'guest account' to print
;   guest ok = no
;   writable = no
;   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.


[Shared]
   path = /home/Shared
   available = yes
   browsable = yes
   public = yes
   writable = yes

[Multimedia]
   path = /home/Multimedia
   available = yes
   browsable = yes
   public = yes
   writable = yes



# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

I use networkmanager, and samba is the last daemon to start....

Strike0 · 2011-10-09 20:17:55

I dont use samba, but maybe just letting it start in the background (by adding a "@" before the daemon in rc.conf) helps?

Xi0N · 2011-10-09 20:19:20

Some other way to share files via network with windows machines?

I will try the @ thingy..... see if it works....

skanky · 2011-10-10 09:27:40

I have the same problem and already start samba in the background. I have been playing around with it and found that I need to close Explorer (on the windows box) and re-open it after the restart before it will connect. I'm going to keep looking and will post back here if I find anything.

Sean-Der · 2011-10-10 11:50:59

Does your network go live before OR after samba starts? Samba starting without an active interface MAY cause issues, just a troubleshooting guess.

skanky · 2011-10-10 13:14:46

That's a good point. Mine is started after the networking stuff, but they're all done background as well. As far as I can remember, there was no change there to start-up listing in rc.conf when this started happening. Though as there may have been a Samba change something may have affected it. I'll change it to make sure the networking is up before samba starts.

Strike0 · 2011-10-10 13:25:35

How about you go to

sudo gnome-session-properties

and add an entry for samba there, perhaps with restart or a wait before starting?

skanky · 2011-10-10 13:32:59

Strike0 wrote:

How about you go to
sudo gnome-session-properties
and add an entry for samba there, perhaps with restart or a wait before starting?

Might work for the OP, but not for me as I don't use gnome. I have written a script to restart it...and I could look to see whether adding it to somewhere like bash profile will do, but I'd rather fix the issue - esp. if it's configuration. Thanks for the suggestion though.

Xi0N · 2011-10-10 13:38:20

Does not work for me as well...
I use the desktop, but sometimes, while im out, my wife switches the pc on and just connects, while the login session is still there and noone did log-in.....
I understand it can be a workaround, but this is not supposed to be the way samba behaves......

Strike0 · 2011-10-10 21:49:26

Yes, both very valid reasons I suppose.
You two have seen and followed:
https://wiki.archlinux.org/index.php/Sa … e_by_other
I am sure. I dont have a further suggestion currently.

Last edited by Strike0 (2011-10-10 21:50:41)

Xi0N · 2011-10-10 21:58:14

Yes, I followed those steps.... no luck....

skanky · 2011-10-11 08:36:26

Yes thanks - I don't use network but netcfg, but I tried the net-auto* daemons not backgrounded and it still didn't work. Thanks for the suggestions.

Xi0N · 2011-10-11 08:46:56

I have an idea that came to my mind now... im at work so i cannot test it right now... so, if anyone wants to give it a try for me....

If the problem is that the network is not up while samba comes live and thus, samba does not know which is the network interface it should listen to for connections, maybe we can change something in this directive at /etc/samba/smb.conf ... and tell samba directly which is the ip/interface to listen to...

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

It's a long shot, but i don't really know what else to do....

skanky · 2011-10-11 09:55:24

Okay, I've done some testing. I have upped the log level and it seems this is the error:

[2011/10/11 10:49:04,  3] nmbd/nmbd.c:962(main)
  Opening sockets 137
[2011/10/11 10:49:04,  3] ../lib/util/util_net.c:70(interpret_string_addr_internal)
  interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0 [Address family for hostname not supported]
[2011/10/11 10:49:04,  0] nmbd/nmbd.c:689(open_sockets)

Looking around this seems to be a timing issue. I have changed the order of the samba start in daemons to be as late after the networking stuff as possible, and I have specified the interfaces and ip addresses (I used dhcp with fixed leases), but I'm still getting this error. This problem has come up elsewhere, including Debian, here is the bug there:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576415

I didn't read the patch but it looks to me that they've patched samba to allow an interface specification of network manager, to get it to wait for that to finish. The big issue seems to be that the network connections could come up some time after the networking initialisation is finished (I'm probably putting this across poorly), so we can't rely on the previous process to finish.

Anyhoo, I'll keep looking...

skanky · 2011-10-11 11:04:43

Okay, I've moved my samba start-up to my post-up command in my relevant netcfg profile.
I haven't been able to test it yet as I rebooted and got dhcp lease failures and had to wait 20 minutes or so before I could connect that ic. I'll see if it fixes it when I start the machine tomorrow am.

skanky · 2011-10-12 08:40:36

Right that seems to have solved it for me. I had forgotten to tie samba to the interface that starts it, but once that was done, it worked the next two starts.
This is effectively the same as Strike0 suggested, and shows that Sean-Der's suggestion was correct, so thank you very much to both.

This fix is actually pretty good, despite my earlier reservations, as I've tied samba to eth0, and I only want it running when I'm at my desk anyway.

Xi0N · 2011-10-12 14:51:28

skanky wrote:

Right that seems to have solved it for me. I had forgotten to tie samba to the interface that starts it, but once that was done, it worked the next two starts.
This is effectively the same as Strike0 suggested, and shows that Sean-Der's suggestion was correct, so thank you very much to both.
This fix is actually pretty good, despite my earlier reservations, as I've tied samba to eth0, and I only want it running when I'm at my desk anyway.

I don't get it, so what did you finally do to get it working?

skanky · 2011-10-12 15:07:35

Firstly, do you use netcfg?

If not, then I'm not sure whether you can do what I'm doing but with a slightly different mechanism. It might be worth looking though if what you use has something similar.

Anyway, in netcfg profiles, you have the ability to execute commands before or after an interface is up or down. On my laptop (which has my samba share), I have moved the samba daemon from rc.conf, and instead call

rc.d start samba

in my POST_UP section for my wired (eth0) interface. This means that nmbd gets started after that interface is connected. I have also specified eth0 in the interfaces entry of smb.conf (thank you for pointing that entry out).

This does have the added bonus that my samba share is not available when I'm away from my desk - I only use it to share info. with a Windows desktop machine at work.

Xi0N · 2011-10-12 15:41:53

Yeah, but i think this is not compatible with networkmanager, which I use... anyway, thanks

skanky · 2011-10-12 15:58:11

Try this: https://wiki.archlinux.org/index.php/Ne … Dispatcher

Xi0N · 2011-10-12 18:36:15

skanky wrote:

Try this: https://wiki.archlinux.org/index.php/Ne … Dispatcher

I'll try... thanks!!!

hseara · 2011-10-30 10:52:36

Hi I have exactly the same problem. I'm pretty sure that somehow is related with the hardware of the computer, as only one of my computers seems to be affected by this problem. I'm I a networkmanager user. I have solved the issue by taking away samba from the daemons array in /etc/rc.conf (in fact I putted a ! in front what is the same). An the following the suggestion up. I have made a script "/etc/NetworkManager/dispatcher.d/30_samba":

#!/bin/sh

INTERFACE=$1 # The interface which is brought up or down
STATUS=$2 # The new state of the interface

case "$STATUS" in
    'up') # $INTERFACE is up
	exec /etc/rc.d/samba start
	;;
    'down') # $INTERFACE is down
	# Check for active interface and down if no one active
	if [ ! `nm-tool|grep State|cut -f2 -d' '` = "connected" ]; then
		exec /etc/rc.d/samba stop
	fi
	;;
esac

as indicated in wiki networkmanager and pointed above. Finally, I set the permission for "30_samba" scrip to 755 and the ownership to root:root. Now it works.

Note: If I leave the samba daemon in the array or background it I get a weird problem as only the nmbd but not smbd in up after reboot.

I hope it helps to others. Still I found very weird this behaviour. It has been going on for a long while with this computer although I was lazy to dig in the reasons until now. I will really appreciate if someone more skilful could have a look to the problem.

Last edited by hseara (2011-10-30 10:55:13)

nomphy · 2012-03-04 22:48:55

It seems that samba needs to have an active network interface before it can do its thing. Letting NetworkManager start/stop samba seems to have solved the problem for me. Thanks hseara!

Arch Linux

#1 2011-10-09 15:18:28

Need to restart samba to access a shared folder

#2 2011-10-09 20:17:55

Re: Need to restart samba to access a shared folder

#3 2011-10-09 20:19:20

Re: Need to restart samba to access a shared folder

#4 2011-10-10 09:27:40

Re: Need to restart samba to access a shared folder

#5 2011-10-10 11:50:59

Re: Need to restart samba to access a shared folder

#6 2011-10-10 13:14:46

Re: Need to restart samba to access a shared folder

#7 2011-10-10 13:25:35

Re: Need to restart samba to access a shared folder

#8 2011-10-10 13:32:59

Re: Need to restart samba to access a shared folder

#9 2011-10-10 13:38:20

Re: Need to restart samba to access a shared folder

#10 2011-10-10 21:49:26

Re: Need to restart samba to access a shared folder

#11 2011-10-10 21:58:14

Re: Need to restart samba to access a shared folder

#12 2011-10-11 08:36:26

Re: Need to restart samba to access a shared folder

#13 2011-10-11 08:46:56

Re: Need to restart samba to access a shared folder

#14 2011-10-11 09:55:24

Re: Need to restart samba to access a shared folder

#15 2011-10-11 11:04:43

Re: Need to restart samba to access a shared folder

#16 2011-10-12 08:40:36

Re: Need to restart samba to access a shared folder

#17 2011-10-12 14:51:28

Re: Need to restart samba to access a shared folder

#18 2011-10-12 15:07:35

Re: Need to restart samba to access a shared folder

#19 2011-10-12 15:41:53

Re: Need to restart samba to access a shared folder

#20 2011-10-12 15:58:11

Re: Need to restart samba to access a shared folder

#21 2011-10-12 18:36:15

Re: Need to restart samba to access a shared folder

#22 2011-10-30 10:52:36

Re: Need to restart samba to access a shared folder

#23 2012-03-04 22:48:55

Re: Need to restart samba to access a shared folder

Board footer