Write failure - broken pipe errors in logs

[Joe Newby]

Have searched through the mailing list archives and have seen this show up a
couple of other times, but no answers seem to be forthcoming.  I am runing
Samba 2.0.6 on a Red Hat 6.0 system and keep seeing the following errors in
the logs:
lib/util_sock.c:write_socket_data(537) write_socket_data:  write failure.
Error = broken pipe
followed by:
lib/util_sock.c:writewrite_socket(563) write_socket:  Error writing 4 bytes
of data to socket 5:  ERRNO = Broken pipe

What's going on here and how can I fix it.  It doesn't seem to cause any
problems, but I don't like seeing these kind of eror messages.  I'm using
share level security and have enabled the TCP_NODELAY socket option as
described in the documentation.

At present, there are about 15 people that use Samba to access Excel
spreadsheets and Access databases.  Could this be causing the problem, or is
there something I can configure to stop this?

Thanks,

Joe Newby
Network Admin
Stone County Ironworks