I've noticed that along with bad (or terrible) write performance I see lots of these in log.smb [1999/08/19 16:14:31, 0] lib/util_sock.c:write_socket_data(570) write_socket_data: write failure. Error = Broken pipe and in compiling I saw these messages, which I later thought might be related: smbd/oplock.c: In function `open_oplock_ipc': smbd/oplock.c:98: warning: passing arg 3 of `ngetsockname' from incompatible pointer type smbd/oplock.c: In function `receive_local_message': smbd/oplock.c:243: warning: passing arg 6 of `nrecvfrom' from incompatible pointer type lib/util_sock.c: In function `is_a_socket': lib/util_sock.c:54: warning: passing arg 5 of `getsockopt' from incompatible pointer type lib/util_sock.c: In function `read_udp_socket': lib/util_sock.c:179: warning: passing arg 6 of `nrecvfrom' from incompatible pointer type lib/util_sock.c: In function `client_name': lib/util_sock.c:1021: warning: passing arg 3 of `ngetpeername' from incompatible pointer type lib/util_sock.c: In function `client_addr': lib/util_sock.c:1067: warning: passing arg 3 of `ngetpeername' from incompatibl nmbd/nmbd.c:89: warning: duplicate `volatile' *** bin/rpcclient removed My platform is an IBM RS/6000 running AIX 4.2.1.0, and other than this samba is quite stable. On my Linux boxes I dont' seem to see anything similair.