Comment 5 for bug 996968

Revision history for this message
James Page (james-page) wrote :

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