topic Re: UPN (user principal name) login does not work after migration to Clustered Ontap 8.2.2 in ONTAP Discussions

UPN (user principal name) login does not work after migration to Clustered Ontap 8.2.2

TOMASYAWORKS — Mon, 16 Feb 2015 13:32:45 GMT

We just did a migration from Data Ontap 8.2 7 mode to Clustered mode 8.2.2 for our Cifs protocol volumes.

Users from outside the domain where authenticated with their UPN "username@domainname.user.com"

After the migration with the 7-mode migration tool to clustered Ontap Cifs, users who are outside the domain, for example with an Ipad, they cannot login with their UPN anymore.

They can login with \domainname\username.

Users who are inside our Domain network for example a workstation which is a domainmember can login with their UPN.

Any thoughts on this?

Re: UPN (user principal name) login does not work after migration to Clustered Ontap 8.2.2

neto — Tue, 19 May 2015 18:44:58 GMT

Hi Tomas,

This is neto from Brazil

How are you?

Did you collect any trace that we could take a look? Do you have a Support Case open?

My thoughts are:

Do me a simple test, do you have a workstation (Windows for example) that is outside the domain? Could you please try to logon using UPN?

and please collect a trace and we could check.

Also collect the same trace using a workstation (windows) that is inside the domain.

I believe we could check and analyse the differences over there.

Thanks

neto

Re: UPN (user principal name) login does not work after migration to Clustered Ontap 8.2.2

Sebe — Wed, 06 Jun 2018 15:09:36 GMT

similar issue here

we have a different UPN than domain name. If users try to authenticate with user@fancyDomainName.com it fails. Authentication with domain\username works fine. On Oncommand, i get the following Error:

secd.cifsAuth.problem: vserver (fsxxx15) General CIFS authentication problem. Error: User authentication procedure failed CIFS SMB2 Share mapping - Client Ip = 10.207.5.75 [ 14] User 'fancydomainName.com\user' authenticated using NTLMv2 security **[ 14] FAILURE: Unsupported Windows domain name 'fancydomainName' [ 14] CIFS authentication failed [ 15] Using a cached connection to dcxxx [ 21] Unable to find the NetBIOS domain name for Active Directory 'fancyDomainName' [ 21] Unsupported Windows domain name 'fancyDomainName"

Any Idea, how I can tell my Netapp, that domainname is domain and fancyDomainName is just a UPN? "fancyDomainName" shoud get translated to "Domain"

Thanks

Sebe