An example of IIS failure and resolution

An example of IIS failure and resolution
Author: unknown Source: Network

I have encountered IIS authentication at the same time the ASP program can not run the situation, because the problem is more representative, so summed up, take out, I hope for everyone later in the face of similar problems to provide a reference.
Problems and Solutions:
When you are finished configuring the server, the Validation dialog box always appears when you open the Web site. By convention, think about what changes you made when you configured your server:
1, set the Group Policy
Account Policy
A. Passwords must meet security requirements
B. Minimum password length of 8
Account Lockout Policy
A. Account lockout threshold
2, installed the IIS Lockdown2.1 tool
Because the validation section is configured in the Iis-> directory security-> authentication method, the first priority is to troubleshoot there, by default, the authentication method should be configured to:
1, [checked] anonymous access
2. [Not selected] Basic validation
3, [checked] Integrated Windows authentication
No problem, then click the "Edit" button under Anonymous access to check anonymous access configuration, by default
1, the user name is IUSR_computername (ComputerName is the same as the machine name)
2, the password should be gray can not be entered.
3, [checked] allow IIS to control the password
After comparison did not find any problems, because the IUSR_computername account password is created automatically, will it be because the password mismatch caused? Then, in the Computer Management to reset the security requirements of the password, and then return to "edit", the first move to allow IIS to control the password, and then in the Available Password box to enter the password just set, and then select "Allow IIS to control the password", test, Fix! The prompt for the password is no longer present.
However, new problems have arisen, whenever the user accesses the ASP page, there will be 500 error, and the display text page does not have a similar problem, the first thought is only the problem of the program, so the site root directory to create a blank text file, renamed ASP file, still appear 500 error.
It is the most likely to feel IIS Lockdown, so I first focus on its configuration, open the site-> home directory-> application configuration-> application mapping, and then see the. asp file mapping is correct (asp.dll).
When the log is checked, the Dllhost.exe process (the IIS process) does not start, and Dllhost.exe is controlled by IWAM_computername, so turn on computer Management again to view IWAM_computername users. Surprised to find the original account was locked, unlock, ok! You can browse the ASP program normally.
Description
This article is the first two days in the configuration of the server to solve the problem of a summary, because at that time was handled at about 2 o'clock in the morning, did not do a good record, so the middle of some of the process is not very detailed, I hope you understand.