[Samba] Transport endpoint is not connected

Stefan G. Weichinger monitor at oops.co.at
Sun Mar 6 13:42:21 GMT 2005


Hello, I tried to google this, but haven't found anything really
helpful so far.

I get stuff like this at one Samba-3.0.9-Domain-Member-Server:

> [2005/03/06 13:30:47, 1] smbd/service.c:make_connection_snum(647)
>   fre2003 (192.168.86.11) connect to service users initially as user fre (uid=1006, gid=1000) (pid 31447)
> [2005/03/06 13:31:57, 1] smbd/service.c:close_cnum(835)
>   fre2003 (192.168.86.11) closed connection to service users
> [2005/03/06 14:02:19, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
> [2005/03/06 14:02:19, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
> [2005/03/06 14:02:19, 0] lib/access.c:check_access(328)
> [2005/03/06 14:02:19, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
>   Denied connection from  (0.0.0.0)
> [2005/03/06 14:02:19, 1] smbd/process.c:process_smb(1084)
> [2005/03/06 14:02:19, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
>   Connection denied from 0.0.0.0
> [2005/03/06 14:02:19, 0] lib/util_sock.c:write_socket_data(430)
>   write_socket_data: write failure. Error = Connection reset by peer
> [2005/03/06 14:02:19, 0] lib/util_sock.c:write_socket(455)
>   write_socket: Error writing 5 bytes to socket 23: ERRNO = Connection reset by peer
> [2005/03/06 14:02:19, 0] lib/util_sock.c:send_smb(647)
>   Error writing 5 bytes to client. -1. (Connection reset by peer)
> [2005/03/06 14:02:20, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
> [2005/03/06 14:02:20, 0] lib/access.c:check_access(328)
> [2005/03/06 14:02:20, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
>   Denied connection from  (0.0.0.0)
> [2005/03/06 14:02:20, 1] smbd/process.c:process_smb(1084)
> [2005/03/06 14:02:20, 0] lib/util_sock.c:get_peer_addr(1136)
>   getpeername failed. Error was Transport endpoint is not connected
>   Connection denied from 0.0.0.0
> [2005/03/06 14:02:20, 0] lib/util_sock.c:write_socket_data(430)
>   write_socket_data: write failure. Error = Connection reset by peer
> [2005/03/06 14:02:20, 0] lib/util_sock.c:write_socket(455)
>   write_socket: Error writing 5 bytes to socket 23: ERRNO = Connection reset by peer
> [2005/03/06 14:02:20, 0] lib/util_sock.c:send_smb(647)
>   Error writing 5 bytes to client. -1. (Connection reset by peer)

The section [global]:

> [global]
>    workgroup = WKGP
>    netbios name = MAIL
>    server string = Samba
>    interfaces = eth* lo
>    map to guest = Bad User
>    security = domain
>    password server = NTSERVER
>    passdb backend = tdbsam
> 
>    encrypt passwords = yes
>    name resolve order = wins bcast hosts
> 
>    domain master = no
>    domain logons = no
>    local master = no
>    preferred master = no
>    os level = 0
> 
>    load printers = no
>    hosts allow = 192.168.86. 172.32.99. 127.
>    wins support =  yes
>    log level = 1
> 
>    oplocks = no
>    level2 oplocks = no
>    kernel oplocks = no

This is an up-to-date Suse 9.2 Pro machine, with the rpm
samba-3.0.9-2.3 installed. (The 3.0.11 rpm didn't make much
difference). There is a NT PDC (= NTSERVER) in the LAN which does not
provide WINS, the WINS-Server-Address (= Samba-server) is distributed
via DHCP.

Any hints for me?
-- 
Regards,
Stefan



More information about the samba mailing list