Standalone Server win2003 System Site FAQ _ Server

Issue 1: Parent Path not enabled

Examples of symptoms:
Server.MapPath () Error ASP 0175:80,004,005
The Path character is not allowed
/0709/dqyllhsub/news/opendatabase.asp, line 4
Characters are not allowed in the Path parameter of MapPath ...

Reason Analysis:
Many web pages use things like. /formatted statement (that is, the page that returns to the previous layer, which is the parent path), and IIS6.0 for security reasons, this option is turned off by default.

Workaround:
In IIS, the properties-> the home directory-> configuration-> option. Check the "Enable Parent path" front. Confirm the refresh.

Problem 2:asp Web extensions improperly configured (same applies to asp.net, CGI)

Examples of symptoms:
HTTP Error 404-file or directory not found.

Reason Analysis:
The new Web application extension option is added to IIS6.0, where you can allow or disallow ASP, ASP.net, CGI, and IDC programs, which are prohibited by default.

Workaround:
In the Web service extension in IIS, select Active Server Pages and click Allow.

Problem 3:IUSR account is disabled

Examples of symptoms:
HTTP Error 401.1-Unauthorized: Access denied due to invalid credentials.

Reason Analysis:
Because the user is using anonymous access account is the IUSR_ machine name, so if this account is disabled, will cause users inaccessible.

Solution:
Control Panel-> Management tools-> Computer Management-> Local Users and groups, enable IUSR_ machine name account.

Problem 4:ntfs permissions set improperly

Examples of symptoms:
HTTP Error 401.3-Unauthorized: Access because the ACL's settings for the requested resource were denied.

Reason Analysis:
Users of a Web client are subordinate to the user group, so if the file has insufficient NTFS permissions, such as no Read permissions, it will cause the page to be inaccessible.

Solution:
Enter the Security tab of the folder, configure user permissions, or at least Read permissions. About NTFS permission settings are no longer fed here.


Problem 5:mime Setup problem causes some types of files to be downloaded (for example, ISO)

Examples of symptoms:
HTTP Error 404-file or directory not found.

Reason Analysis:
IIS6.0 has canceled support for some MIME types, such as ISO, causing client downloads to go awry.

Workaround:
The property->http header->mime type-> new in IIS. In the dialog box that follows, the extension is filled in. The Iso,mime type is application.