Hi,

I just installed Samba 3.0.4 on a Solaris 2.6 server. Everything seems to go
OK, with people connecting to all shares without any problem. But when
looking at the log.smbd file I see from time to time the following serie of
errors:

[2004/05/25 16:01:43, 0] lib/util_sock.c:get_peer_addr(978)
getpeername failed. Error was Transport endpoint is not connected
[2004/05/25 16:01:43, 1] lib/util_sock.c:get_peer_name(937)
Gethostbyaddr failed for 0.0.0.0
[2004/05/25 16:01:43, 0] lib/util_sock.c:get_peer_addr(978)
getpeername failed. Error was Transport endpoint is not connected
[2004/05/25 16:01:43, 0] lib/access.c:check_access(328)
[2004/05/25 16:01:43, 0] lib/util_sock.c:get_peer_addr(978)
getpeername failed. Error was Transport endpoint is not connected
[2004/05/25 16:01:43, 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 (0.0.0.0)
[2004/05/25 16:01:43, 1] smbd/process.crocess_smb(883)
[2004/05/25 16:01:43, 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/05/25 16:01:43, 0] lib/util_sock.c:write_socket_data(413)
write_socket_data: write failure. Error = Broken pipe
[2004/05/25 16:01:43, 0] lib/util_sock.c:write_socket(438)
write_socket: Error writing 5 bytes to socket 6: ERRNO = Broken pipe
[2004/05/25 16:01:43, 0] lib/util_sock.c:send_smb(630)
Error writing 5 bytes to client. -1. (Broken pipe)

(the last two entries can vary about the number of bytes and the socket
number)

None of the users has complained at all, so I imagine those erros don't
cause any "visible" effect on the user side. I can't find any clue about
what's causing this kind of incidences. Maybe are they "normal" and due to
some "bad" action made by some user? I really don't know what to look for...

Any help will be welcome.

Thanks!

Toni