Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello guys,
Can anyone help me with this case:
We had an issue that caused our AD to fail completely.
We have no way to recover.
We had to create a new AD from scratch.
But after reconfiguring CIFS and mapping the shares,
We came across "Access Denied"
Can anyone share some solution
Filer: FAS8020HA
Ontap Date: 8.2.5P5 Data Ontap 7-Mode
Old Domain: Windows Server 2012R2
Nwe Domain: Windows Server 2016
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You mentioned, after reconfiguring CIFS; Does that mean CIFS setup is completed successfully and the CIFS server machine account is created in your 2016 AD domain ?
You can do few checks:
1) Is filer time and the AD time in sync (Within 5 mnt apart)
2) Make sure SMB2 is enabled on filer: (SMB1 is disabled by default in 2016, so it (DC) must communicate via SMB2)
Enable this:
filer> options cifs.smb2.client.enable on
Try again, else share rdfile /etc/messages
