Solved

Netapp Clustered ONTAP 8.3 CIFS issue

Posted on 2016-08-26
5
34 Views
Last Modified: 2016-09-01
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.
0
Comment
Question by:tcloud
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 42

Expert Comment

by:paulsolov
ID: 41772645
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.
0
 

Accepted Solution

by:
tcloud earned 0 total points
ID: 41773030
Issue ended up being SPN conflict between the PROD and DR cifs SVMs because they have different system names.

Scenario #3 resolved my issue:
https://kb.netapp.com/support/index?page=content&id=1013601&actp=search&viewlocale=en_US&searchid=1472309929657
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 41773431
Did the KB provided resolve your issue?
0
 

Author Comment

by:tcloud
ID: 41773815
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.
0
 

Author Closing Comment

by:tcloud
ID: 41779507
KB resolved my issue completely.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Suggested Courses

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question