Samba error: write_socket_data: write failure. Error = Connection reset by peer

[Ratzie]

Red Hat ES 3.0
Samba 3.0.9

We have been getting this from the start.
And these errors are very frequent.
1st how to fix the errors
or..
2nd How to change the facility on the smb daemon to a lower priority.

Jun 5 08:05:03 samantha smbd[7789]: [2006/06/05 08:05:03, 0] lib/util_sock.c:get_peer_addr(1000)
Jun 5 08:05:03 samantha smbd[7789]: getpeername failed. Error was Transport endpoint is not connected
Jun 5 08:05:03 samantha smbd[7789]: [2006/06/05 08:05:03, 0] lib/util_sock.c:write_socket_data(430)
Jun 5 08:05:03 samantha smbd[7789]: write_socket_data: write failure. Error = Connection reset by peer
Jun 5 08:05:03 samantha smbd[7789]: [2006/06/05 08:05:03, 0] lib/util_sock.c:write_socket(455)
Jun 5 08:05:03 samantha smbd[7789]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Jun 5 08:05:03 samantha smbd[7789]: [2006/06/05 08:05:03, 0] lib/util_sock.c:send_smb(647)
Jun 5 08:05:03 samantha smbd[7789]: Error writing 4 bytes to client. -1. (Connection reset by peer)
Jun 5 08:05:06 samantha smbd[7791]: [2006/06/05 08:05:06, 0] lib/util_sock.c:get_peer_addr(1000)
Jun 5 08:05:06 samantha smbd[7791]: getpeername failed. Error was Transport endpoint is not connected
Jun 5 08:05:06 samantha smbd[7791]: [2006/06/05 08:05:06, 0] lib/util_sock.c:write_socket_data(430)
Jun 5 08:05:06 samantha smbd[7791]: write_socket_data: write failure. Error = Connection reset by peer

[Ken Grabowski]

This could be a name resolution problem. Make sure both systems involved can resolve the host name and I.P. address. Domain name service should be configured to give both forward and backward name resolution for all the hosts involved.

If you are not using DNS, then make sure the correct names and I.P. are listed in both systems /etc/hosts files.

[Ratzie]

i will tackle this later, still have not found an answer