on a AD DC with no network interface up OR no IP configured (yet) we get those messages while starting up: [2014/03/21 03:08:21.146639, 0] ../source4/lib/socket/interface.c:325(load_interface_list) WARNING: no network interfaces found [2014/03/21 03:08:21.147467, 0] ../source4/smbd/service_task.c:35(task_server_terminate) task_server_terminate: [kdc: no network interfaces configured] the first one is a legit warning but the second is a problem. The KDC does not start. let's have a look at netstat -anp|grep "LISTEN " | grep samba : *Without* network at startup time: tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 12822/samba tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN 12814/samba tcp 0 0 0.0.0.0:1024 0.0.0.0:* LISTEN 12810/samba tcp 0 0 0.0.0.0:3268 0.0.0.0:* LISTEN 12814/samba tcp 0 0 0.0.0.0:3269 0.0.0.0:* LISTEN 12814/samba tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 12814/samba tcp 0 0 0.0.0.0:135 0.0.0.0:* LISTEN 12810/samba *WITH* network at startup time we also see: tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 12671/samba tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 12671/samba
those udp listening sockets are also missing if the network interface was not configured at startup: udp 0 0 0.0.0.0:389 0.0.0.0:* 21764/samba udp 0 0 0.0.0.0:464 0.0.0.0:* 21765/samba udp 0 0 0.0.0.0:53 0.0.0.0:* 21771/samba udp 0 0 0.0.0.0:88 0.0.0.0:* 21765/samba udp 0 0 0.0.0.0:137 0.0.0.0:* 21761/samba we only listen on 0.0.0.0:138 udp with a non configured network interface