Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: dilligaf on April 18, 2009, 06:40:52 PM

Title: 7.4 messages log full of smbd errors as follows
Post by: dilligaf on April 18, 2009, 06:40:52 PM

Does anyone know why, or the fix?
Thanks in advance.

Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:get_peer_addr(1224)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   getpeername failed. Error was Transport endpoint is not connected
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:get_peer_addr(1224)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   getpeername failed. Error was Transport endpoint is not connected
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/access.c:check_access(327)
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:get_peer_addr(1224)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   getpeername failed. Error was Transport endpoint is not connected
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   Denied connection from  (0.0.0.0)
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:get_peer_addr(1224)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   getpeername failed. Error was Transport endpoint is not connected
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   Connection denied from 0.0.0.0
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:write_data(562)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Apr 16 09:41:15 wrpcsrvr smbd[28779]: [2009/04/16 09:41:15, 0] lib/util_sock.c:send_smb(761)
Apr 16 09:41:15 wrpcsrvr smbd[28779]:   Error writing 5 bytes to client. -1. (Connection reset by peer)

Title: Re: 7.4 messages log full of smbd errors as follows
Post by: cactus on April 18, 2009, 07:06:30 PM

Quote from: dilligaf on April 18, 2009, 06:40:52 PM

Does anyone know why, or the fix?
Thanks in advance.

A quick google seems to indicate that M$ first tries to contact simultaneously at port 139 and 445 and drops either when a connection has been established on one of them. A common solution suggested would be to pin point the Samba port to 139, using the following setting in the samba configuration file:

Code: [Select]

smb ports = 139
In fact on all my SME Server installations it is like this by default. What do the following commands output on your server?

Code: [Select]

grep -iR 'sme ports' /etc/samba/smb.conf

Code: [Select]

db configuration show smb