It does an LDAP lookup for itself to see if it needs to create a new machine account or to use the existing one.
Did you try to enable "cifs.trace_login" during the process?
You may want to open a support case.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Momonth Sent: Thursday, August 11, 2016 6:53 AM To: toasters@teaparty.net Subject: "cifs setup" fails with "Setup cannot connect to an LDAP server for the FQDN"
Hi,
I tried to add 8.2.3 7-Mode filer to Windows AD via "cifs setup" wizard, but it's failing with:
CIFS - Logged in as username@MYDOMAIN.COM *** Setup cannot connect to an LDAP server for the MYDOMAIN.COM *** active directory domain, and so cannot continue.
I think the error message is misleading as the filer can talk to LDAP servers (I have multiple domain controllers) and I have a tcpdump that confirms it.
From what I could get from the tcpdump, the filer does the following:
0. Sends DNS request "SRV _ldap._tcp.MYDOMAIN.COM"
// + some more DNS requests for "SRV _kerberos" etc.
1 Sends LDAP search query that looks like this:
Filter: (&(&(DnsDomain=MYDOMAIN.COM)(Host=FILER-NAME))(NtVer=0x00000006))
Does it try to find itself ?
2. Gets am empty (but successful) response, where "matchedDN" is empty.
3. Sends "abondonRequest" to LDAP server.
4. Sends "unbindRequest to LDAP server.
The filer repeats it for all LDAP server it fetched at step 0. and quits with the error.
I found the following KBs:
https://kb.netapp.com/support/index?page=content&id=2026294&actp=LIS... https://kb.netapp.com/support/index?page=content&id=2018207&actp=LIS...
All my LDAP servers have names that are less than 15 symbols, that's verified. And NetBIOS is not active I was told.
Any ideas maybe?
Cheers, Vladimir _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters