On 1/1/19 12:21 AM, Miroslav Geisselreiter wrote:
# wbinfo --ping-dc checking the NETLOGON for domain[NT4DOMAIN] dc connection to "nt4member.intranet.xx" succeeded
Well, the host where you ran that command thinks that "nt4member" is the DC. Do you see anything in your configuration file that might indicate why? You haven't given us enough information to be much more use.
Thank you. Exactly and that is my problem. # grep -i nt4member /etc/samba/smb.conf netbios name = nt4member
some parameters from smb.conf: [global] client ipc signing = default idmap config * : backend = tdb idmap config * : range = 100000-150000 idmap config NT4DOMAIN : backend = tdb idmap config NT4DOMAIN : range = 500-99999 winbind enum groups = yes winbind enum users = yes winbind expand groups = 0 winbind max domain connections = 5 winbind nested groups = yes winbind rpc only = no winbind scan trusted domains = no winbind sealed pipes = yes winbind use default domain = no workgroup = NT4DOMAIN netbios name = nt4member security = domain allow trusted domains = yes passdb backend = ldapsam:"ldap://ldap1server.intranet.xx ldap://ldap2server.intranet.xx" ldap ssl = start tls realm = INTRANET.XX ldap suffix = dc=intranet,dc=xx ldap admin dn = uid=ldapadmin,dc=intranet,dc=xx ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Idmap ldapsam:trusted = yes ldap delete dn = no ldap deref = auto ldap follow referral = auto socket options = TCP_NODELAY domain master = no domain logons = no local master = no os level = 121 preferred master = no wins server = X.X.X.X
Tell me what more do you need.