[Samba] getpeername failed,
Error was Transport endpoint is not connected
H.meijerink
h.meijerink at starinkbv.nl
Thu Jul 7 03:39:19 GMT 2005
Hello,
Using Samba 3.014 on SLES9 on a proliant Xeon server.
All clients (XP) fixed IP addresses,
Ip <> hostname in hosts table.
During the boot of a XP client I receive these messages in the log file's
Can anybody explain why or what is causing this.
Most of the XP clients reporting none of these messages.
Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:get_peer_addr(1150)
Jul 6 12:50:24 server4 smbd[27787]: getpeername failed. Error was
Transport endpoint is not connected
Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket_data(430)
Jul 6 12:50:24 server4 smbd[27787]: write_socket_data: write failure.
Error = Connection reset by peer
Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket(455)
Jul 6 12:50:24 server4 smbd[27787]: write_socket: Error writing 4 bytes
to socket 5: ERRNO = Connection reset by peer
Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:send_smb(647)
Jul 6 12:50:24 server4 smbd[27787]: Error writing 4 bytes to client. -1.
(Connection reset by peer)
Name resolve order in the smb.conf file: lmhosts hosts wins bcast
Thanks
Harry
h.meijerink at starinkbv.nl
More information about the samba
mailing list