Topic: Need to run a site on IIS and another on Apache

[BeefEater]

Hi There,

First of all I'd like to thank everyone for any help or suggestions they can provide to my current dilema.

I currently have our company website hosted on a 64-bit server 2008 machine running Apache 2.2.x (latest release i think). The website was coded in PHP and the developer has said that it needs to run in apache for the code to work properly. I have successfully implemented it and it's working great, however I have another website for some software the company has purchased that will act as an SSL webdav or ftp (simply speaking) site. The software developer has informed me that their site is only supported in IIS. This has thrown a huge monkey wrench into my plans as I was counting on using virtual hosts with Apache to have the server know which site to display.

Since I am unable to host the additional site with apache, but need to host our company site with it, I would like to know if it's possible to somehow configure apache to still use virtual hosts and redirect requests for the additional SSL site to the IIS page? The additional site will require access on port 80 and 443. I would like to continue to use one IP address for the web server as I think it's a simpler solution, but can configure the server as multi-homed if necessary. I'm just hoping there's a way to implement something close to what I had originally planned.

Again, thanks for any help or suggestions. I'm hoping to have a solution worked out in the next week or two before I begin deploying the software we have purchased.

BeefEater

[glsmith]

Use a different port for the one that doesn't need 80 & 443.
Unless you have a router that supports more than one wan IP (to forward requests to proper internal ip), pretty much the only way to do it.

[BeefEater]

Thanks for the reply.

Looks like there's no way to do what I was hoping to. I guess I'll have to configure the server as a multi-homed web server.

Just looking for confirmation of something if someone could post a reply one way or the other.

Will configuring the 2nd NIC in my webserver to be on the same subnet as the first NIC work? I've had issues with this configuration on other systems and suspect no, but a second opinion would be nice.

I currently have the first NIC on my router's DMZ subnet and would like to put the second one on there as well, but think this might be an issue so I may just make another subnet for the 2nd NIC.

Again, thanks for the help.

Regards,

BeefEater

[glsmith]

The bigger question is, how does the router know which request on port 80 goes to which internal IP?

Does IIS have to be on 80? Can it be run entirely on 443?

www.siteA:443 -> IIS
www.siteA:80 -> Apache -- redirect --> www.siteA:443
www.siteB:80 -> Apache

is an option.

Running Apache also as a reverse proxy with IIS on another port is an option, this keeps siteA on 80 even though IIS is running on say 81. But configuration can be difficult.

www.siteA:443 -> IIS
www.siteA:80 -> Apache <-- proxy --> IIS:81
www.siteB:80 -> Apache

[BeefEater]

well, to answer your question, I suppose I would have the DNS Records for our company website go to one wan IP, which would then be forwarded to the webserver on the DMZ, then the additional website running on port 80 and 443 (i am fairly certain it requires both) could be on another WAN IP and be forwarded to the 2nd NIC on the webserver, likely on a different subnet. I have 3 wan IPs available at the moment ( i would like to drop one if I can, but I want to wait to be sure I don't need it) Our router is a sonicwall appliance that is quite flexible in its port configurations.

I like your reverse proxy idea but am not really an expert on setting up or hosting websites. Got apache running in a couple days with no prior experience, but I think my config is fairly simple and trying to work out this proxy idea might be over my head. Perhaps if you could point me to a tutorial or some documentation about it, that would give me something to work from. I think I will see what I can dig up on my own as well as it does sound promising. So long as Apache, while acting as a reverse proxy, can read the host header and know what website is being requested, I think it would work.

Thanks for the suggestions, maybe not all hope is lost.

Regards,

BeefEater

[glsmith]

Probably a good start would be here
http://www.apachetutor.org/admin/reverseproxies

[BeefEater]

Thanks for the link. It's an interesting read and I will have to spend time with it in front of me while I'm working on the web server to get it working.

Looks like I have a weekend project...

Thanks for the help