I have started migrate volumes to a new cluster via snapmirror.
After broken off the snapmirror relationship, the volume gets RW and I create a junction path to use for the cifs share.
Even if I give the share Everyone, I'm unable to access to share. I can see the share from the Explorer, but not accessing it. It worked before the migration. Even stranger gets it when I tried to create a new volume/share on the new cluster. I get the same problem, but some test share I created just after installation of the cluster works fine. The only thing I have done is upgrading ontap to 9.13.1.P2. I think it was 9.12-something before upgrading it.
I can't find anything that differ between the share that works and do who doesn't work.
Any ideas? I have a case, but the respond time is slow (prio 3).
Ensure Time (date) on your FILER (new cluster) is within 5 minute deviation from the AD Server.
Is the flexvol (R/W) security style marked as NTFS ?(A FlexVol volume inherits the security style of the root volume of its containing SVM) so make sure it is not 'unix', and if so change it to 'ntfs'?