WebSphere HTTP Server - IBM HTTP & MS IIS on one system?

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere HTTP Server > July 2004 > IBM HTTP & MS IIS on one system?





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author IBM HTTP & MS IIS on one system?
Michael Yashin

2004-06-23, 5:48 pm

Hi,

I have system with 2 IPs.

Need the following configuration:
IP1:80 - IBM HTTP
IP2:80 - MS IIS

If IIS starts first all is OK. If IBM HTTP starts first, IIS fails
telling "Address is already in use". Because IBM HTTP is smaller it
starts faster (therefore first). Setting dependencies between
services is not a good idea...

Config for IBM HTTP:
Port 80
BindAddress xx.xx.xx.xx (IP1 here)

Is there any solution?


PS. Win2000, IBM HTTP 1.3.26, MS IIS 5
Sunit Patke

2004-06-23, 5:48 pm

There are multiple places in a configuration file (httpd.conf) where you can
bind to an IP address and not all directives have verb bind in it. Look for
VirtualHost definitions etc.

Sunit

"Michael Yashin" <yashin@reksoft.ru> wrote in message
news:4cf458ad.0406230043.3de88f42@posting.google.com...
> Hi,
>
> I have system with 2 IPs.
>
> Need the following configuration:
> IP1:80 - IBM HTTP
> IP2:80 - MS IIS
>
> If IIS starts first all is OK. If IBM HTTP starts first, IIS fails
> telling "Address is already in use". Because IBM HTTP is smaller it
> starts faster (therefore first). Setting dependencies between
> services is not a good idea...
>
> Config for IBM HTTP:
> Port 80
> BindAddress xx.xx.xx.xx (IP1 here)
>
> Is there any solution?
>
>
> PS. Win2000, IBM HTTP 1.3.26, MS IIS 5



Aaron W Morris

2004-06-26, 9:54 am

Michael Yashin wrote:
> Hi,
>
> I have system with 2 IPs.
>
> Need the following configuration:
> IP1:80 - IBM HTTP
> IP2:80 - MS IIS
>
> If IIS starts first all is OK. If IBM HTTP starts first, IIS fails
> telling "Address is already in use". Because IBM HTTP is smaller it
> starts faster (therefore first). Setting dependencies between
> services is not a good idea...
>
> Config for IBM HTTP:
> Port 80
> BindAddress xx.xx.xx.xx (IP1 here)
>
> Is there any solution?
>
>
> PS. Win2000, IBM HTTP 1.3.26, MS IIS 5


Instead of using Port and BindAddress directives, I would recommend a
more straightforward Listen directive:

Listen xx.xx.xx.xx:80

--
Aaron W Morris <aaronmorris@mindspring.com> (decep)

Gene

2004-07-28, 3:04 am

And configure IIS to listen IP2 only:

Web Site properties:

IP Address: IP2 (default is "all not assigned", then IIS is listening all IP
Adress).

Gene

"Aaron W Morris" <aaronmorris@mindspring.com> escribió en el mensaje
news:cbg3tj$4loc$1@news.boulder.ibm.com...
> Michael Yashin wrote:
>
> Instead of using Port and BindAddress directives, I would recommend a
> more straightforward Listen directive:
>
> Listen xx.xx.xx.xx:80
>
> --
> Aaron W Morris <aaronmorris@mindspring.com> (decep)
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com