Migrating from XP Pro IIS Admin to Modern IIS: A Step-by-Step Plan

Troubleshooting IIS on Windows XP Pro: A Practical XP Pro IIS Admin Handbook

Windows XP Professional’s Internet Information Services (IIS) is a lightweight web server useful for legacy apps, development, and testing. This handbook focuses on practical, actionable troubleshooting steps for common IIS issues on XP Pro (IIS 5.1). Follow the checks in order — start with basics, then move to configuration, performance, and security.

1) Verify IIS is installed and services are running

1. Open Control Panel → Add or Remove Programs → Add/Remove Windows Components → Internet Information Services — ensure it’s checked.
2. Check services:
   • Start → Run → services.msc → Confirm the IIS Admin Service and World Wide Web Publishing Service (WWW Publishing Service) are started.
   • If stopped, right-click → Start. Set Startup type to Automatic if needed.

2) Confirm site bindings and default document

1. Open Internet Information Services MMC (Start → Administrative Tools → Internet Information Services).
2. Under Default Web Site:
   • Verify the site is Started.
   • Right-click → Properties → Web Site tab → IP address/port: ensure correct IP (or set to “(All Unassigned)”) and port (default 80).
   • Host header: clear if none defined, or confirm hostname matches client requests.
3. Default Document: Properties → Documents tab → ensure default document (default.aspx, index.html, etc.) is present and listed in correct order.

3) Test basic connectivity

1. From the server: open a browser and navigate to http://localhost and http://127.0.0.1.
2. From the server using IP: http://.
3. From a client machine: http:// (or hostname).
   If server responds locally but not remotely, check network/firewall.

4) Check Windows Firewall and network settings

1. Windows Firewall (Control Panel → Windows Firewall): ensure port 80 (and 443 if HTTPS) are allowed. Add an exception for the IIS process (inetinfo.exe) or the port.
2. Router/NAT: ensure port forwarding for external access.
3. Verify no binding conflicts with other apps using port 80: open Command Prompt → netstat -ano | find “:80” and match PID in Task Manager.

5) Review IIS and system event logs

1. Event Viewer (Start → Administrative Tools → Event Viewer):
   • Check Application and System logs for IIS-related errors (W3SVC, Inetinfo, ASP.NET exceptions).
   • Note timestamps, error codes, and process names for targeted fixes.

6) Diagnose application errors (ASP/ASP.NET)

1. For classic ASP:
   • Enable sending detailed errors to browser: IIS Manager → Properties → Home Directory → Configuration → Debugging → check “Send detailed ASP error messages to client”.
   • Examine error messages and line numbers, then fix script issues.
2. For ASP.NET:
   • Check web.config for customErrors settings (set mode=“Off” temporarily to see full error details).
   • Ensure correct .NET Framework is installed and registered: run the appropriate aspnet_regiis.exe (for applicable versions).
   • Confirm application mappings: Properties → Home Directory → Configuration → Verify .aspx mapped to correct aspnet_isapi.dll.

7) Permission and authentication issues

1. File system permissions:
   • Ensure the content folder grants Read (and Write, if needed) to the IISIUSRS (or IUSR) account.
2. Authentication methods:
   • In Properties → Directory Security → Authentication and access control: verify Anonymous access, Integrated Windows authentication, or others as required.
   • For anonymous access, confirm the IUSR account and its password (Reset if necessary).
3. Script permissions:
   • If ASP scripts need COM components, ensure the COM objects allow access to the IIS worker account via DCOMCNFG.

8) Monitor performance and resource constraints

1. IIS 5.1 on XP is single-site, single-user limited: heavy traffic may exhaust resources quickly.
2. Check CPU, memory, and handle usage in Task Manager.
3. Use Performance Monitor (perfmon) counters: Web Service requests/sec, ASP Requests Executing, and Process% Processor Time for inetinfo.exe.
4. Recycle problematic applications by restarting the IIS services (IISReset) or rebooting the server when necessary.

9) SSL/TLS issues (HTTPS)

1. Ensure server certificate is properly installed: IIS Manager → Default Web Site → Properties → Directory Security → Server Certificate.
2. Verify bindings: port 443 and correct IP selected.
3. XP-era IIS supports older TLS versions—modern clients may reject weak ciphers. If modern client errors appear, consider using a reverse proxy or upgrading the server.

10) File upload and request limits

1. Classic ASP has script timeout and file size constraints; increase via scriptTimeout or Server.ScriptTimeout, and configure ASP buffers.
2. For applications using ASP.NET 1.x/2.0, increase maxRequestLength in web.config to allow larger uploads.

11) Common specific errors and fixes

• 403 Forbidden: Check NTFS permissions, directory browsing settings, and anonymous access.
• 404 Not Found: Confirm file exists, check default document list and virtual directory mappings.
• 500 Internal Server Error: Enable detailed errors,