I have a client who is trying to deploy a site that I designed in ASP.NET MVC, they are running IIS 6 and I've talked them through on how to setup wildcard mapping to make the clean URLs work.
However; when they attempt to go to the site they are still getting the normal page not found. Because for some reason the wildcard mapping isn't working.
What could be the issue?
In IIS 6 fo performance reasons there is no IIS level wildcard mapping to ASP.NET - this needs to be added in the IIS control panel.
The reason is that in IIS 6, asp.net runs external to the IIS core process (contrary to 7 where IIS is written in .NET), so they only forward what ASP.NET "should know about".
Customer should SERIOUSLY consider upgrading to IIS 7 ;)
Issue sounds the same as described in steve sandersons blog. I'd go for option 1. Why? Because you can then further mimic iis7 by doing things like hooking into the request-processing pipeline :-)
I had a similar problem, turns out it was because the aspnet_isapi.dll was not allowed.
Click Web Service Extensions in IIS Manager and check that ASP.NET v2.0.50727 is in the list and is allowed.