Host Headers for multiple websites not working

[teddarr]

I have a Windows Server 2003. I am trying to run multiple websites on the server.

I have 3 different websites I'd like to run.

Currently the default website is working but no others.

All the domains have an a record pointing to the network router. The router is conficured correctly to send all website requests to my server.

One the server and for each website I went to the IIS manager on the Websites tab and have the IP address set up as the server's IP. I click the advanced button and add a value. I use the server IP, port 80 and the host header value such as www.example.com .

On the Home Directory tab, I have the correct local path specified, And I have Scripts and Executables for the Execute permissions. I have also created a separate Application Pool for each website and have that application pool specified on the home directory tab.

When I type in the url for the desired website using the iis default website all works great. When I type in the url for one of the domains I want to use host headers for I get a runtime error. The web app works great on the development server and when used as the default website in IIS, but will give the runtime error only as a host header.

Any ideas?

[teddarr]

Here's the error I'm gettong and I do have custom errors set to "Off" so I don't know why I'm getting this errpr:

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors > tag within a "web.config " configuration file located in the root directory of the current web application. This <customErrors > tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
</system.web>
</configuration>

[JamieHowarth0]

Hi teddarr,

Are you using SSL on any of the sites in question? And are you explicitly specifying IP addresses to listen on, or using "All Unassigned" when adding host headers to sites?

Best,

codegecko

[JamieHowarth0]

Hi teddarr,

Are you using SSL on any of the sites in question? And are you explicitly specifying IP addresses to listen on, or using "All Unassigned" when adding host headers to sites?

Best,

codegecko