[Samba] Can't connect Windows 7 client to Samba 3.3.12 on AIX

[Rowland Penny]

On Wed, 4 Jan 2017 15:58:39 -0300
Andres Tarallo via samba <samba at lists.samba.org> wrote:

> Hi !!!
> 
> I've Samba 3.3.12 running on AIX, I have a few windows 7 using a
> shared resource on that server.
> 
> This is the shared resource definition:
> 
> [shared_disk]
>         comment = shared_disk
>         path = /home2/nfs-chiappe/shared_disk
>         valid users = user1,user2
>         write list = @staff
>         read only = No
>         create mask = 0764
> 
> This particular Windows 7 Computer is driving me crazy. I get this
> errors on the machine log of samba:
> 
> [2017/01/04 16:44:07,  0]
> lib/util_sock.c:read_socket_with_timeout(939) [2017/01/04 16:44:07,
> 0] lib/util_sock.c:get_peer_addr_internal(1676) getpeername failed.
> Error was A socket must be already connected.
> read_socket_with_timeout: client 0.0.0.0 read error = A socket must
> be already connected.. [2017/01/04 16:44:31,  0]
> lib/util_sock.c:read_socket_with_timeout(939) [2017/01/04 16:44:31,
> 0] lib/util_sock.c:get_peer_addr_internal(1676) getpeername failed.
> Error was A socket must be already connected.
> read_socket_with_timeout: client 0.0.0.0 read error = A socket must
> be already connected.. [2017/01/04 16:44:37,  1]
> librpc/ndr/ndr.c:ndr_push_error(493) ndr_push_error(5): Bad char
> conversion [2017/01/04 16:44:37,  0]
> rpc_server/srv_pipe.c:api_rpcTNP(2381) api_rpcTNP: srvsvc:
> SRVSVC_NETSHAREENUMALL failed. [2017/01/04 16:44:49,  0]
> lib/util_sock.c:read_socket_with_timeout(939) [2017/01/04 16:44:49,
> 0] lib/util_sock.c:get_peer_addr_internal(1676) getpeername failed.
> Error was A socket must be already connected.
> read_socket_with_timeout: client 0.0.0.0 read error = A socket must
> be already connected.
> 
> 
> Any ideas are appreciated.
> 
> Andrés

Yes, upgrade Samba, 3.3.x went EOL over 5 years ago, so even if you can
find a bug in your version of Samba, it very unlikely to get fixed.

Rowland