Falha na junção do host Windows a um Samba Active Directory

Question

Eu não pude entrar em um computador com Windows (2k3) em um Samba4 Active Directory, porque recebi esta mensagem no host:

Error occured joining the domain. The specified network name is no longer available.

Recebi avisos serevos quando inicio o Samba (em log.samba):

[2016/05/28 17:28:45.075722,  0] ../source4/smbd/server.c:490(binary_smbd_main)
  samba: using 'standard' process model
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2016/05/28 17:28:45.107472,  0] ../lib/util/become_daemon.c:124(daemon_ready)
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
  STATUS=daemon 'samba' finished starting up and ready to serve connections
[2016/05/28 17:28:45.118242,  0] ../lib/util/util_runcmd.c:328(samba_runcmd_io_handler)
  /usr/sbin/winbindd: Failed to exec child - No such file or directory
[2016/05/28 17:28:45.123154,  0] ../source4/winbind/winbindd.c:47(winbindd_done)
  winbindd daemon died with exit status 255
[2016/05/28 17:28:45.123264,  0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [winbindd child process exited]
[2016/05/28 17:28:45.124258,  0] ../source4/smbd/server.c:211(samba_terminate)
  samba_terminate: winbindd child process exited
[2016/05/28 17:28:45.824903,  0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done)
  ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_ACCESS_DENIED

Meu / etc / hosts (posteriormente corrigido com endereços corretos):

127.0.0.1       localhost
172.16.0.10     omega.open.local
172.16.0.10     OMEGA.open.local
172.16.0.10     open.local
172.16.0.10     OMEGA
172.16.0.10     omega
172.16.0.10     OPEN
172.16.0.10     OPEN.LOCAL

Meu /etc/resolv.conf:

nameserver 172.16.0.10
search open.local
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 172.16.0.10
search open.local

Se eu executar o nslookup omega.open.local, obtenho o IP do servidor corretamente.

    

Answer 1

O problema não é causado pelos erros mostrados no log. Tentei resolver o problema várias vezes e finalmente encontrei a solução (em este site ):

... adding winbind package solves it (probably better to reboot after adding it, instead of trying to restart all samba services). It doesn't say you need any special winbind config.

Antes de encontrar a resposta, fiz o downgrade do Samba para a versão 4.3.9 e adicionei essas linhas a /etc/samba/smb.conf , então não tenho certeza se essas duas etapas são necessárias.

idmap_ldb:use rfc2307 = yes 
server signing = Auto 

Antes de resolver o problema, não consegui acessar recursos compartilhados pelo servidor usando //SERVERNAME path e não consegui executar este comando com êxito:

smbclient -L localhost -U%

    

Answer 2

Entrada de arquivo de hosts incorreta para localhost

Loopback em um sistema local sempre precisa ser 127.0.0.1

Os sistemas Windows e alguns linux testarão sua pilha IP local como parte do processo de junção e chamar-se-ão de chamadas netbios e RPC.

Quando o sistema tenta se resolver, ele está falhando.

Você precisa fazer o ping de host local e ping loopback e obter o endereço de volta 127.0.0.1

Se você não puder, a adesão falhará.

Sua primeira entrada nos hosts 27.0.0.1 localhost precisa ser 127.0.0.1 localhost

Corrija essa entrada e veja o que acontece. Espero que isso seja útil.