DNS and GENSEC issues when running the samba binary

Erick Nascimento erick.nogueira.nascimento at gmail.com
Tue Nov 3 22:06:56 MST 2009


Hi,

After start the following command:
$ sudo bin/samba -i -M single -d4

I got the errors below periodically.

I have a Windows Server 2008 DC on 143.106.167.147 and the samba DC is on
143.106.167.143.
The AD full domain name is "winserverad.ltc.inovasoft.unicamp.br". I have a
bind9 server that have a zone for "winserverad.ltc.inovasoft.unicamp.br"
that forward the requests the w2k8 DNS server.
Before running the binary, I runned scripting/devel/drs/vampire_ad.sh to
vampire w2k8 AD.

The name "a7b3d65b-2a90-4786-ad93-cdee0850bff8._
msdcs.winserverad.ltc.inovasoft.unicamp.br"
should be resolved to the w2k8 server IP (I can`t resolve this name on my
Linux box).
After a restart of the w2k8 server, the GENSEC issues disappeared, but now
they are appearing again.
I'm using the git tree with revision number
4a4f420481cae5ba82a42d6763d3732defccac24
(October 15).

Contents of /etc/resolv.conf:
domain ltc.inovasoft.unicamp.br
search WINSERVERAD.LTC.INOVASOFT.UNICAMP.BR ltc.inovasoft.unicamp.br
nameserver 127.0.0.1

The errors:
[...]
dreplsrv_periodic_schedule(5) scheduled for: Wed Nov  4 02:18:49 2009 BRST
Mapped to DCERPC endpoint 135
added interface ip=143.106.167.143 nmask=255.255.255.224
added interface ip=127.0.0.1 nmask=255.0.0.0
dreplsrv_notify_schedule(5) scheduled for: Wed Nov  4 02:18:49 2009 BRST
dns child failed to find name
'a7b3d65b-2a90-4786-ad93-cdee0850bff8._msdcs.winse
rverad.ltc.inovasoft.unicamp.br' of type A
dreplsrv_op_pull_source(WERR_BADFILE/NT_STATUS_NO_SUCH_DEVICE) failures[1]
added interface ip=143.106.167.143 nmask=255.255.255.224
added interface ip=127.0.0.1 nmask=255.0.0.0
Could not find GENSEC backend for auth_type=16
Failed to start GENSEC client mechanism (null): NT_STATUS_INVALID_PARAMETER
Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 -
NT_STATUS_INVALID_
PARAMETER
dreplsrv_op_pull_source(WERR_INVALID_PARAM/NT_STATUS_INVALID_INFO_CLASS)
failure
s[1]
[...]

Are there any additional configuration need to solve that ?

Thanks,
Erick Nogueira do Nascimento


More information about the samba-technical mailing list