I have a Windows 2003 web server that is serving up 3 public-facing websites via IIS6. The all run under the Default App Pool.
I have added a new, very simple, one page website to serve as a "Maintenance" website. It is setup with anonymous access enabled, and all 404 errors redirect to /index.html.
I basically stop the other 3 websites and start the Maintenance website when it is needed.
The other three websites function normally all day long.
However, the Maintenance website presents users with a login credentials dialog and/or responds with a 401.1 code. I tried adding the IIS_USR account to the directory security with Read and Read & Execute access, but I still have the same result.
I have a very similar setup on three other servers, which serve up additional public-facing websites.
What is going on and how can I fix this?