NT4 + IIS 4.0 + New web site = 403 Forbidden ??? Any ideas ??

[technodave]

The default web site works fine, I put it on port 81 so I can use port 80 for my own personal web site. I'm 99.9% positive that I duplicated all the settings of the default web site for my own personal site, but I get a 403 forbidden error what I try to connect to it via //server or http://127.0.0.1 But here's the weird part ... if i put in http://127.0.0.1/index.htm , it works just fine, and I can browse the site from there. It just seems as if it's not making the initial step correctly.

The permissions both in IIS and the actual directory are the same. Anonymous access is allowed, and all that other good stuff ... what am I missing ??

 

[Poof]

Did you tell it that "index.htm" is the "default" page to use?

 

[technodave]

yep, sure did ... still no dice ... any other ideas??

 

[technodave]

Even weirder ... I went back and made sure that index.htm was the default webpage and somehow it was removed. I put it back and now it shows the IIS DEFAULT web page with Red 'X' boxes instead of the pics, instead of 403 forbidden Why is my index showing that page??

The default page on my Davesis index.htm
and the Website path is C:\Inetpub\Dave
the IIS4 default website path is c:\Inetpub\wwwroot

 

[Poof]

Sorry for the delay in responding. Had some power outages here when some nasty storms came through and a couple of my OC'd machines on UPSes that had managed to lock up (due to the rise in ambient temp in here, 'cause the ACs were off), decided not to POST when I rebooted them :|. So I've been spending the past couple hours troubleshooting and trying to cool it down in here.

Anyway - I think you maybe answered your own question. That default web page that's setup right now is what will BE your page.... regardless. However, in order to change this, you'll have to see if you can setup what are called "virtual" websites.

I did this a long time ago with IIS 4, but I did it by multihoming (assigning multiple IPs to a single NIC) and assigning each website it's own unique IP. If you're doing this at home with "reserved" IPs (eg., the 192.x.x.x), then there's no problem setting up your own site as a virtual one with a different IP/URL than the "default". But if you're doing this for viewing on the internet, then I think you'll need to have at least 2 "real" IPs to do it.

There may be a way to setup virtual websites and map them to different URLs and all using the same IP, but I've never done it with IIS, so I'm not sure if it's possible or not.