[Samba] Question about Samba connections for 3.0 and 3.2

William Jojo w.jojo at hvcc.edu
Thu Sep 25 13:12:56 GMT 2008

What typically causes the following in the log?

[2008/09/25 09:07:14, 0] smbd/server.c:open_sockets_smbd(527)
  open_sockets_smbd: accept: Software caused connection abort


I know that these are created due to accepting connections on both 445 and 139:

[2008/09/25 09:07:24, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Socket is not connected
[2008/09/25 09:07:24, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client Error Broken pipe
[2008/09/25 09:07:24, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Broken pipe)

The 445 is answered first by Samba, Windows closes the 139 connection and Samba then tries to reply to the client on the 139 connection which is no longer connected. Is this correct?


More information about the samba mailing list