Symptoms

Customer's NAS_Server is unable to communicate to the domain controllers and Customer is unable to access CIFS shares.

Cause

Review of the ktrace log files shows the following errors:[/EMC/C4Core/log/c4_safe_ktrace.log]2018/09/07-12:52:37.705027 135 7FE161FB1702 sade:SMB: 3:[0067-fs07] SSXNego:Negociate NoReply2018/09/07-12:52:37.705054 27 7FE161FB1702 sade:SMB: 3:[0067-fs07] Open&Bind(lsarpc): No reply from DC=*SMBSERVER DCStatus=5/DOMAIN_CONTROLLER_NOT_FOUND Ems=Bind_CreateXFaile2018/09/07-12:52:37.705056 1 7FE161FB1702 sade:SMB: 3:[0067-fs07] d2018/09/07-12:52:37.705065 9 7FE161FB1702 sade:SMB: 3:[0067-fs07] OpenAndBind[LSA] DC=*SMBSERVER failed: Bind_CreateXFailed DOMAIN_CONTROLLER_NOT_FOUND- review of the EMCSystemLogFile shows domain controller errors as well[/EMC/backend/log_shared/EMCSystemLogFile.log]"2018-09-07T13:24:05.001Z" "0067-fs07-m_spa" "Neo_CEM" "31636" "N/A" "ERROR" "14:603ab" :: "All Domain Controller servers configured for CIFS server 0067-FS07 are not reachable." :: Category=User Component=Health"2018-09-07T13:24:35.571Z" "0067-fs07-m_spa" "Neo_CEM" "31636" "N/A" "ERROR" "14:70001" :: "Failed to send e-mail alert (Invalid alert configuration or mail server error). Alert text: All Domain Controller servers configured for CIFS server 0067-FS07 are not reachable." :: Category=User Component=AlertServices"2018-09-07T13:25:26.680Z" "0067-fs07-m_spa" "Kittyhawk_safe" "19052" "unix/spa/root" "ERROR" "13:10380007" :: "For the NAS server 0067-fs07 in the domain tb.zsb.sbrf.ru, the connection with the Domain Controller is valid." :: Category=Audit Component=DART_SMB"2018-09-07T13:26:42.735Z" "0067-fs07-m_spa" "Kittyhawk_safe" "19052" "unix/spa/root" "ALERT" "13:10380006" :: "The NAS server 0067-fs07 in the domain tb.zsb.sbrf.ru can't reach any Domain Controller." :: Category=Audit Component=DART_SMB"2018-09-07T13:27:07.922Z" "0067-fs07-m_spa" "Neo_CEM" "31636" "N/A" "ERROR" "14:603ab" :: "All Domain Controller servers configured for CIFS server 0067-FS07 are not reachable." :: Category=User Component=Health"2018-09-07T13:32:27.260Z" "0067-fs07-m_spa" "Kittyhawk_safe" "19052" "unix/spa/root" "ALERT" "13:10380006" :: "The NAS server 0067-fs07 in the domain tb.zsb.sbrf.ru can't reach any Domain Controller." :: Category=Audit Component=DART_SMB- Confirmed with the Customer that SMBv1 was NOT disabled [refer to article Dell EMC Unity, VNX, VNXe,: Users unable to access CIFS after disabling SMB1 on Domain Controllers (User Correctable) if smbv1 is disabled]- When running server CIFS noticed that the domain controllers have leading special characters "**"[/nas/bin/server_cifs ALL]Security mode = NTMax protocol = SMB3.0I18N mode = UNICODECIFS service of VDM 0067-fs07 (state=loaded)Home Directory Shares DISABLEDDOMAIN TB FQDN=fqdn.com SITE=0067_TYUMEN RC=10SID=S-1-5-15-DC**SMBSERVER(xxx.xxx.xxx.xxx) ref=113 time=0 ms (Closest Site) DC**SMBSERVER(xxx.xxx.xxx.xxx) ref=143 time=0 ms (Closest Site) >DC**SMBSERVER(xxx.xxx.xxx.xxx) ref=153 time=0 ms (Closest Site) DC**SMBSERVER(xxx.xxx.xxx.xxx) ref=137 time=0 ms (Closest Site) CIFS Server 0067-FS07[TB] RC=1580 (local users supported)Full computer name=0067-fs07domain.com realm=domain.comComment='EMC-SNAS:T8.0.1.112'if=1_interface l=xxx.xxx.xxx.xxx b=yyy.yyy.yyy.yyy mac=aa:aa:aa:aa:aa:aaFQDN=0067-domain.com (Updated to DNS)Password change interval: 0 minutesLast password change: Thu Feb 15 00:09:12 2018 GMTPassword versions: 3

Resolution

There is a known bug in VNXe where VNXe is unable to read either the CIFS name or Domain Controller name properly with leading zero's.It is recommended practice that the CIFS name or Domain Controller name lead with alphabet characters before numeric characters to avoid communication issues between the CIFS and Domain Controller.Quick way to identify the issue is to use the "server_cifs" command, or "nslookup" of the DC will show you the correct name. If either "server_cifs" or "nslookup" shows " DC**SMBSERVER" then Customer is likely running into this bug.This bug is addressed in the hotfix: VNXe-hotfix-3.1.8.9340299.1.2.009.9773043.1536151334 (Please open ticket with support to have hotfix image provided).

Support Cases