We are migrating CIFS shares from an old 7-MODE system to a new CDOT cluster.
Existing 7-MODE system is joined to the domain as XFILES
New CDOT SVM joined to the domain as DENPRDCIFS01
CIFS LIF on new CDOT SVM is 192.168.21.251 (DNS record for DENPRDCIFS01 points to this IP)
We have successfully migrated the shares from the 7-MODE system to the new CDOT system and cut them over. Customer wants to maintain the ability to connect to shares using the XFILES computer name. We have changed the DNS record for XFILES to be a DNS alias pointing at the DNS record for the CIFS LIF on the SVM (DENRPDCIFS01). We have not removed the old 7-mode "XFILES" computer from AD but have added it as a NETBIOS alias on the new CIFS server on the NetApp cluster.
We can browse/connect to the shares on the new cluster using a UNC path with the IP of the CIFS LIF and the DENPRDCIFS01 host name. We can ping the XFILES host name and it resolves correctly to the IP address of the CIFS LIF on the cluster. However, we still cannot browse to the shares at "\\XFILES\" on existing client that previously connected to the 7-MODE system XFILES. We can browse/connect to \\XFILES\ on a new windows client that had never previously connected to XFILES CIFS server on the 7-mode system.
Couple of questions:
1) Is the old "XFILES" AD entry cached somewhere on existing clients which is causing our issues? If so, how do we clear it?
2) Do we need to delete old "XFILES" computer entry from AD to make this work? Customer is hesitant to do this in case we need to fail back to using the 7-MODE system if we cannot get this issue fixed.
3) If we do delete the existing XFILES computer AD entry, can we re-add it easily if we need to fail back to the 7-mode system?