2014-03-11 10:26 PM
one of our customer configured vservers name which were DNS resolvable and they were accessing CIFS shares using vserver names and not by CIFS server names.
Both vserver and CIFS server names were different and pointing to same IP however CIFS server names were not registered in DNS. Do you have idea what’s the best practice NetApp recommends around this?
I am listing down some scenarios below.
2014-03-11 11:05 PM
Here the concern should be AD authentication (Kerberos).
When we create CIFS server, it will register it as computer account in AD. If the end users use any alias apart from CIFS server name to access the shares, then the authentication fall back to NTLM. Kerberos authentication does not work.
What is the rational behind using the DNS alias instead of CIFS server?
2014-03-12 01:03 AM
No specific reason as per customer one of the netapp guy came to deploy cluster mode and customer now thinks this must be right way to go as somebody from netapp done setup.
I think I should go back and educate customer to use CIFS server name for share access and register same in DNS. make sense?