[Samba] getpeername failed. Error was Transport endpoint is notconnected (3.0.37)

[Andrew Masterson]

> 
> Hi All,
> 
> I have a Solaris 10 server (Sun Fire T5520) that has recently been patched with
> Samba 3.0.37 but is not able to share any drives to Windows clients. Instead,
> the /var/samba/log/log.smbd is showing the following errros:
>      getpeername failed. Error was Transport endpoint is not connected
>     Denied connection from 0.0.0.0 (0.0.0.0)
>     [2011/03/10 21:10:04, 1] smbd/process.c:(1076)
>     [2011/03/10 21:10:04, 0] lib/util_sock.c:(1224)
>     write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
>     Error writing 5 bytes to client. -1. (Broken pipe)
> 
> It would be very much appreciate some guidances on how to resolve this issue.
> 

This error is very old, and seems to be related to samba binding to multiple ports (139 and 445).  You only need 445 in most modern worlds, unless you're a PDC from what I can tell.  I stuck this in my smb.conf file:

# restrict ports to avoid
# "getpeername failed. Error was Transport endpoint is not connected" and
# "Error writing 4 bytes to client. -1. (Transport endpoint is not connected)"
# errors from port 139 legacy mode - PDC may need 139 open
        smb ports = 445

-=Andrew