Did you check the knowledgebase ?

I've just re-did it but I don't see anything that applies to my case..

strange thing is that before there was a CIFS server that joined the domain (some months ago).. and now I am not able to re-do the same action.

Oliver

Try server_checkup – it can identify a number of issues that can bother CIFS

Rainer

Hi Rainer,

thanks for your reply..

I did it and these are the result..

as you can see it seems that dc and dns reachability is not good.. but from celerrra I can ping them and even the dns data is there:

[nasadmin@celerra ~]$ server_checkup server_2
server_2 :

------------------------------------Checks--------------------------------------

Component REPV2 :

F_RDE_CHEC: Checking the F-RDE compatibility of Repv2 sessions............. Pass

Component HTTPS :

HTTP      : Checking the configuration of HTTP applications................ Pass
SSL       : Checking the configuration of SSL applications................. Pass

Component CIFS :

ACL       : Checking the number of ACLs per file system....................*Pass
Connection: Checking the load of CIFS TCP connections...................... Pass
Credential: Checking the validity of credentials........................... Pass
DC        : Checking the connectivity and configuration of Domain Controlle*Fail
DFS       : Checking the DFS configuration files and DFS registry.......... Pass
DNS       : Checking the DNS configuration and connectivity to DNS servers. Fail
EventLog  : Checking the configuration of Windows Event Logs............... Pass
FS_Type   : Checking if all file systems are in the DIR3 format............ Pass
GPO       : Checking the GPO configuration................................. Pass
HomeDir   : Checking the configuration of home directory shares............ Pass
I18N      : Checking the I18N mode and the Unicode/UTF8 translation tables. Pass
Kerberos  : Checking password updates for Kerberos......................... Pass
LDAP      : Checking the LDAP configuration................................ Pass
LocalGrp  : Checking the database configuration of local groups............ Fail
NIS       : Checking the connectivity to the NIS servers................... Pass
NS        : Checking the naming services configuration..................... Pass
NTP       : Checking the connectivity to the NTP servers................... Fail
Ntxmap    : Checking the ntxmap configuration file......................... Pass
Secmap    : Checking the SECMAP database................................... Pass
Security  : Checking the CIFS security settings............................ Pass
Server    : Checking the CIFS file servers configuration................... Fail
Share     : Checking the network shares database........................... Fail
SmbList   : Checking the range availability of SMB IDs.....................*Pass
Threads   : Checking for CIFS blocked threads.............................. Pass
UM_Client : Checking the connectivity to usermapper servers................ Pass
UM_Server : Checking the usermapper server database........................*Pass
UnsupOS   : Checking for unsupported client network operating systems...... Fail
UnsupProto: Checking for unsupported client network protocols.............. Pass
VC        : Checking the configuration of Virus Checker servers............ Pass
WINS      : Checking the connectivity to WINS servers...................... Fail

Component FTPDS :

FS_Type   : Checking if all file systems are in the DIR3 format............ Pass
FTPD      : Checking the configuration of FTPD............................. Fail
NIS       : Checking the connectivity to the NIS servers................... Pass
NS        : Checking the naming services configuration..................... Pass
NTP       : Checking the connectivity to the NTP servers................... Fail
SSL       : Checking the configuration of SSL applications................. Pass

NB: a result with a '*' means that some tests were not executed. use -full to run them

##############################################################

[nasadmin@celerra ~]$ server_ping server_2 10.0.10.5
server_2 : 10.0.10.5 is alive, time= 0 ms

##############################################################

[nasadmin@celerra ~]$ server_dns server_2 -option dump
server_2 :
DNS cache size for one record type: 64
DNS cache includes 6 item(s):
dctorri.xxxxxx.lan
Type:A         TTL=3429 s  dataCount:1
  10.0.11.5
---
dcquinto.xxxxxx.lan
Type:A         TTL=3470 s  dataCount:1
  10.0.10.5 (local subnet)
---
bbb.xxxxxx.lan
Type:A,AAAA    TTL=185 s  dataCount:0
  negative entry
---
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.xxxxxx.lan
Type:SRV       TTL=429 s  dataCount:2
  priority:0      weight:100    port:389   server:dcquinto.xxxxxx.lan
  priority:0      weight:100    port:389   server:dctorri.xxxxxx.lan
---
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.xxxxxx.lan
Type:SRV       TTL=429 s  dataCount:2
  priority:0      weight:100    port:88    server:dctorri.xxxxxx.lan
  priority:0      weight:100    port:88    server:dcquinto.xxxxxx.lan
---
xxxxxx.lan
Type:SOA       TTL=170 s  dataCount:1
  version:52460 server:dcquinto.xxxxxx.lan
---
##############################################################

ok, I will do so.

thanks for your help.

Oliver

Hi,

error message "DomainJoin::getAdminCreds: gss_acquire_cred_ext failed: Miscellaneous failure. Preauthentication failed" means something on the account provided on the Join command is wrong.

Since you said the account and password are correct, I recommend you to open a support ticket. There are some special commands we can use to diagnose the AD and the Celerra.

Gustavo Barreto.

Something is wrong

A server_dsns – o dump doesnt really test the DNS – it just dumps the case.

I dont think there are user level commands to test data mover DNS (expect for server_checkup)

I would carefully check the DNS setup and restart the DNS service

Server_cifssupport also has some options to test domain controller availability

If you don’t get any further there I would suggest to open a service request.

Service should have some .server_config commands to test

Rainer

I do agree with you Rainer, but indeed if I do a :

server_dns server_2 -option flush and then stop and start if I try again the join to the domain I can see the server_dns server_2 -option dump table get populated..

that should means the dns is working.. (isn't?)

anyway.. I've tried to use the /nas/bin/server_cifssupport but I am not able to get any kind of info from it..

even the pingdc is not working..

Let me preface this by saying the Primus at face value suggests it is an old issue; however, if you are to read through some of the reported symptoms, there is some similarity in what you are experiencing.

For instance, you report being able to ping the DNS servers, but the server_checkup command returns: "Fail".  There is a "Symptom" in the Primus that states:

Also, of course there is a similarity with the join failing.

If related, the resolution is to disable ip reflect; however, to test this will require a reboot of the datamover.  Just a thought.  If you can take the outage (and maybe if someone else in this community can also review first) maybe this is worth trying?  Then again, since you've probably opened up a support ticket by now, let's see what feedback they have after they've had a chance to review a bit.