Windows authentication problems

The WindowsAuthentication Module is added at the Server level. The site does load if I turn off Windows Authentication and enable Anonymous obviously. Can anyone tell me what I might be missing here?

Improve this question. Aaronaught Aaronaught 2 2 gold badges 4 4 silver badges 13 13 bronze badges. Mind capturing a plaintext wireshark of the authentication attempt change your password to something throwaway first - we don't want your real password hashes on the net? ShaneMadden: I kind of do mind on account of all the various bits of information I'd be exposing, but I can do a Fiddler session which should be almost the same, and then I can at least anonymize IPs and so on - and in fact I already did, the results should be pretty self-explanatory the client is not showing the credentials prompt because the server isn't asking for any.

Oh, interesting, somebody seems to have reported this problem on Stack Overflow as well - no answers there, sadly. Aaronaught How did you get a different username here than on Cooking? When I first saw this question, I thought it was someone spoofing you.

Ward: Anybody can edit their username, it's part of the profile. This was my original one, only use others on the non-tech sites. Add a comment. Active Oldest Votes. It turns out that there are two Windows Authentication modules: On the server, the managed WindowsAuthentication module was there, but not the native WindowsAuthenticationModule highlighted above.

Improve this answer. ThoriumBR 5, 2 2 gold badges 22 22 silver badges 33 33 bronze badges. The managed WindowsAuthentication module isn't what it sounds like.

It's support for Windows identities in ASP. Net, and it's always installed when ASP. Net is installed. But the Windows Authentication native module is what gets installed when you tick the Windows Auth component in Server Manager, and that's what you need in order for that authentication option to become visible in the Authentication GUI. If I put on directory browsing I can see all the documents and files in the folder but if I try and access index. Description: An error occurred while accessing the resources required to serve this request.

The server may not be configured for access to the requested URL. Error message Verify that you have permission to view this directory or page based on the credentials you supplied and the authentication methods enabled on the Web server.

Contact the Web server's administrator for additional assistance. I have enabled anonymous access and I still get the error. If I try and view index. If there is another way to secure the site and I am doing it all the wrong way then I am open to suggestions. Ideally I want the entire site, sub-directories as well, locked down if your not in the access group, but open to everyone who is in the correct access group.

Look, there is no role provider in your web. Have you seen the login dialog prompt? Sign in to vote. User posted I am sorry, but I asked this question on the IIS 7 General forum but I have not get any reply and it has been more than 3 days already.

Windows Authentication is installed After I disable the "Anonymous Authentication" and enable the "Windows Authentication" things begin to acting really weir. I think there is a miss configuration that I must have done. Please show me if you know a fix for this, or any KB that explains this. In , Microsoft shipped updates to Windows that changed the default configuration of unconstrained delegation for Kerberos to disabled.

As resource SID compression is widely used and unconstrained delegation is deprecated, MaxTokenSize of or larger should become sufficient for all scenarios.

A MaxTokenSize value of 48, bytes should be sufficient for most implementations. This is the default value in Windows Server and later versions. However, if you decide to use a larger value, review the known issues in this section. This issue is similar in that a user who has too many group memberships cannot authenticate, but the calculations and conditions that govern the issue are different.

For example, the user may encounter this issue while using either Kerberos authentication or Windows NTLM authentication. For more information, see Logging on a user account that is a member of more than 1, groups may fail on a Windows Server-based computer.

Therefore, the Kerberos ticket is using percent of its original size. However, if you set the MaxTokenSize registry entry to 48, bytes, and you use the space for SIDs and claims, a Kerberos error occurs. Previous versions of this article discussed values of up to , bytes for MaxTokenSize.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.