[Samba] Bringing up interface causes smbd to become unresponsive on that subnet

Tony Markel tmarkel at umich.edu
Tue May 1 04:29:52 MDT 2012

>From a windows client I get "network path not found" as soon interface is
brought up, by either host name or ip address, but only on computers on the
same subnet as that interface.  The log (finally) tells a story I can't
find a solution to:

May  1 06:16:41 nt-filer01 smbd[15036]: [2012/05/01 06:16:41.456860,  0]
May  1 06:16:41 nt-filer01 smbd[15036]:   getpeername failed. Error was
Transport endpoint is not connected
May  1 06:16:41 nt-filer01 smbd[15036]:   read_fd_with_timeout: client read error = Connection reset by peer.
May  1 06:16:43 nt-filer01 smbd[19573]: [2012/05/01 06:16:43.169215,  0]

As soon as I take the interface down, all is normal.

Thanks for your help,


On Mon, Apr 30, 2012 at 11:04 PM, Jeremy Allison <jra at samba.org> wrote:

> 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