Thanks for taking the time to report this bug in Ubuntu.
I've seen similar issues when using the following configuration:
bind interfaces only = yes
This causes samba to only bind to selected interfaces rather than
0.0.0.0 - as it starts early in the boot process this fails as its not
guaranteed that all network interfaces have started when smbd does:
start on (local-filesystems and net-device-up)
When you restart smbd after boot the network interfaces have started so
all works OK.
I would suggest that you either reconfigure samba to listen more
generically or add a upstart stanza to /etc/init/smbd.override:
start on (local-filesystems and net-device-up IFACE=eth0)
You will need to change this to fit your configuration - i.e. which
network interface provides 192.168.0.0/24. For more information see
'man 5 init'.
I'm going to mark the bug as 'Invalid' as I think its specific to your
local samba configuration. If you think this is not the case please
comment and mark as 'New'.
Thanks
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/996968
Title:
Samba needs to be stopped and restarted in order to work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
