[Samba] Bringing up interface causes smbd to become unresponsive on that subnet
Jeremy Allison
jra at samba.org
Mon Apr 30 21:04:37 MDT 2012
On Mon, Apr 30, 2012 at 05:12:18PM -0400, Tony Markel wrote:
> This is a strange problem I can't seem to wrap my head around.
>
> I have a server with 2 interfaces. Samba is serving happily on one, and
> will remain on a single interface (eth0, subnet A(/22), vlan 101). I wish
> to bring up a second interface (eth1, subnet B(/24), vlan 102) that will be
> serving up nfs and ssh traffic only. Currently, Samba will process
> requests from any computer on the public internet.
>
> Now, before I bring up the second interface on subnet B, I modify my
> smb.conf to bind to eth0, and I speficy the netmasks of subnet A and B.
>
> The problem is this:
> When I bring up eth1, subnet B cannot access the service. When I take it
> down, normal service resumes.
What does "cannot access the service" mean ? How exactly does it fail ?
More information about the samba
mailing list