Mulitple Web Sites (IIS and Apache) and SSL

Discussion in 'Windows Networking' started by tshad, Jan 16, 2007.

  1. tshad

    tshad Guest

    We have multiple Websites on one server (IIS) and one appache (tomcat) also
    on the same server.

    This has worked fine until now. We need secure pages on all the Websites.
    We can handle the multiple Websites on IIS by adding a different address on
    the NIC card and adding one of the address to each Web Site. Then all the
    Websites can share port 443.

    But can we do the same with Apache? Can we have the Apache sharing 443 on
    the same Web Server as IIS? I assume you can't as you can only have one
    application listening on each port. If there is a way around this without
    having to buy another server we would be thrilled.


    tshad, Jan 16, 2007
    1. Advertisements

  2. Andrei Ungureanu [MVP], Jan 16, 2007
    1. Advertisements

  3. tshad

    tshad Guest

    That was the confusion we were running into.

    I had thought that only one application (service) on a machine can listen on
    one port (having nothing to do with the IP). I know that an IP and Port
    Number constitute a socket.

    But if you could have more than one application listening on a port, does
    that mean that if I have SMTP running on a machine I could add another IP
    address to my NIC and have my application listen on Port 25 (what SMTP uses)
    but on the other IP Address.

    Also, I didn't know you could hook Apache to a different IP Address.


    tshad, Jan 16, 2007
  4. Ok, so let's say it in a different way: "only one application on a machine
    can listen on one SOCKET". So, different IP address, same port number =>
    different socket. I haven't worked with Apache but I doubt that it can't be
    configured to listen on another ip address.

    Andrei Ungureanu
    Test our new EventReader!
    Andrei Ungureanu [MVP], Jan 20, 2007
  5. tshad

    tshad Guest

    No, your right. Only one application can listen on one Socket (IP:port).
    The problem was that IIS grabs all the addresses so it looked like when it
    was listening on one address the application would listen to all. This is
    the case but not because ports are Application dependant, as I thought.

    Apache will do the same thing. If you don't define a particular Address, it
    will listen on all address on the machine. This would conflict with IIS
    which would grab all the addresses. This is solved by using httpcfg to
    exclude the address you want to have Apache listen to.

    The problem is that it doesn't work completely as documented but close.


    tshad, Jan 22, 2007
  6. Andrei Ungureanu [MVP], Jan 29, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.