Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am deploying my web application on iis6. I kept receive this "windows security" pop up to enter user name and password.. I have already disabled anonymous user, and checked integrated windows authentication but it just wont "automatically" login.

What should i do?

I have check the security settings-local intranet zone: "login as automatic logon only in Intranet zone". Also my production server is a standalone server, and hence might not hold AD account and credentials.

share|improve this question

migrated from May 1 '12 at 19:21

This question came from our site for professional and enthusiast programmers.

What browser are you using? – Oskar Kjellin Apr 27 '12 at 9:35
both IE and Firefox wont work.. – Huatsin Yeo Apr 27 '12 at 9:52
you should potentially remove tags for visual studio 2010 and c# and and add tags for windows-server-2003 and iis6. Potentially move qeustion over to server fault an admin would be much better suited to tackling this question. – Anicho Apr 30 '12 at 14:53

For Internet Explorer, you might have to add the server address to the local intranet zone. IE often has a hard time detecting local intranet servers on its own, so you might have to manually add your site to that list. You can do that manually in IE settings or you can use group policies to manage a list of intranet servers within an AD domain. You can view the zone IE has chosen for your site from the menu File/Properties.

For Firefox, you have to tell FF to forward your network credentials to that site. in about:config you have to add the sites to the settings





share|improve this answer
hey because i am not an administrator, i cannt add the site to the zone. it is gray out! yes, i tried doing that on my local development pc and it works. But what should i do at the production server? – Huatsin Yeo Apr 30 '12 at 2:46
Nothing on the server. It's a client-side problem. You need to ask the client administrator to add the server name to the local intranet zone, or change the DNS name of the server so that it matches the settings already in that zone (for eg, if the zone is configured for * and your server is , make sure it's accessible via – TristanK May 2 '12 at 0:28 All you need to know, let me know how it goes.

I would love to rewrite this lovely article and take credit but that's cheating. I have fallen in the hands of this issue myself but this article was a life saver I keep it in my bookmarks under IIS solutions lol.


Let's get this straight you have I am presuming a windows server 2003/2003 r2 box or xp machine with IIS6.

Before we dig deeper check the following out make sure you have setup a new site in iis6, pointing to a folder in C:\inetpub\wwwroot\, if not there pointing to C:\MyOwnFolder or C:\Program Files\SomeFolder is fine you will need make sure folders have the following permissions:

Inetpub\wwwroot (or C:\MyOwnFolder) Administrators        Full control 
Inetpub\wwwroot (or C:\MyOwnFolder) System                Full control 
Inetpub\wwwroot (or C:\MyOwnFolder) IIS_WPG               Read, execute 
Inetpub\wwwroot (or C:\MyOwnFolder) IUSR_MachineName      Read, execute 
Inetpub\wwwroot (or C:\MyOwnFolder) ASPNET                Read, execute 


Now you should look into your IIS settings.

How to un-configure Authentication in IIS

  1. Start IIS Manager or open the IIS snap-in.

  2. Expand Server_name, where Server_name is the name of the server, and then expand Web Sites.

  3. In the console tree, right-click the Web site, virtual directory, or file for which you want to configure authentication, and then click Properties.

  4. Click the Directory Security or File Security tab (as appropriate), and then under Anonymous and access control or Authentication and access control, click Edit.

  5. Click to uncheck all options next to the authentication method or methods that you want are currently checked, and then click OK.

  6. Click to check enable anonymous access

  7. Make sure username is set to MACHINENAME\IUSR_MACHINENAME obviously replacing MACHINENAME with the name of your server/machine.

  8. IUSR is a built in account it should automagically authenticate it's self

Source: ( this article is the opposite of what I just showed you to do )

Try all this if does not work I will give some further steps, there are a billion and one things you can check.

share|improve this answer
sorry, im kinda confuse. becox i had tried so many ways, while my previous project was successful. maybe its because of the server, btw the "Internet Explorer's Intranet zone security setting" part is not working both on the client and server side, and i couldnt add the server address to client's browser becox they got no admin rights. – Huatsin Yeo Apr 30 '12 at 8:45
@HuatsinYeo I have updated my answer. – Anicho Apr 30 '12 at 11:18

You should check the files authentication in windows. Ex authenticated users group. There are two authentication that you need to take care of. IIS authentication and the file system access.

share|improve this answer

Before the application pool credentials kick in, the IUSR_computername account is used to load the configuration for the website. Make sure IUSR_computername account (also known as aspnet account) has read access to the folder where that application is deployed.

share|improve this answer
No, it's not. App pool credentials are the first thing used to boot and read configuration for an App Pool. – TristanK May 2 '12 at 0:26

Well, I am new to Dotnet I dont know if the solution that worked for me and the above is the same, but anyways here's what I did.

We were facing issues too in an upload utility and whenever the user clicked on "Upload" button, a pop up window kept popping up for asking for credentials(Which never hapened intially) and ultimately led to "401 invalid credentials" error.

You just have to go to the concerned folder/website in the IISNET manager on the server and right click and check the security. Add the users/ groups that should have access to upload and give them full permission if not present already.

Post this change they should be able to access/ upload the file without any credentials prompt.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.