topic After DC Update No CIFS Access (PDC BROKEN) in ONTAP Discussions

After DC Update No CIFS Access (PDC BROKEN)

marshit — Wed, 04 Jun 2025 09:59:57 GMT

Hello Folks,

I'm running 7-mode NetApp release 8.2.5 - yes, this system is going away and EOL already. But nevertheless I have a Windows 2016 server that was updated last week. It's a VM and we changed to a different VM but used the same name as the previous so DNS didn't needed to be changed.

Now I noticed that none of my CIFS connections works. When I run cifs sessions it's completly empty. I have ran testdc, prefdc, resetdc, stopped and restarted CIFS service and still no luck.

When I run cifs domaininfo command it says BROKEN everywhere for Favored and Preferred Addresses.

What can I do next?

Re: After DC Update No CIFS Access (PDC BROKEN)

NetApp_SR — Tue, 07 Jun 2022 04:04:02 GMT

You say its a different VM so some security identifier may have changed try "cifs terminate" and then "cifs setup". Follow the prompts to reconnect.

Re: After DC Update No CIFS Access (PDC BROKEN)

aladd — Tue, 07 Jun 2022 05:17:09 GMT

Check to make sure of what SMB version is presently being used and authentication method between storage and the DC.

Re: After DC Update No CIFS Access (PDC BROKEN)

Mjizzini — Tue, 07 Jun 2022 06:07:59 GMT

ONTAP is utilizing SMB1 to communicate with the DC(s) and the DC(s) cannot communicate over SMB1

Enable smb2 for DC connection on the filer, or enable smb1 on the DC.

Authentication issues after upgrading domain controller to Server 2016

Re: After DC Update No CIFS Access (PDC BROKEN)

paul_stejskal — Tue, 07 Jun 2022 13:53:06 GMT

Did it break right after updates to Windows 2016? If so, which updates were applied?

Re: After DC Update No CIFS Access (PDC BROKEN)

marshit — Tue, 07 Jun 2022 14:44:36 GMT

I'm on WIndows 2019 but is wasn't an OS upgrade just now, that was done months agao and has been working fine.

@NetApp_SR I already tried running setup again for CIFS several times and what it did was fix the "domaininfo" to where it doesn't say "BROKEN" anymore but yet I still can't access.

Now I did notice there are no computer objects within AD for for NAS filers, do those need to be manually added again? The DNS entries are still within AD and apppear to be fine.

Re: After DC Update No CIFS Access (PDC BROKEN)

aladd — Wed, 08 Jun 2022 01:03:58 GMT

Yes, you will need a machine account on the DC in order to effectively authenticate.

CIFS setup should correct the machine account issue, but it sounds like we need more information on the problem.

Can you try to authenticate and then get the output to the following command?

::>event log show -event *secd*

Re: After DC Update No CIFS Access (PDC BROKEN)

Mjizzini — Wed, 08 Jun 2022 02:09:47 GMT

Cifs server Machine account deleted from AD

Re: After DC Update No CIFS Access (PDC BROKEN)

marshit — Wed, 08 Jun 2022 19:14:28 GMT

None of these commands are for 7-mode. I also had already re-added the objects to AD.

Re: After DC Update No CIFS Access (PDC BROKEN)

marshit — Wed, 08 Jun 2022 19:17:05 GMT

Your command didn't work and that also is not a 7-mode command.

Re: After DC Update No CIFS Access (PDC BROKEN)

AlexDawson — Thu, 09 Jun 2022 02:59:37 GMT

To confirm, is it running 8.2.5P5?

Re: After DC Update No CIFS Access (PDC BROKEN)

tahmad — Thu, 09 Jun 2022 03:14:30 GMT

are you able to share the logs requested by aladd

Re: After DC Update No CIFS Access (PDC BROKEN)

marshit — Thu, 09 Jun 2022 12:45:31 GMT

@AlexDawson You are correct.

Re: After DC Update No CIFS Access (PDC BROKEN)

marshit — Thu, 09 Jun 2022 12:46:23 GMT

@tahmad That command didn't work on 8.2.5 version of 7-mode.

Re: After DC Update No CIFS Access (PDC BROKEN)

aladd — Fri, 10 Jun 2022 01:36:28 GMT

Sorry @marshit ,

Can you please try to reauthenticate and then collect the output from the following:

>rdfile /etc/messages