Publish .xsd file on IIS6

I have an .xsd file I would like published on my website (Win Server 2003, IIS6)

I assume that entering a URL of into IE should display the contents of the .xsd file... However, all I get is a 404 "File Not Found" error.
If I rename the file with a .xml the file displays as expected (so the file is definitely there!)

Having searched here and elsewhere for solutions I have confirmed the MIME type is set to text/xml, and there is no Application Mapping set for .xsd extension.

No entries appear in the log file when trying to access the .xsd file (but there are when the file extension is changed to .xml)

Any suggestions as to what else I could try?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Praveen DMInfra Team LeadCommented:
Praveen DMInfra Team LeadCommented:
Plz try configuring the XSD files with dll files as similar to aspx.. and add the MIME too and try accessing the same.. If u have a FW do add the extension is trusted list..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ReklawAuthor Commented:

Can you clarify what you mean by "If u have a FW do add the extension is trusted list"

The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

ReklawAuthor Commented:

I have tried mapping .xsd files to aspnet_isapi.dll as you suggest but it has no effect.
ReklawAuthor Commented:
Upping the points as it looks like this is a difficult one!
ReklawAuthor Commented:
Found the problem....
The firewall was blocking outbound .xsd extensions .... I didn't know it did that!
ReklawAuthor Commented:
I didn't realise FW was Firewall, sorry my lack of understanding.
Praveen DMInfra Team LeadCommented:
gr8.. In short we refer FW instead of Firewall and AV for Antivirus etc... Cheers Good luck...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.