You see, what i mean jerry, with the 0.0.0.0 thing!!
i think the getpeer error comes from
samba trying to connect to 0.0.0.0 instead of the
actual ip adress.
-----------------------------------------------------
Collen Blijenberg (Montessori Lyceum Herman Jordan)
Tuesday, April 13, 2004, 2:43:50 PM, you wrote:
MWC> could these errors be avoided? I am using samba-3.0.2
MWC> [2004/04/05 10:25:11, 0] lib/util_sock.c:get_peer_addr(952)
MWC> getpeername failed. Error was Transport endpoint is not connected
MWC> Denied connection from (0.0.0.0)
MWC> [2004/04/05 10:25:11, 1] smbd/process.c:process_smb(883)
MWC> [2004/04/05 10:25:11, 0] lib/util_sock.c:get_peer_addr(952)
MWC> getpeername failed. Error was Transport endpoint is not connected
MWC> Connection denied from 0.0.0.0
MWC> [2004/04/05 10:25:11, 0] lib/util_sock.c:write_socket_data(388)
MWC> write_socket_data: write failure. Error = Connection reset by peer
MWC> [2004/04/05 10:25:11, 0] lib/util_sock.c:write_socket(413)
MWC> write_socket: Error writing 5 bytes to socket 16: ERRNO = Connection
MWC> reset by
MWC> peer
MWC> [2004/04/05 10:25:11, 0] lib/util_sock.c:send_smb(605)
MWC> Error writing 5 bytes to client. -1. (Connection reset by peer)
MWC> --
MWC> .~. http://toylet.homeip.net
MWC> / v \ Linux 2.4.22-xfs
MWC> /( _ )\ 8:42pm up 3 days 23:01
MWC> ^ ^ load average: 1.18 1.12 1.05