As posted in the original message I had sent, it's set to "index.html" like
it always has been. The problem is only occuring on the UNC listed root
directory--subdirectories work fine. The actual root to our primary
website is the root directory of a partition (drive letter, E) on the same
drive in which IIS 3.0 resides. There are no problems there at all.
Here's the original message again:
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 (NTFS)
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 default--but
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).
Josh Hillman
hillman@talstar.com