I have samba-server-3.3.10-0.1.101mdk installed and I get the following errors
Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:get_peer_addr(1000) Jan 27 22:12:13 test smbd[5268]: getpeername failed. Error was Transport endpoint is not connected Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:write_socket_data(430) Jan 27 22:12:13 test smbd[5268]: write_socket_data: write failure. Error = Connection reset by peer Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:write_socket(455) Jan 27 22:12:13 test smbd[5268]: write_socket: Error writing 4 bytes to socket 23: ERRNO = Connection reset by peer Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:send_smb(647) Jan 27 22:12:13 test smbd[5268]: Error writing 4 bytes to client. -1. (Connection reset by peer) I have installed a second server to test and I get the same errors Samba seems to work OK, but if I am writing to af database at the same time as the error occurs the database gets corrupted. So the connection seems to be broken for a short time. I don't like this behavior, I had not something like it with Samba ver. 2.x Is it a bug in Samba? Have I misconfigured Samba or the network? What can I do? Bj�rn Fahn�e [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
