[Samba] Curious Transport Endpoint message

[David M Noriega]

I have a curious message I get repeatedly every so often on a samba
domain member that serves up our network's home and group shares.

[2009/07/07 12:24:56,  0] lib/util_sock.c:read_socket_with_timeout(939)
[2009/07/07 12:24:56,  0] lib/util_sock.c:get_peer_addr_internal(1607)
  getpeername failed. Error was Transport endpoint is not connected
  read_socket_with_timeout: client 0.0.0.0 read error = Transport
endpoint is not connected.

I dont know of any reason for this and this doesnt seems to impact
performance. Its just a slow day and thought I'd fix something that
isnt broken

smb.conf:

[Global]
        workgroup = X.X.X
        server string = XXX %v
        security = domain
        password server = *
        lanman auth = Yes
        encrypt passwords = yes
        enable privileges = yes
        loglevel = 0
        syslog = 0
        name resolve order = wins bcast host
        deadtime = 5
        os level = 8
        local master = No
        domain master = No
        wins server = x.x.x.x
        remote announce = x.x.x.x/X.X.X
        interfaces = ce0
        hosts allow = xxx.xxx.0.0/255.255.0.0
        hosts deny = ALL


-- 
Personally, I liked the university. They gave us money and facilities,
we didn't have to produce anything! You've never been out of college!
You don't know what it's like out there! I've worked in the private
sector. They expect results. -Ray Ghostbusters