I submitted this ticket and was told I should post the problem in the forums. Can anyone figure out why I'm doing the right thing (according to support) but not getting the right result? Surely using custom error pages isn't that unusual. So why isn't it working? ---------------------------------------------------------- I logged into IIS7 manager & navigated to the password-protected folder (the one I set "deny anonymous users" to). I clicked Error Pages. I added entries for status code 401.1 and 401.2 (the codes that came up when I clicked cancel from the user login prompt on the website). For each I selected "Execute a URL on this site" and typed in the path to the error page. When I did all this, nothing changed. The same user-unfriendly error page came up when I clicked cancel from the user login page on the website. There's an alert on the Error Page config page that says "You have configured detailed error messages to be returned for both local and remote requests. When this option is selected, custom error configuration is not used." So I clicked Edit Feature Settings and changed Detailed errors to Custom errors, and I set the default page to the same one I set in the 401.1/401.2 entries (along with Path type to Execute URL). As a consequence of doing that, the login did not come up. When I clicked the link that points to the page in the password-protected folder, I went straight to the error page (the one I specified in Feature Settings). There was no user prompt -- just the error page. When I switched the settings back to Detailed errors, I got the login prompt but not the custom error page (same as before). Shouldn't I be able to have both a custom error page AND the login prompt? I find it odd that changing the error page settings took away the login. Site: http://asghoust.w05.Winhost.com/ Protected folder: /member_services/newsletter/newsletter_secure Error page: /member_services/newsletter/error.aspx BTW, the login itself works fine. When I enter the correct username/pw, it's peachy.