VNX: Shares from VNX CIFS Server not working due to SMB1 protocol disabled at domain controller

Summary: VNX: Shares from VNX CIFS Server not working due to SMB1 protocol disabled at domain controller

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

SMB1 disabled at domain controller

Able to join CIFS Server to windows active directory but unable to access shares.

server log shows following error in SMB protocol :
  
2015-08-12 16:51:42: 13157007360: SMB: 3: DC0x18 CIFS[NET] 10.202.0.101 dispatchIPCtoDC: No Reply TID=0x0 PID=0x19ef UID=0x0
2015-08-12 16:51:42: 13157007360: SMB: 3: SSXNego:Negociate NoReply
2015-08-12 16:51:42: 13157007360: SMB: 3: W2KDCRequestA:setDCDown(10.0.0.1)
2015-08-12 16:51:42: 13157007360: SMB: 3: last message repeated 1 times
2015-08-12 16:51:42: 13157007360: SMB: 3: CIFS::connectToDc:No DC found domain=domain.com
2015-08-12 16:51:42: 13157007360: SMB: 3: No more valid DC (currDC=0x0ABC)
2015-08-12 16:51:42: SMB: 3: Open&Bind(lsarpc): No reply from DC=AD_SERVER DCStatus=0/WAIT Ems=Bind_CreateXFailed
2015-08-12 16:51:42: SMB: 3: OpenAndBind[LSA] DC=AD_SERVER failed: Bind_CreateXFailed WAIT
  
PING DC fails:

$ server_cifssupport server_2 -pingdc -compname cifs.domain.com -dc AD_SERVER
server_2 : done

PINGDC GENERAL INFORMATION

DC SERVER:
Netbios name : AD_SERVER

CIFS SERVER :
Compname : cifs
Domain : domain.com

Error 13160939581: server_2 : compname cifs DC=AD_SERVER Step='Logon IPC$' failed with ntStatus='WAIT'.

Cause

At the Domain Controller SMB1 protocol is disabled.

CIFS Server requires SMB1 protocol. As this is blocked at Domain Controller, CIFS Server to DC communication fails.

Resolution

In all VNX OE code versions prior to 8.1.9.211, a VNX CIFS server requires SMB1 support on the Domain Controller to function correctly. 

In VNX OE version 8.1.9.211 and later, CIFS servers no longer require SMB1 support in order to function correctly.

Additional Information

To verify current setting:

To view the current setting for SMB1 protocol on the domain controller via Powershell:
 

Get-SmbServerConfiguration 
To check a remote server the name can be given like (IP address cannot be given):
Get-SmbServerConfiguration -CimSession <DC_Name>



If SMB1 is disabled, CIFS Server will not work and server_cifs <DM or VDM> will show that the DC is not having a connection established. When connected, the DC name will a ">" character, but it will be missing due to blocking of SMB1 protocol

To Enable SMB1 Support:
 

Powershell command to enable SMB1 support:

Set-SmbServerConfiguration  -EnableSMB1Protocol $true


Example:

PS C:\Users\Administrator> Get-SmbServerConfiguration  -CimSession DC2SHEE | findstr /i "SMB1"
EnableSMB1Protocol              : False
PS C:\Users\Administrator> Set-SmbServerConfiguration  -CimSession DC2SHEE -EnableSMB1Protocol $true -Force
PS C:\Users\Administrator> Get-SmbServerConfiguration  -CimSession DC2SHEE | findstr /i "SMB1"
EnableSMB1Protocol              : True


To disable SMB1 support :

Set-SmbServerConfiguration  -EnableSMB1Protocol $false

 

Affected Products

vVNX
Article Properties
Article Number: 000056502
Article Type: Solution
Last Modified: 12 Sep 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.