Dedicated Server Win2003 System Site FAQ

Standalone server win2003 system site FAQ

Problem 1: Parent paths not enabled

Example symptoms:
Server.MapPath() error ASP 0175 : 80004005
Disallowed Path characters
/0709/dqyllhsub/news/OpenDatabase.asp, line 4
The .. characters are not allowed in the Path parameter of MapPath.

Cause analysis:
Many Web pages use statements such as ../ (that is, returning to the previous-level page, i.e. the parent path), and for security reasons IIS6.0 disables this option by default.

Solution:
In IIS, Properties->Home Directory->Configuration->Options. Check the box before "Enable Parent Paths". Confirm and refresh.

Problem 2: Improper configuration of ASP Web extensions (also applies to ASP.NET, CGI)

Example symptoms:
HTTP Error 404 - File or directory not found.

Cause analysis:
IIS6.0 added a Web program extensions option, in which you can allow or prohibit programs such as ASP, ASP.NET, CGI, IDC, etc. By default, programs such as ASP are prohibited.

Solution:
In IIS, in Web Service Extensions, select Active Server Pages and click "Allow".

Problem 3: IUSR account is disabled

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

Cause analysis:
Because the account used for anonymous user access is IUSR_machine name, if this account is disabled, users will be unable to access.

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

Problem 4: Improper NTFS permission settings

Example symptoms:
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.

Cause analysis:
Web client users belong to the user group. Therefore, if the NTFS permissions for the file are insufficient (for example, no read permission), the page cannot be accessed.

Solution:
Go to the Security tab of the folder and configure the permissions for user, at least granting read permission. NTFS permission settings will not be further elaborated here.

Problem 5: MIME setting problems cause some types of files to be unable to download (using ISO as an example)

Example symptoms:
HTTP Error 404 - File or directory not found.

Cause analysis:
IIS6.0 removed support for some MIME types, such as ISO, causing client download errors.

Solution:
In IIS, Properties->HTTP Headers->MIME Types->New. In the dialog that follows, enter .ISO for the extension and application for the MIME type.