On Jun 16, 8:06 pm, Steve in Santa Rosa
[quoted text, click to view] <SteveinSantaR...@discussions.microsoft.com> wrote:
> The web page has a link to the MP3 files, just like links to other HTML or
> PDF files that do load successfully. Thus the browser, in this case IE6,
> requests the MP3 from IIS using HTTP. The IIS log for each unsuccessful
> attempt to load an MP3 file shows several entries:
>
> 1) Anonymous IE6 gets status 401 for the file (usually twice), then
> 2) (Sometimes) anonymous WMP 9 gets status 404 for a non-existant file with
> the same name, but an extension of .smi, then
> 3) (Sometimes) IE6, showing the authenticated user, gets status 200 for the
> original file request, then
> 4) Anonymous NS Player 9 gets status 206 for the original file request, and
> that ends it.
>
> The same workstation (browser, player, etc.) functions flawlessly accessing
> an identical IIS 5 site on a windows 2000 server that was copied onto the new
> problem IIS 6 site. I have never seen any reference to a search for a
> non-existant .smi file (whatever that is) in the old server logs, nor is
> there any reference to any such file in any of the HTML. Also, when the
> "Users" group is given NTFS permissions to access the folder and files, the
> same user and workstation can access the MP3 files just fine.
I need you to provide verbatim IIS log entries for a single user
initiated failed attempt to retrieve a MP3 in your protected website
area.
I do not understand what you are describing with steps #1-4 because
you talk about anonymous IE6, anonymous WMP, and NS Player 9, which
are three different clients (to me) and I do not understand their
relationship to the single user initiated failed attempt to retrieve a
MP3.
My suspicion is that you have custom software running on IIS5 that is
not running or malfunctioning on IIS6 to result in this behavior --
because by default, HTML, PDF, and MP3 files are all handled by the
IIS6 static file handler which treats them the same, so if your
secured part of the website also transfers those resource types
successfully, then I do not believe the issue has to do with IIS6.
The issue may be with difference in website configuration on IIS5 and
IIS6. Even if you have identical configuration, most functionality on
IIS6 is disabled while on IIS5 it is enabled, so you may have to
figure out what additional functionality you relied on IIS5 that is
not enabled by default on IIS6 -- this is reasonable for security
purposes.
//David
http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //