If your server is 2003, it only supports .net by default, and does not support asp, so the following operations must be performed:

Open the local computer in iis6.0->web service extension

Just allow active server pages.

Problem 1: The parent path is not enabled

Symptom example:

Server.MapPath() Error 'ASP 0175 : 80004005'

Path characters not allowed

/0709/dqyllhsub/news/OpenDatabase.asp, line 4

Characters '..' are not allowed in the Path parameter of MapPath.

  Cause Analysis:

Statements such as ../ format are used in many web pages (that is, return to the page at the previous layer, that is, the parent path), and IIS6.0 is closed by default for security reasons.

  Solution:

In IIS Properties->Home Directory->Configuration->Options. Put a tick in front of "Enable parent path". Confirm refresh.

Problem 2: Improper configuration of ASP's Web extensions (applies to ASP.NET, CGI as well)

Symptom example:

HTTP Error 404 - File or directory not found.

  Cause Analysis:

In IIS6.0, the option of web program extension has been added, in which you can allow or prohibit programs such as ASP, ASP.NET, CGI, and IDC. By default, programs such as ASP are prohibited.

  Solution:

Select Active Server Pages in the Web service extension in IIS, and click "Allow".

Question 3: Improper identity authentication configuration

Symptom example:

HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.

Cause Analysis: IIS supports the following Web authentication methods:

Anonymous authentication

IIS creates the IUSR_computername account (where computername is the name of the server on which IIS is running) to authenticate anonymous users when they request Web content. This account grants the user the right to log on locally. You can reset anonymous user access to use any valid Windows account.

Basic Authentication

Use Basic authentication to restrict access to files on NTFS-formatted Web servers. With basic authentication, the user must enter credentials, and access is based on the user ID. Both user IDs and passwords are sent across the network in clear text.

Windows Integrated Authentication

Windows Integrated Authentication is more secure than Basic Authentication and works well in intranet environments where users have Windows domain accounts. In Integrated Windows Authentication, the browser tries to use the credentials of the current user during the domain logon process, and if the attempt fails, the user is prompted for a username and password. If you use Integrated Windows Authentication, the user's password will not be transmitted to the server. If the user is logged on to the local computer as a domain user, he does not have to authenticate again to access network computers in the domain.

Digest authentication

Digest authentication overcomes many of the shortcomings of basic authentication. When using digest authentication, the password is not sent in clear text. Alternatively, you can use digest authentication through a proxy server. Digest authentication uses a challenge/response mechanism (the mechanism used by Integrated Windows Authentication), where the password is sent in encrypted form.

.NET Passport Authentication

Microsoft .NET Passport is a user authentication service that allows single sign-on security to make users more secure when accessing .NET Passport-enabled Web sites and services. .NET Passport-enabled sites rely on the .NET Passport central server to authenticate users. However, the central server does not authorize or deny specific users access to individual .NET Passport-enabled sites.

  Solution:

Configure different identity authentication according to needs (usually anonymous identity authentication, which is the authentication method used by most sites). Authentication options are configured under IIS Properties->Security->Authentication and Access Control.

Question 4: Improper configuration of IP restrictions

Symptom example:

HTTP Error 403.6 - Forbidden: The client's IP address is denied.

  Cause Analysis:

IIS provides an IP restriction mechanism. You can restrict certain IPs from accessing the site through configuration, or restrict only certain IPs from accessing the site. range, an error message will appear.

  Solution:

Go to IIS Properties->Security->IP Address and Domain Name Restrictions. If you want to restrict the access of certain IP addresses, you need to choose to authorize access, and click Add to select the IP addresses that are not allowed. On the contrary, you can only allow access to certain IP addresses.

Question 5: IUSR account is disabled

Symptom example:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.

  Cause Analysis:

Since the account used by the user for anonymous access is IUSR_machine name, if this account is disabled, the user will not be able to access.

  Solution:

Control Panel->Administrative Tools->Computer Management->Local Users and Groups, enable the IUSR_machine name account.

Question 6: Improper setting of NTFS permissions

Symptom example:

HTTP Error 401.3 - Unauthorized: Access is denied due to ACL settings on the requested resource.

  Cause Analysis:

The user of the web client belongs to the user group. Therefore, if the NTFS permission of the file is insufficient (for example, there is no read permission), the page will be inaccessible.

  Solution:

Enter the security tab of the folder, configure user permissions, at least read permission is required. Regarding the NTFS permission setting, it will not be reported here.

Question 7: The IWAM account is out of sync

Symptom example:

HTTP 500 – Internal Server Error

  Cause Analysis:

The IWAM account is a built-in account automatically created by the system when IIS is installed. After the IWAM account is established, it is jointly used by Active Directory, the IIS metabase database, and the COM+ application program. The account password is stored separately by the three parties, and the operating system is responsible for the synchronization of the IWAM password stored by the three parties. The system's password synchronization work for IWAM accounts sometimes fails, resulting in inconsistent passwords for IWAM accounts.

  Solution:

If AD exists, select Start->Programs->Administrative Tools->Active Directory Users and Computers. Set a password for the IWAM account.

Run c:\Inetpub\AdminScripts>adsutil SET w3svc/WAMUserPass + password to synchronize IIS metabase database password

Run cscript c:\inetpub\adminscripts\synciwam.vbs -v to synchronize the password of the IWAM account in the COM+ application

Question 8: Some types of files cannot be downloaded due to MIME setting problems (take ISO as an example)

Symptom example:

HTTP Error 404 - File or directory not found.

  Cause Analysis:

IIS6.0 canceled the support for some MIME types, such as ISO, which caused the client to download errors.

  Solution:

In IIS, Properties->HTTP Header->MIME Type->New. In the subsequent dialog box, the extension is filled with .ISO, and the MIME type is application.

In addition, factors such as firewall blocking, ODBC configuration errors, web server performance limitations, and thread limitations are also possible reasons for the inability to access the IIS server, so I won't go into details here.