Friday, March 30, 2012

Login failed for user NT AUTHORITY\ANONYMOUS LOGON (but user.identity.name is correct)

I need help. The security principal is the correct Domain\User, but the error message says I am not authenticated.

So here is my error Message:

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Me.User.Identity.Name=CompanyDomain\Ryan; System.Security.Principal.WindowsIdentity.GetCurrent=CompanyDomain\Ryan; HttpContext.Current.User.Identity.Name=Company\Ryan

Generated by:

Dim

secPrincAs System.Security.Principal.WindowsIdentity = System.Security.Principal.WindowsIdentity.GetCurrentMe.lblError.Text = ex.Message & vbCrLf & vbCrLf &"Me.User.Identity.Name=" &Me.User.Identity.Name &"; System.Security.Principal.WindowsIdentity.GetCurrent=" & secPrinc.Name &"; HttpContext.Current.User.Identity.Name=" & HttpContext.Current.User.Identity.Name

Here is the Connection String:

Private ConnStringAsString ="Server=10.144.162.111;Database=DNS;Trusted_Connection=True"

IIS has 4 websites hosted on it. The parent level allows anonymous with windows auth off, but the website level has anonymous off with widnows auth and digest.

In IIS, is there a problem with having the parent level anonymous and website level windows auth?

I think i found the error. My web server is a different machine from my data server. When my browser connects to the webserver it uses impersonation and delegation, but the web server is not trusted for delegation on the active directory. So when the webserver tries to pass the credentials to the data server the domain controller will not allow it.

Working on a 3 tier setup here...

Ryan

No comments:

Post a Comment