Windows Forum

Ask something
Discussion Locked

Multihoming problems with IIS 4

0 helpful
8 replies

by ds9

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have recently switched to all Microsoft products, and are having problems Multihoming web sites on Internet Information Server, Ver 4.0

The OS is Windows NT Server Ver 4.0 with service pack 6a

IIS4 indicates that to multihome sites, one of the following items must be different. The IP number, port #, or the "host header".
To conserve IP numbers, we selected IP and port to be the same, and use different host headers. We tried the Nickname as the header, doesn't work. We tried the File Folder name, doesn't work. We are beginning to believe that we do not understand what MICROSOFT calls the "Host Header".

Can anyone give us a hint....????

8 replies

by mckaytech

For a couple of reasons, I prefer to use port numbers to support virtual hosting rather than host headers (some SSL issues, primarily) so my understanding of host headers is not where it should be but here's what I know:

The host header doesn't have to be a pre-existing entity and you should be able to use any of the options you mentioned, but you do have to make sure your name resolution system knows what to do with it and that may be where you're running into trouble.

There is an article on TechNet that summarizes the procedure (Q190008) and I've found that it works best if you use the Internet Manager plug-in to the MMC console.

Hope this provides enough of a hint to get you started. If you need further information, if you usethe search term "virtual hosting", you'll probably get better stuff because "multi-homed" in the Microsoft world usually refers to a server that sits on more than one subnet.

paul

by zs6dgb

Open 'Internet Service Manager.
Highlight the site you have created, right click, and click properties. Under the WEB SITE Tab, next to the IP address ,you will see an advanced button. Click the advanced button, the highlight the ip address, click edit, and enter the 'Host Header Name'.
This is where you can assign either a port number [80] ip address, or host header.
(NB!! This is very different from the 'Custom HTTP Header' which you might want to remove if you added it by mistake.)
The DNS Server should first have an entry
(or host file).
You should be able to ping the name and get the ip address. You can have thousands of names on the same ip address.
EG if you ping www.davina.co.za you get 196.15.215.133 If you ping mail.davina.co.za
you also get 196.15.215.133 but if you go to the later in IE you would be directed to 196.15.215.133 :8383 .This is because mail...was set up on IIS to re-direct to another port{the home directory tab}because the webmail, mail and www is on the same server. Nifty Eh!
Also ensure that you have the correct 'default document'(Your first web page) installed under the "Documents" Tab.

All the best
David

by zs6dgb

The Host Header than is the site name.
EG. under Advanced......
For the site nicknamed WWW---Davina
196.15.215.133 80 www.davina.co.za

For the Site nicknamed MAIL---Davina
196.15.215.133 80 mail.davina.co.za

If you would like more info
mail me
myson@icon.co.za
david@webserve.co.za

by ds9

Thanks - I should have suspected that but did not. Works O.K. - I was using Oreilly's WebSite Pro before IIS4 and there, you use a unrelated Nickname for the local server tp find the site.
Thanks again.
George

This discussion is closed to new replies.