errors in log.smbd

i used cat /var/log/samba/log.smbd.log and i getting these messages
can someone explain it to me like where i have made mistake

**[2009/05/04 10:00:07, 0] lib/util_sock.c:write_data(1059)
[2009/05/04 10:00:07, 0] lib/util_sock.c:get_peer_addr_internal(1607)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2009/05/04 10:00:07, 0] smbd/process.c:srv_send_smb(74)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2009/05/04 10:10:57, 1] smbd/service.c:close_cnum(1405)
bch (::ffff:10.4.97.175) closed connection to service users
[2009/05/04 10:10:57, 1] smbd/service.c:close_cnum(1405)
dbm58nf1 (::ffff:10.4.97.7) closed connection to service users
[2009/05/04 10:13:40, 0] smbd/server.c:main(1210)
smbd version 3.2.7-11.2.1-2080-SUSE-CODE11 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/05/04 10:15:06, 0] lib/util_sock.c:write_data(1059)
[2009/05/04 10:15:06, 0] lib/util_sock.c:get_peer_addr_internal(1607)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2009/05/04 10:15:06, 0] smbd/process.c:srv_send_smb(74)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2009/05/04 10:27:12, 0] lib/util_sock.c:write_data(1059)
[2009/05/04 10:27:12, 0] lib/util_sock.c:get_peer_addr_internal(1607)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2009/05/04 10:27:12, 0] smbd/process.c:srv_send_smb(74)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
**

On Mon May 4 2009 10:46 am, davesal wrote:

>
> i used cat /var/log/samba/log.smbd.log and i getting these messages
> can someone explain it to me like where i have made mistake
>
<snip>
> [2009/05/04 10:00:07, 0] lib/util_sock.c:get_peer_addr_internal(1607)
> getpeername failed. Error was Transport endpoint is not connected
> write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
> [2009/05/04 10:00:07, 0] smbd/process.c:srv_send_smb(74)
> Error writing 4 bytes to client. -1. (Transport endpoint is not
> connected)
<snip>
davesal;

These are generally innocuous. Windows XP will try to connect on both ports
139 and 445. Once an XP client connects on one of these ports, it silently
drops the other. If you want to get rid of the error in your log, or just
verify my answer, add the following parameter to the Global Section
of /etc/samba/smb.conf , then restart samba.


smb ports = 139

This will keep Samba from lessening on port 445. To restart Samba:


su
rcsmb restart


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

thanks its working

On Mon May 4 2009 12:15 pm, PV wrote:

<snip>
> lessening
should be “listening”

P. V.
“We’re all in this together, I’m pulling for you.” Red Green