[Samba] Error was Transport endpoint is not connected

robert.gehr robert.gehr at baumann-gmbh.de
Mon Oct 11 06:57:10 MDT 2010

Hello All

I used to back up a Mssql database (about 55GB) to a samba share without
any problems. The samba server "Server-A" was running version 3.4.7
We just got one of those "Netgear ReadyNas3200" things and I tried to
backup up to a share there which sometimes works and sometimes not in
wich case I get the following error:


[2010/10/08 21:32:26.937834,  0]
[2010/10/08 21:32:26.966404,  0]
  getpeername failed. Error was Transport endpoint is not connected
  read_fd_with_timeout: client read error = Connection reset by


The samba version on the ReadyNas is 3.5.4

On the windows side nothing has changed apart form the destination to
the new share. The ReadyNas performs pretty well and I do not get any
network errors or otherwise. To rule out some network problem I exported
a nfs share on the ReadyNas which I mounted on "Server-A", created a
share on "Server-A" that points to the nfs-mount and ran a backup. No
problems and no errors.

Any ideas which buttons to push in order to get a reliable backup going
again? From what I read this usually points to a problem on the client
side but nothing has changed there. I could of course use the
"Server-A:smb->nfs-mount:ReadyNas" solution but this is not what I want.



More information about the samba mailing list