Re: Peculiar IIS behavior

Josh Hillman ( (no email) )
Mon, 5 May 1997 19:00:38 -0400

From: SMPnet <>
Subject: Re: Peculiar IIS behavior
Date: Monday, May 05, 1997 2:44 PM

This is not correct. The default for all sites root or virtual is
what you set it to. When you first install IIS it's default.htm.
You then change it for ALL sites by changing it in the IIS manager.

I know. I had changed it from "default.htm" to "index.html" a few minutes
after installing IIS around 8 months ago... Either way, every directory on
the local drive/partition (including root) respond just fine when leaving
"index.html" off the URL. Only the root directory on the UNC listed share
(physically located on another machine) doesn't respond without putting
"index.html" at the end of the URL. All other directories on that system
do work fine without referencing the file, and permissions are the same
throughout all of the directories on that same partition.

Josh Hillman

Josh Hillman wrote:
> > It sounds like the IIS anonymous user account on the server does not
> > at least read permissions for the directories in question. If a
> > box pops up when you try to access these sites with Netscape, that is
> > almost certainly your problem. We keep a copy of Netscape just for the
> > purpose of checking that we have virtual directories set up properly.
> > Netscape is very fussy about the permissions where the newer Internet
> > Explorers you what ever account you are logged in as and if you have
> access
> > normally it will give you access with the browser also. We had a
> > problem a while back.
> I can't remember if I already responded to this or not, but permissions
> not the problem here and nor is the name of the "default file". In IIS,
> "index.html" has always been the default file and as far as permissions
> it can't be that either because the file does pull up, IF it's directly
> referenced--but this only needs to be done in the root directory. All
> subdirectories respond just fine without referenceing index.html. It's
> if IIS thinks that "/testwww" is a FILE in the root directory on the
> E: drive (where all the other webfiles are) instead of responding to
> "/testwww" as being a directory where it's supposed to be looking (UNC
> referenced drive (root directory) on another server. It only responds as
> directory when "/index.html" or some other file or subdirectory is
> referenced at the end of the URL.
> Here's the original message I sent out:
> I noticed this peculiar behavior with IIS 3.0 and was wondering if anyone
> else has run into it:
> I have a second hard drive in one our servers that I've partitioned
> into two 1GB partitions. On one of those partitions, I took the root
> directory (H:\) and shared it so that it could be accessed by IIS 3.0
> (running on a different machine in the same domain).
> The directory and files are:
> H:\index.html
> H:\temp\index.html
> When enter in the following URLs, I get the following responses:
> http://mywebserver/testwww (as well as http://mywebserver/testwww/)
> HTTP/1.0 404 Object Not Found
> http://mywebserver/testwww/index.html
> (displays the "index.html" page normally)
> http://mywebserver/testwww/temp
> (displays the "index.html" page normally)
> The problem is that it's not displaying the index.html file by
> ONLY in the root directory, wheareas in other subdirectories, it does
> display index.html automatically (without having to type it in the URL).
> In IIS, here are the settings:
> Directory: \\machinename\www
> Virtual Directory: /testwww
> Account info: (using an account/password for use with the shared
> resource)
> Access: Read
> Enable Default document: index.html
> Directory Browsing: (not allowed)
> There are no errors displaying anywhere (including Event Viewer).
> Any idea why this is happening?
> Josh Hillman
> ----------------------------------------------------------

> NTISP Mailing List

NTISP Mailing List