404 even though file exists, mappings and permissions set

I have locked down my IIS on XP Pro, and am now testing the config. I have navigated to 127.0.0.1 and 'Default.asp' is parsed and displayed as its in my default documents list. When I rename the file to 'foo.asp' and try navigating to 127.0.0.1/foo.asp I get a 404.

What gives?

Thanks.

Try restarting IIS after you rename the file, or add a new file rather than renaming the default file.

Thanks for the reply Doug, I have tried that but I'm still getting a 404. I think I will go through the various log files and see if that helps, else I will have to reinstall IIS and lockdown manually so that I can see what's causing the problem.

If you ran the IIS lockdown tool I believe you can run it again to undo changes.

You might take a look at the NTFS file permissions on your virtual directory, maybe new files don't inherit proper permissions for the anonymous IIS user account.

Just a couple guesses.

Thanks for your suggestions.

I think I've fixed it

I have found out that static pages and cgi scripts don't have the problem as described with the asp file. So I re-mapped asp files to the html extension and it works now.

I think it might have been some kind of persistancy error, when I checked the mappings after lockdown the asp files were all mapped to the 404 dll. I have since overrided the asp mappings to re-enable them, but it seems that the previous config was still live some how?