> My money is on the switch :-). This is a classic "my tcp connection > went away and I don't know why" error message. > > Jeremy.
Your money was invested well ;-) In our situation the problems disappeared for now (cross the fingers!) with a new hub, what makes sense because of a fine working Win2003 Server x64 + Samba in an other network. Still got these (but doesnt' seem to harm): [2006/03/10 13:20:35, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Transport endpoint is not connected [2006/03/10 13:20:35, 0] lib/access.c:check_access(328) [2006/03/10 13:20:35, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Transport endpoint is not connected [2006/03/10 13:20:35, 1] smbd/process.c:process_smb(1187) [2006/03/10 13:20:35, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Transport endpoint is not connected [2006/03/10 13:20:35, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer [2006/03/10 13:20:35, 0] lib/util_sock.c:send_smb(765) Error writing 5 bytes to client. -1. (Connection reset by peer) Thank you Jeremy & Robert! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
