IIS 5.0 with host headers: If the Sales web site is stopped, what response will a user receive when requesting the Sales host-header URL?

Introduction / Context:
Internet Information Services (IIS) 5.0 can run multiple sites on the same IP/port using host headers. When a specific site is stopped, IIS no longer serves content for that host header. Understanding the HTTP status returned in this condition helps troubleshoot user reports and confirms whether the site state, permissions, or content is at fault.

Given Data / Assumptions:

• Two sites exist (HR and Sales) configured with host headers.
• The Sales site has been stopped for maintenance.
• Users access by the Sales host name; no alternate bindings exist.

Concept / Approach:
When IIS receives a request for a host header that maps to a stopped site, IIS cannot route the request to an active application context. Rather than redirecting, IIS returns an error indicating the requested resource cannot be found. In IIS 5, this typically surfaces as HTTP 404 for that host header request, differentiating it from permission errors (403.x) or application errors (500.x).

Step-by-Step Solution:

Verification / Alternative check:
Use IIS Manager to confirm site state. Start/stop the site and repeat the request; observe 404 when stopped and 200 OK when running.

Why Other Options Are Wrong:

• IIS does not auto-redirect to another site or an alternate page when a site is stopped.
• 403.2 indicates read access denied on an active site, not a stopped one.

Common Pitfalls:
Confusing a 404 due to a stopped site with a 404 due to missing files; always check site state first.

Final Answer:
The user receives a 404 – File Not Found error