Link to home
Start Free TrialLog in
Avatar of Member_2_1261037
Member_2_1261037Flag for United States of America

asked on

Netapp Clustered ONTAP 8.3 CIFS issue

We have a CNAME "DOCS" that points to a CIFS Vserver that works fine in PROD.  When In DR mode using a snapmirrored destination that uses the exact same DNS servers, the Win10 or 2012 server clients are not able to access \\DOCS in the DR system, yet the IP \\10.0.50.55 works.  \\DOCS.domain.com.\ [with a period behind the COM] works as well.  Why do IP addresses, FQDN with PERIOD, and A record names work, but the ONE "DOCS" CNAME does not???  Other CNAMES work as well.  Win7 clients do not have any issue in DR system.
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

It may be that nebios is not enabled, especially if it's AD integrated.

https://library.netapp.com/ecmdocs/ECMP12452955/html/vserver/cifs/nbtstat.html

-nbt-name <text>] - NBT Name
If you specify this optional parameter, the command displays the NetBIOS name service information only for the specified NetBIOS name.
ASKER CERTIFIED SOLUTION
Avatar of Member_2_1261037
Member_2_1261037
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Did the KB provided resolve your issue?
Avatar of Member_2_1261037

ASKER

Yes, this stems from having two stand-alone Filers where DR is a Snapmirror destination and the SYSTEM NAME for the Cifs servers have to be unique.  When switching to DR filer, the SPNs point to the PROD system names and need to be updated to point to the DR system names.  I simply removed the SPN pointing to PROD host names and added new ones that point to DR system names and the issue was resolved.  When moving from DR back to PROD, this process has to be reversed.
KB resolved my issue completely.