Problem running Samba with IPv4 only network

[Jeremy Allison]

On Fri, Jun 06, 2014 at 02:17:39PM +1000, Amitay Isaacs wrote:
> 
> Thanks Jeremy.  Patch works as far as AD functionality is concerned.  (I am
> using the AD as authentication source for clustered samba.  Only things I
> use from Samba server are domain authentication and DNS.)
> 
> However I still see following errors during start up.
> 
>   /usr/sbin/smbd: smbd version 4.1.8 started.
>   /usr/sbin/smbd: Copyright Andrew Tridgell and the Samba Team 1992-2013
>   Terminating connection - 'wbsrv: wbsrv_call_loop:
> tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED'
>   single_terminate: reason[wbsrv: wbsrv_call_loop:
> tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED]
>   /usr/sbin/smbd: STATUS=daemon 'smbd' finished starting up and ready to
> serve connectionsopen_socket_in(): socket() call failed: Address family not
> supported by protocol
>   /usr/sbin/smbd: smbd_open_once_socket: open_socket_in: Address family not
> supported by protocol
>   /usr/sbin/smbd: open_socket_in(): socket() call failed: Address family
> not supported by protocol
>   /usr/sbin/smbd: smbd_open_once_socket: open_socket_in: Address family not
> supported by protocol
> 
> 
> Do we need to worry about wbsrv failures?

The error messages are to be expected and I
think they're a good thing. They're telling
you you screwed up interface config :-).

Can I have your 'Reviewed-by:' on the patch ?

If so I'll push tomorrow morning and raise
a bug for a 4.1.x back-port.

I'll take a look at the wbsrv message
tomorrow and if it's a problem address
it.

Cheers,

	Jeremy.