[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

[Rowland penny]

On 11/06/2019 09:09, Andreas Habel via samba wrote:
> Hi,
>
> after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence - task_server_terminate: [XXXd failed to setup interfaces] error messages in log.samba (I removed a couple of "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." lines for better readability):
>
> [2019/06/11 09:23:47.400171,  0] ../source4/smbd/server.c:448(binary_smbd_main)
>    samba version 4.7.6-Ubuntu started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2017
> [2019/06/11 09:23:47.771969,  0] ../source4/smbd/server.c:620(binary_smbd_main)
>    samba: using 'standard' process model
>   [2019/06/11 09:23:47.777949,  0] ../source4/nbt_server/interfaces.c:205(nbtd_add_socket)
>    Failed to bind to 152.94.0.255:137 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.778059,  0] ../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [nbtd failed to setup interfaces]
> [2019/06/11 09:23:47.782712,  0] ../source4/cldap_server/cldap_server.c:130(cldapd_add_socket)
>    Failed to bind to ipv4:152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.782813,  0] ../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [cldapd failed to setup interfaces]
> [2019/06/11 09:23:47.788484,  0] ../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:88 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788606,  0] ../source4/kdc/kdc-server.c:584(kdc_add_socket)
>    Failed to bind to 152.94.0.106:88 TCP - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788675,  0] ../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [kdc failed to setup interfaces]
>   [2019/06/11 09:23:47.853221,  0] ../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:0 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.853360,  0] ../source4/rpc_server/dcerpc_server.c:3023(add_socket_rpc_tcp_iface)
>    service_setup_stream_socket(address=152.94.0.106,port=0) for dnsserver backupkey eventlog6 browser unixinfo dssetup drsuapi lsarpc mgmt failed - NT_STATUS_ADDRESS_NOT_ASSOCIATEDtask_server_terminate: [Failed to startup dcerpc server task]
> [2019/06/11 09:23:50.199566,  0] ../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:50.199780,  0] ../source4/ldap_server/ldap_server.c:1030(add_socket)
>    ldapsrv failed to bind to 152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:50.200068,  0] ../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [Failed to startup ldap server task]
>
> However, after restarting samba-ad-dc everything looks fine, no error messages at all (despite of "setproctitle..." messages).
>
> Any idea on how to start samba properly on boot?
>
Are you by any chance trying to start the 'nmbd' binary as well as the 
'samba' binary ?

If so, you must stop this happening. On a DC, starting 'samba' will 
start all other required binaries.

If this isn't the case, can you please post your smb.conf

Rowland