I'm currently investigating an issue like this - basically, a customer
of ours is using Vista SP1, and transferring large files. The
transfer is interrupted - the interruptions appear to correlate to
these entries in samba.log:
sloisn01-1: [2008/01/14 16:33:46, 0, pid=77015, effective(0, 0),
real(0, 0)] lib/util_sock.c:write_data(563)
write_data: write failure in writing to client 10.0.13.40. Error
Broken pipe
sloisn01-1: [2008/01/14 16:33:46, 0, pid=77015, effective(0, 0),
real(0, 0)] lib/util_sock.c:send_smb(1016)
Error writing 4 bytes to client. -1. (Broken pipe)
In my experience, this typically happens when the Windows OS is
unsatisfied with a message returned from Samba, and drops the
connection. In my case, they are also using SMB signing, so it may
also be part of the problem. I'm trying for an internal repro, and
will update the list with my findings. There's also some chance this
is fixed in 3.2.xx builds - have you tried those?
Tx,
Todd
On Jan 10, 2008, at 1:22 AM, Mössler, Michael wrote:
Yesterday i installed then new SP1 RC for Microsoft Vista Enterprise,
Since then I cant connect to our samba server any more.
Samba is configured as ad member, with winbind and idmap backend =
rid.
Has anyone the same Problem ?
Mit freundlichen Grüßen
Michael Mössler
uhb consulting AG
Chiemseering 1
84427 St. Wolfgang
Tel.: 08085/939-131
Fax.: 08085/939-222
Web: www.uhb-consulting.de
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Todd Stecher | Windows Interop Dev
Isilon Systems P +1-206-315-7500 F +1-206-315-7501
www.isilon.com D +1-206-315-7638 M +1-425-205-1180
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
