404 Error: Site Not Found
- A guide to resolving the "File or directory not found" error when a web site is not accessible on the requested port.
- The HTTP Error 404.1, encountered within Internet Information Services (IIS), signals that the web site you are attempting to access is hosted on an IP address configured to...
- If you encounter this error, consider the following steps to resolve the issue:
Troubleshooting HTTP Error 404.1 in Internet Information Services (IIS)
Table of Contents
A guide to resolving the “File or directory not found” error when a web site is not accessible on the requested port.
Understanding the HTTP Error 404.1
The HTTP Error 404.1, encountered within Internet Information Services (IIS), signals that the web site you are attempting to access is hosted on an IP address configured to reject requests specifying a port number. This error, specifically “File or directory not found: web site not accessible on the requested port,” indicates a configuration issue preventing access to the desired resource.
Troubleshooting Steps for HTTP Error 404.1
If you encounter this error, consider the following steps to resolve the issue:
- Verify the Web Site Address: “Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.”
- Report Incorrect Links: “If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.”
- Navigate Back: Click the back button to try another link.
Technical Information for Support Personnel
For those with technical expertise, further investigation and resolution may involve the following resources:
- Microsoft Product Support Services: Go to Microsoft Product Support Services and perform a title search for the words HTTP and 404.
- IIS Help: Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled hosting Multiple Web Sites on a Single Server, Port Assignments for Internet Services, and About Custom Error Messages.
Additional IIS Error Codes
Beyond the HTTP Error 404.1, IIS utilizes a range of HTTP status codes to communicate the outcome of client requests. Here’s a brief overview of some common codes:
- 200 – OK: “IIS 7.0 successfully processed the request.”
- 304 – not modified: “The client browser requests a document that is already in the cache, and the document has not been modified since the document was cached.”
- 403.12 – Mapper denied access: “The page that you want to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file.” this can occur on Microsoft Windows 2000 Professional and Microsoft Windows XP Professional, which “automatically impose a 10-connection limit on IIS.”
“`html
Troubleshooting HTTP Error 404.1 in IIS: Frequently Asked Questions
A comprehensive guide to understanding and resolving the “File or directory not found” error when a website is not accessible on the requested port in Internet Data Services (IIS).
What is HTTP Error 404.1 in IIS?
Question: What does the HTTP Error 404.1 mean in Internet Information Services (IIS)? What are the common causes of this error?
Answer: The HTTP Error 404.1 in IIS means “File or directory not found: web site not accessible on the requested port.” This error indicates that the web server cannot find the requested resource on the specified port. Common causes include:
- The website isn’t bound to the correct IP address and port combination.
- The specified port number is incorrect or not configured in IIS.
- Firewall rules are blocking access to the port.
- DNS resolution issues prevent reaching the correct IP address.
How do I troubleshoot HTTP Error 404.1?
Question: What are the steps to troubleshoot and resolve HTTP Error 404.1?
Answer: Follow these steps to troubleshoot HTTP Error 404.1:
- Verify the Web Site Address: Carefully check the spelling and formatting of the URL in the browser’s address bar. A simple typo can lead to this error.
- Check IIS Bindings: Ensure that the website in IIS is correctly bound to the IP address and port being used. Go to IIS Manager, select the website, and check the “Bindings” settings.
- Firewall Configuration: Make sure that the firewall allows traffic on the port the website is using (usually port 80 for HTTP and 443 for HTTPS).
- DNS Resolution: Verify that the DNS record for the website resolves to the correct IP address of the server.
- IIS Logs: Examine the IIS logs for more detailed information about the error. The logs are typically located in
%SystemDrive%inetpublogsLogFiles. - Test with a simple HTML file: Place a basic HTML file (e.g., `index.html`) in the website’s root directory and try to access it. This helps determine if the issue is with the application or IIS configuration.
How do I check IIS bindings?
Question: How do I verify the website bindings in IIS to ensure they are correctly configured?
Answer: To check IIS bindings, follow these steps:
- Open IIS Manager (inetmgr).
- in the connections pane, expand the server node and then the Sites node.
- select the website you are troubleshooting.
- In the Actions pane, click on Bindings…
- In the Site Bindings dialog, review the bindings for the site. Ensure that the Type (http or https), IP address, and Port are correctly configured. The IP address can be set to “All Unassigned” if you wont the site to respond on all IP addresses.
What other HTTP status codes are important in IIS?
Question: Besides 404.1, what other HTTP status codes should I be aware of when managing an IIS server?
Answer: IIS uses a variety of HTTP status codes to communicate the outcome of client requests.Here are some common codes you should be familiar with:
- 200 – OK: The request was successfully processed.
- 301 - Moved Permanently: The requested resource has been permanently moved to a new URL. This is frequently enough used for SEO purposes.
- 302 – Found (Moved Temporarily): The requested resource has been temporarily moved to a different URL.
- 304 – Not Modified: The client’s cached version of the resource is still valid and doesn’t need to be re-downloaded.
- 400 – Bad Request: The server could not understand the request due to malformed syntax. [1] outlines sub-status codes like 400.1 (Invalid Destination Header) and 400.2 (Invalid Depth Header), which provide more specific details.
- 403 - Forbidden: The server understood the request, but is refusing to fulfill it.This frequently enough relates to permission issues.A specific example is 403.12 - mapper denied access which is tied to client certificate issues on older operating systems.
- 404 - not Found: The server could not find the requested resource.
- 500 – Internal Server Error: A generic error message indicating that something went wrong on the server. Reviewing server logs is crucial for diagnosing the root cause.
- 503 – Service Unavailable: The server is temporarily unable to handle the request due to maintenance or overload.
Where can I find more technical support for IIS?
Question: Where can I find additional technical resources and support for troubleshooting IIS issues?
Answer: You can find technical support through these resources:
- Microsoft Product Support Services: Go to Microsoft Product Support Services and search for relevant keywords like “HTTP” and “404.”
- IIS Help: Open IIS Help directly within IIS Manager (inetmgr). Search for topics such as “Hosting Multiple Web Sites on a Single Server,” “Port Assignments for Internet Services,” and “About Custom Error Messages.”
- GitHub: The repository how-to-use-http-detailed-errors-in-iis.md provides helpful documentation on configuring custom and detailed errors for troubleshooting.
Common IIS HTTP Status Codes
Question: Can you provide a speedy reference table summarizing some of the common IIS HTTP status codes and their meanings?
Answer: Here’s a table summarizing common HTTP status codes in IIS:
| Status Code | Description | Common Causes |
|---|---|---|
| 200 OK | Request was successful | Normal operation |
| 304
Related reading |