Hi folks - I'm asking here 'cause this is driving me nuts :-)
Scenario: I have laptop onto which our IT guys have installed XP Pro (and a Whole Bunch of Other Stuff, but that shouldn't be relevant - I hope) They know next to nothing about IIS so it's a vanilla-flavoured install. I have the task of recreating our two corporate intranets to demonstrate to our parent company in a location where they have *no* network connection in, oh... another fifteen hours time...
But I digress.
I've got everything working *except* I cannot get Perl CGI files to run - I just get a 404. Now I realise this is what happens if URLSCAN is installed, but I don't think our IT guys even know what URLSCAN is and I certainly cannot find any evidence either URLSCAN or IISLOCKDOWN has been installed/run on this laptop. (Question 1 - what does URLSCAN look like under XP Pro?)
I know Perl is installed OK (I've installed it on dozens of IIS servers before, I've checked the application mappings - they are OK and I can run Perl from the command line) To prove that I'm using the correct URL I've turned on directory browsing and all the scripts are listed in the browser (oh, IE5.5 and IE6 if that makes any difference) If I click on "fred.txt" I get to see the contents of that file, but if I click on "fred.pl" (Hello world) I simply get a 404. The IIS log file also shows a 404.
I've got lots of experience with IIS4, 5 & 6 but IIS 5.1 seems a bit odd, but that could be because it's XP Pro and not a Server version of Windows hence a lot of IIS options are missing.
I wonder if it's some bizarre security thing. I never use anonymous access as all users are part of NT Domains here. Because this is a stand-alone demonstration I have set the EVERYONE group to have full access to everything (R/W and Execute) so I can't see how it's permissions-related. And in any case I would have expected errors other than a 404.
I've run out of ideas. Over to you :-)