Windows

General discussion

Locked

IIS5 Answering on Multple NICs

By Joseph Moore ·
Machine: Win2KServer, SP3, with all recent patches, running on IBM Netfinity 5000.

IIS is installed and running (only FTP and WWW installed and configured). FTP is fine. WWW is the problem

The server has 2 NICs in it, both with different IP addresses (for the sake of argument, let's say NIC#1 is 10.0.0.1 and NIC#2 is 10.0.0.2).
IIS WWW is "bound" to 10.0.0.1, port 80 only. For a screen snapshot of this window, go here:
http://www.horrorseek.com/horror/leeringclown/techrepublic/iis1.gif
(please remove any spaces)
(Yes, agan that is not the correct internal IP address; I am using a valid 10.x.x.x address)
The Advanced button reveals the same info. Go here for another screen snapshot:
http://www.horrorseek.com/horror/leeringclown/techrepublic/iis2.gif
(again, remove any spaces)

The problem is that IIS is answering all WWW requests on port 80 for BOTH IP addresses, not just the single one it is configured to use. I have verified this by using SamSpade and NetBrute, 2 tools that can expose the web server packet info. Both tools give me this info back from both IP addresses:

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Content-Location: http://10.254.253.230/Default.htm
Date: Mon, 07 Oct 2002 21:39:10 GMT
Content-Type: text/html

As you can see, IIS answered. Now, I need to have IIS stop answering on the 2nd NIC (10.0.0.2) for port 80, so I can install Lotus Domino and have IT answer on NIC2 port 80. But, we are not there yet.

Also, when you use a web browser to go to http://10.0.0.1 you get the default home page on my web site, as I would expect. On http://10.0.0.2 you get a message reading "No web site is configured at this address."

I have gone into the Properties for the IIS server itself, and Edited the Master Properties. You cannot set the IP address there. I thought you could, but guess not.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

Ok, an update. Lotus Domino 5.0.8 is on the box now. To make things easy, we set up the Domino HTTP Server to work on port 81, and in doing that, our 2-engine web site is working flawlessly!
Yep. IIS on port 80 is dishing out its web pages, and theframes supplied by the Domino web content are also working, with that data coming on port 81.
Now, we have (2 years ago) been able to get Domino to only answer on 1 IP address on a multi-homed server, so we can do that again! Tomorrow (hopefully) we will get this to work. The idea:
Get Domino HTTP server to ONLY answer on the 2nd IP, port 80. In doing this, IIS is completely DISABLED.
Once Domino is up, we will then start IIS. IIS will find the 1st IP address port 80 open, and will answer onthat one; but IIS will find the 2nd IP address port 80 already taken by Domino.
It is our hope that in trying things like this that when IIS comes up and finds that the 2nd IP address is already taken, that it will not crash Domino!
IF in doing this, IIS works on 1st IP port 80, and Domino works on 2nd IP port 80, then we will have the config we are looking for!
Friday will be an interesting day!

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

Update for Friday:
Well, there is no update! We are trying to contact a Domino consultant, to get Domino to only listen on the 2nd IP port 80.
So, onto the next week.

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

Couple of comments. First, no work done today, since it is Columbus Day.
Next for DR - Yes, I know about specifying the port address in the HTTP address line. Currently, with Domino running on this server, it is set to answer HTTP requests on port 81, and IIS handles port 80. So, yes, you can go to HTTP://10.0.0.1:81 and you get the Domino default home page; go to HTTP://10.1.1.1:80 gives you the home page of my web site presented by IIS.
The whole port 80-81 issue is really NOT the issue. Itwas a fast way to get IIS and Domino both answering HTTP requests, so we could test if even running IIS and Domino on the same machine would be possible! It does work this way, but there are problems. I cannot leave Domino on port 81, due to firewall ruleset restrictions. (I had a test user who could not connect outbound to port 81, so they could not see any Domino-delivered content.).
This is why 1 NICs and 2 IP addresses, so IIS can have 1 IP at port 80, and Domino the other IP at port 80. No firewall problems, and all HTTP traffic running out on the standard port.
LordInfidel - I know, trying to run IIS and Domino on the same machine was NOT my idea!!! I am just the guy stuck with this configuration who has to get it running! If it were up to me, Domino would be on 2 machines. Now, we do have Domino configured to also support IIS (there is a setting in the Domino server document that states that IIS is also running on the server). I am just waiting for my Domino consultant to come to the office and set up Domino to only run on the 2nd IP address. This CAN be done; we have a single server in house with 2 NICs, 2 IP addresses, and 2 running installs of Domino, each Domino serving up a separate web site.
So, we will set up Domino like this, to only work on the 2nd IP, and then it is my HOPE that IIS will then only be able to work on the 1st IP address port 80!

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

This is gonna take a few days to resolve itself.
I will keep this up-to-date on developments.

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

Point value changed by question poster.

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

Stupid Socket Polling!
That was the answer.
All hail LordInfidel, who found the solution.
Yes, the writeup on Technet article Q238131 did solve my problem. The VB script quoted on the article did make the necessary changes to IIS so that IIS would only work on the IP address you have it configured to work with. Please see LordInfidel's post on this Technet article for the text.
Ok. So now, IIS is only running on the 1st IP address. I will (hopefully) get my Domino consultant in the office in the next day or two to set up Domino to only work on the 2nd IP address.
In doing that, both web engines will be working in tandem, on their own port 80, on their own IP address, on the same server, delivering a unified web site.
I am going to close this question later tonight.
Thank you to all who helped out.
Joe Moore

Collapse -

IIS5 Answering on Multple NICs

by Joseph Moore In reply to IIS5 Answering on Multple ...

This question was closed by the author

Related Discussions

Related Forums