From: Justin Piszcz on
Hello,

After upgrading a host from XP/32 to Windows 7/64, I see the following entries
in the logs, what is the root cause of this issue?

Nov 14 10:10:18 l1 smbd[6174]: getpeername failed. Error was Transport endpoint is not connected
Nov 14 10:10:18 l1 smbd[6174]: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] smbd/process.c:62(srv_send_smb)
Nov 14 10:10:18 l1 smbd[6174]: Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] lib/util_sock.c:738(write_data)
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] lib/util_sock.c:1491(get_peer_addr_internal)
Nov 14 10:10:18 l1 smbd[6174]: getpeername failed. Error was Transport endpoint is not connected
Nov 14 10:10:18 l1 smbd[6174]: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] smbd/process.c:62(srv_send_smb)
Nov 14 10:10:18 l1 smbd[6174]: Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] lib/util_sock.c:738(write_data)
Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18, 0] lib/util_sock.c:1491(get_peer_addr_internal)

Nov 17 13:26:23 l1 smbd[19701]: [2009/11/17 13:26:23, 0] lib/util_sock.c:539(read_fd_with_timeout)
Nov 17 13:26:23 l1 smbd[19701]: [2009/11/17 13:26:23, 0] lib/util_sock.c:1491(get_peer_addr_internal)
Nov 17 13:26:23 l1 smbd[19701]: getpeername failed. Error was Transport endpoint is not connected
Nov 17 13:26:23 l1 smbd[19701]: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.

Justin.

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba