Ummm.. good luck in IIS I have to add code to the page to get a clean 404 or 301. M$ seem to think the protocols are open to interpretation. If it's an .htm page and you don't have access to the asp parsing engine then there is little you can do. If you had access to the parser you could configure the server to parse .htm as .asp and add the code at the page level. Otherwise with newer IIS you basically send bad header responses to SE's. For instance if you set up a default 404 it will always return 200 code which is exactly opposite of the intent of the page.
