Of course, checked many times.
Main Topics
Browse All TopicsMy ASP.NET application needs to run in a separate application pools with configurable identity enabled. I also need to have anonymous access DISABLED and Integrated windows authentication ENABLED. The user that my application pool is run under is the admin on the box and also a member of IIS_WPG group.
Under these conditions, when I try to access the website from a client computer (not the server itself) it asks me for a password. I tried to enter admin's credentials, but it would not take it. WHY? It's not supposed to prompt for a password at all. What am I missing? The NT(file) permissions are open for everyone (full control) in the website. Do I need to make my application pool user part of any other NT group on the web server, besides IIS_WPG?
Interesting observations: When I enable anonymous access, I don't get the password prompt (although my application throws an error, because it needs to know who is logged in). Secondly, when I access the website from the web server itself (using localhost), everything works fine. I am puzzled, please help.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
When you look in the IIS logs, what return code do you get for: your first attempt to use the website, your failed login attempt, success on the local machine.
Specifically, is your browser passing your credentials to the app correctly? If it is passing credentials, is it passing the right credentials to the application?
Yes, the application is impersonating. But if I run the application in an application pool with configurable identity, I don't need to use impersonation anymore. So I tried with or without it, same result. The only way I made it work (kind of) now is to use Basic Authentication disabling windows integrated one. Since it is an intranet app, users expect NOT to enter a password (we support IE only), but now they do, which is not a big deal since they can save the password for future logins. Anyway, I still don't understand what is going on with the password prompt and windows integrated authentication.
The problem is that you haven't configured your environment properly for Kerberos authentication delegation. Your users are ending up using NTLM authentication and that can't be passed from the web server to anywhere else to authenticate to other resources. This results in the remote resource server sending an authentication failure messgae back to IIS so IIS aks the browser for different credentials and IE prompts you to enter new credentials.
The fact that Basic works pretty much conforms this - it doesn't need any special configuration. Since you send your userID and password the server can get a token as you and pass that to another machine to authenticate.
Dave Dietz
I went round and round on this one myself. I am not 100% sure you need to do this as at some point I got confused in my 's**t thowing' :-) exercise.
If you really don't want to set up Kerberos and are fine with NTLM, I 'think' this will work. (note that the scripts are located in the path below. I bolded the command.)
C:\Inetpub\AdminS
I was also confused about the ipersonate tag in web.config. To actually get the app to use the identity I set I had to use this in web.config. Maybe the stuff I read I misunderstood but at this point, it works as expected.
<authentication mode="Windows"/>
<identity impersonate="false"/>
Oh, and if it does turn out to be Kerberos and you want to fix that...check this link. I am not an expert but it seems straight forward.
http://msdn.microsoft.com/
Business Accounts
Answer for Membership
by: AmirchoupaniPosted on 2009-01-21 at 13:02:01ID: 23433947
have you entered the correct credential: r?
domain\administrator or WebServerName\administrato