You have the right conceptual idea, though the details are wrong.
<font color=purple> > For example, if I go to the resouce <a style='text-decoration: underline;' href="http://myserver/some/path</font" target="_blank">http://myserver/some/path</font</a>>
> and it has AuthNTLM, then the user I login as (or am logged in
> as) will be the user the IIS process runs at, and thus should
> have the same level access I the user have access to. Correct?
IIS process does not run as the user that is logged in as. IIS runs with a
known (and configurable) process identity on the server, and it obtains a
user token from your authentication protocol. IIS then takes this user
token and "impersonates" a thread with this token. It is this thread that
does all the work on your behalf on the server and is your identity.
Threads can also call "RevertToSelf" to strip off the impersonation token
and execute as the process identity.
As for your actual question:
I suspect you will see all the 404 errors listed in the W3SVC web logs with
a substatus of "3". This behavior is by-design, and please read
troubleshooting or "what's new/changed" in F1-help of IIS Manager for more
details.
One of the fundamental changes in IIS6 is that static files are not
downloadable/browsable by default, and dynamic files are not executable by
default. The former is denied by 404.3, and the latter by 404.2. This is
for security reasons -- we don't want .ASP files to be downloadable nor
executable by default unless you configure it.
You enable static files to be downloadable/browseable by adding MIME Type
for the particular file extension. You enable dynamic files from executing
by adding/enabling a Web Service Extension for that dynamic file.
In your situation, I suggest you add a MIME Type for the .mp3 extension
under the virtual directory that you created. This allows the .mp3 files to
be downloadable. Since you enabled directory browsing, I would also make
sure that no default document exists in those directories if you wish to get
a directory listing.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"ee99ee" <cmiller RemoveThis @compuville.net> wrote in message
news:a8491f4f.0407070321.2fe2c3f8@posting.google.com...
I have made a virtual directory on one of my personal sites on my
server pointing to a local path where I have some MP3s I want to be
able to access via HTTP. I'm running IIS 6.0 on Windows Server 2003
Enterprise. I have turned on directory browsing, disabled the default
content page, disabled anonymous access and enabled windows
authentication. I am on a domain.
I go to the address, but instead of getting a directory listing I get
a 404 error. I have double-checked the path, and that I do have
permission to access the resouce. I can access the resouce as the same
user over a network share, so I defintly have read access. Why am I
getting a 404 error instead of a directory listing?
I really have no idea what's going on. With anonymous access diabled,
and AuthNTLM on, the IIS process runs as the authenticated user,
right? For example, if I go to the resouce <a style='text-decoration: underline;' href="http://myserver/some/path" target="_blank">http://myserver/some/path</a>
and it has AuthNTLM, then the user I login as (or am logged in as)
will be the user the IIS process runs at, and thus should have the
same level access I the user have access to. Correct?
-ee99ee<!-- ~MESSAGE_AFTER~ -->
FAQ
Profile
Private Messages
Log in
