SMBD [15295]: getpeername failover. Error was Transport endpoint is not connected

Add the following code to the /etc/samb/smb.conf configuration file:
the SMB ports = 139

restart SMB service # service SMB restart

(PS:

getpeername failed. Error was Transport endpoint is not connected with a real Error. SMB ports=139 Specifies the port number that the SMB service listens on. By default, it listens on both ports 139 and 445. When Windows XP tried to connect, both ports were tested, and finally only one port was selected to use and the other port was disconnected. All SMBS thought it was an error and were recorded.

>
Those entries in log.smbd do not really indicate a problem. They are due to a windows XP machine on local area network which inquires on both ports 445 and 139. Ultimatley, windows XP only uses one of those ports and it disconnects from the other one, which leads to the samba log entry. The log entries can be eliminated by having samba only listen on one of the two ports, as long as your server is not a PDC (Primary Domain Controller)(which mine is). I read somewhere that having samba only listen on one of the ports can cause a reduction in performance.