write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer

[Torsten]

Hello Jose!

We have had / got the same messages. Samba 3 uses both port 139 and 445. 
  So using Windows 2000 or better the computer tries to connect to both 
ports and just drops one using "RST". Hence samba still things the 
client is there and needs a little bit of time to sort this out.

As we do not use Port 445 (new one) we just disabled this and got rid of 
all the messages.

Nevertheless it is nothing to worry about - if you do not mind you log 
being filled up with things you can ignore this.


-- Torsten.


Jose Espejo wrote:

>hi Kristis, 
> 
>did you ever find out about the fix for the following problem, I'm
>having the exact same thing.
>******************
>Hello,
>
>I'm receiving the following error message using samba3-alpha23:
>
>[2003/07/16 08:58:06, 0] lib/util_sock.c:get_socket_addr(878)
>  getpeername failed. Error was Transport endpoint is not connected
>[2003/07/16 08:58:06, 0] lib/util_sock.c:write_socket_data(384)
>  write_socket_data: write failure. Error = Connection reset by peer
>[2003/07/16 08:58:06, 0] lib/util_sock.c:write_socket(408)
>  write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection
>reset by peer
>[2003/07/16 08:58:06, 0] lib/util_sock.c:send_smb(569)
>************
> 
>Thanks
>J
>
>  
>