[Samba] Very weird access problems from win2k3 to samba 3.x

[Jeremy Allison]

On Fri, Sep 24, 2004 at 04:22:16PM -0400, Eli wrote:
> I've got a samba 3.0.5 (I can't get 3.0.6 or 3.0.7 to compile - I'll get to
> that later) server running and it *appears* to be working just fine.
> 
> >From the 2k3 system in question, if I open an explorer window I can access
> the server via UNC just fine, no errors or anything on the Windows side.
> 
> On the Samba side though, once in a while I get this in the samba.log file
> (and I'm sure you've all seen this countless times before):
> 
> [2004/09/18 02:00:19, 0] lib/access.c:check_access(328)
> [2004/09/18 02:00:19, 0] lib/util_sock.c:get_peer_addr(978)
>   getpeername failed. Error was Transport endpoint is not connected
>   Denied connection from  (0.0.0.0)
> [2004/09/18 02:00:19, 1] smbd/process.c:process_smb(883)
> [2004/09/18 02:00:19, 0] lib/util_sock.c:get_peer_addr(978)
>   getpeername failed. Error was Transport endpoint is not connected
>   Connection denied from 0.0.0.0
> [2004/09/18 02:00:19, 0] lib/util_sock.c:write_socket_data(413)
>   write_socket_data: write failure. Error = Connection reset by peer
> [2004/09/18 02:00:19, 0] lib/util_sock.c:write_socket(438)
>   write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset
> by peer
> [2004/09/18 02:00:19, 0] lib/util_sock.c:send_smb(630)
>   Error writing 5 bytes to client. -1. (Connection reset by peer)

Is this on Linux ? If so are you using sendfile ? If so
try setting "use sendfile = no".

Jeremy.