Re: Re: Multiple web instances assistance and comments -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

> From: "Steve McKay" <steve.mckay@southtrust.com>
> The HTTP server is attempting to bind to address
> 10.10.18.54 on port 80, but the TCP interface or port is
> currently not available.

I'm not familiar with the Apache configuration directives, but I believe the
Classic server uses the BindSpecific directive in conjunction with the
HostName directive to bind to a specific IP address.

Here's a quote from the HTTP Server Webmaster's Guide, for example:

"BindSpecific - Specify if the server binds to one or all IP addresses Use
this directive on a multi-networking system to run a different server
instance on each IP address or host name. All the servers may listen on the
same port.  If you specify On, the server binds to the IP address specified
in the HostName directive only, instead of binding to all local IP
addresses."

"If this directive has not been specified, the server binds to the HostName
specified in the CFGTCP command, options 12 and 13. If you change this
directive, you must stop the server and then start it again."

Nathan M. Andelin
www.relational-data.com

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.