Domino and IIS -- same box, different IP's?

I currently have a situation with a customer and their ISP that I’m concerned about…

I have one machine that is currently running IIS (.NET application) and I also want to run Domino (web apps) on it. The .NET app has nothing to do w/ the Domino apps, but I only have one machine. I have heard that you can assign a separate IP address to the Domino server than the IIS server and they can run simultaneously on the same box – is this true? If so, would I still need to install the Websphere plugin?

Thanks in advance for any feedback…feel free to tell me if this is a really horrible idea and will cause all sorts of problems :slight_smile:

Subject: Domino and IIS – same box, different IP’s?

Hi Jennifer,

I’m working for a client now that has IIS and Domino on the same server. We’re using the Websphere plugin though, since we wanted to integrate them together. If both are on the same box, I believe you will still need to change Domino to use a different port number than 80 (even with another ip address). I maybe wrong on this, but I believe that since both are running on the same OS, only one can have exclusive rights to Port 80. If you change Domino from port 80 and use the Websphere plugin, you can have IIS redirect urls with .nsf to Domino. This would take care of any issues requiring having to put the new port number in the URL. The question you need to answer is:

How much traffic will Domino generate? Domino is very resource intensive for http tasks. If your IIS server is already receiving a lot of hits, then it may not be a good idea for 2 heavily used sites using 2 different web servers to be on the same box. HTH

Subject: Domino and IIS – same box, different IP’s?

I realize that I am more of an IIS Admin than a Domino Admin…because I know that through the MMC on your IIS server, you can configure IIS to use alternate IP addresses. You could probably start here…if you have the IIS Resource Kit that would be better, but the link below should put you in the area of a solution:

http://www.microsoft.com/technet/archive/winntas/support/sur_tcp2.mspx