Koozali.org: home of the SME Server

7.4 messages log full of smbd errors as follows

Offline dilligaf

  • *
  • 266
  • +0/-0
    • http://www.willcraft.com
7.4 messages log full of smbd errors as follows
« 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)

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: 7.4 messages log full of smbd errors as follows
« Reply #1 on: April 18, 2009, 07:06:30 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
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)