topic DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails in Network and Storage Protocols

DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

ctolley — Wed, 15 Mar 2017 01:27:10 GMT

NetApp FAS3240 HA pair with 4 DS4243 arrays

Running- 8.2.3 7-Mode

Trying to move from a Windows 2008 based AD domain to a Windows 2012 AD Domain.

SMB1 is disabled in the 2012 Domain

Time services are runnning and both heads and both DC's are within a few seconds of each other

I suspect the Win2k12 domain doesnt like something about the way the NetApp is handling SMB, but not sure what else to try at this point. I've reconnect one of the controllers back to the original 2008 Domain with no problems.

cifs domaininfo
NetBIOS Domain: {DOMAIN}
Windows Domain Name: {domain name}
Domain Controller Functionality: Not Available
Domain Functionality: Not Available
Forest Functionality: Not Available
Filer AD Site: Default-First-Site-Name

Not currently connected to any DCs

Preferred Addresses:

{SERVER IP 02} {SERVERNAME02} PDCBROKEN
{SERVER IP 01} {SERVERNAME01} PDCBROKEN

options cifs.smb2
cifs.smb2.enable on
cifs.smb2.signing.max_threads 3
cifs.smb2.signing.multiprocessing default
cifs.smb2.signing.required off
cifs.smb2_1.branch_cache.enable off
cifs.smb2_1.branch_cache.hash_time_out 3600 (value might be overwritten in takeover)

console output from cifs resetdc

Tue Mar 14 21:05:50 EDT [SERVERNAME02:cifs.server.infoMsg:info]: CIFS: Warning for server \\{SERVERNAME02}: Connection terminated.
Tue Mar 14 21:05:50 EDT [SERVERNAME02:cifs.server.errorMsg:error]: CIFS: Error for server \\{SERVERNAME02}: Error while negotiating protocol with server STATUS_IO_TIMEOUT.
Tue Mar 14 21:06:20 EDT [SERVERNAME02:cifs.server.infoMsg:info]: CIFS: Warning for server \\{SERVERNAME01}: Connection terminated.
Tue Mar 14 21:06:20 EDT [SERVERNAME02:cifs.server.errorMsg:error]: CIFS: Error for server \\{SERVERNAME01}: Error while negotiating

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

Sahana — Wed, 15 Mar 2017 05:35:46 GMT

Hi,

It could be due to bug : http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=816472

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

ctolley — Wed, 15 Mar 2017 17:44:23 GMT

Hmm, might be related although I cannot even access AD as yet. However they do recommend to move to 8.2.4 which I suppose couldnt hurt.

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

cabjas01 — Mon, 24 Apr 2017 05:01:23 GMT

I have the same problem (PDCBROKEN) if I disable SMB1 on the domain controllers and was forced to re-enable SMB1 to get them working again. Were you able to get this working without re-enabling SMB1 on the DC's?

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

IlyaPykhov — Sat, 10 Jun 2017 09:33:31 GMT

Hi guys,

I have encountered the same issue just now and I was able to fix it by changing the option "cifs.smb2.client.enable" to ON, somehow it was not visible using "options cifs", so i have manually typed the following under advaced privs:

options cifs.smb2.client.enable on

After this PDCBROKEN status for DCs has gone.

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

EugeneB — Wed, 05 Jul 2017 03:24:12 GMT

I have the same issue, and problem solved with the same solution.

options cifs.smb2.client.enable on

May refer to this post https://kb.netapp.com/support/s/article/ka11A0000001H1ZQAU/user-sends-reset-packet-after-negotiate-protocol-request-from-the-storage-system

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

AndyRawlins — Thu, 15 Mar 2018 11:14:32 GMT

Fixed our broken AD connections thank you 🙂

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

essm — Fri, 12 Oct 2018 01:49:46 GMT

Worked for me as well

Re: DataOnTap 8.2.3 change from a Win2k8 Domain to Win2k12 Domain fails

Stadivaka — Fri, 23 Apr 2021 22:08:46 GMT

I had experienced similar issue but we could able to fix the issue after changing the default value of "cifs.AD.retry_delay" from 0 to 15. Later enabled cifs.smb2.client.enable found which are the DCs able to connect those I have set ad preferred DC. Eventually it start communicating and able to get rid off PDCBROKEN.

Best Regards,

Surya Tadivaka

Infrastructure Specialist,