configuration trouble in apache 2.0.49 ...

I'm having trouble getting my desired configuration
to work correctly under Apache 2.0, although it
seemed to work fine in Apache 1.3, and I'm
using the configuration directives the documentation
on the Apache website tells me I should be using
for Apache 2.0 (or I'm pretty sure I'm doing so :-)

My machine uses a static IP address allocated to
me by my ISP (let's call it "1.2.3.4"), and I need the
machine to serve content from its "ServerRoot"'s
"htdocs1" subdirectory when requests are made to it
addressed to "www.domain1.com", and from the
"htdocs2" subdirectory to serve requests addressed
to it as "www.domain2.com"

I;I'm using the following list of directives as to set
up this configuration:

> Listen 80
>
>NameVirtualHost 1.2.3.4
>
><VirtualHost 1.2.3.4>
> ServerName www.domain1.com
> DocumentRoot "C:/Program Files/Apache Group/apache2/htdocs1"
> </VirtualHost>
>
> <VirtualHost 1.2.3.4>
> ServerName www.domain2.com
> DocumentRoot "C:/Program Files/Apache Group/apache2/htdocs2"
> </VirtualHost>

here, as con be seen, my "ServerRoot is "C:/Program Files/Apache
Group/apache2"



Trouble is, I get the following errors (when I try to start the server):

1) "NameVirtualHost *:0 has no VirtualHosts"
2) "Only one usage of each socket address (protocol/network address/port) is
normally permitted"
3) "make_sock: could not bind to address 0.0.0.0:80"

the last two errors seem to be related to the server trying to
respond to requests by allocating a socket which is in use
or otherwise unavailable, but I don't know the cause of
the first error, since I'm sure my "<VirtualHost>" directive
is spelt correctly, and my NameVirtualHost directive doesn't
use the a "*" argument in this case

So where am I going wrong?

Thanks,
Russell

I hope someone answers this, I too have a similar problem.

On 14 Jan 2005, "s" <sabrenael@netscape.net> wrote in
news:1105711181.495256.309270@z14g2000cwz.googlegr oups.com:

> I hope someone answers this, I too have a similar problem.

But would you acknowledge them for taking the time to help you?

Yes, I have before.

> Yes, I have before.

Well, it's all very nice to see this discussion on
whether people acknowledge the help of others,
but, in the meantime, I'd really love to set a
meaningful solution to this problem from
someone, since it's doing quite some damage to my
organisation not having a working website ...

I've managed to get rid of the restart errors but,
despite this, I still get a "404 File not found" error
when I try to access the website. Neither the
"Event Viewer" nor the error logs give any
error messages, which makes me wonder:

How do I, in this case, track down the name
of the file not being found?

Thanks,
Russell

I faced that problem also. But in my case, I was running IIS server
when I tried to set up apache server. That's why 3) "make_sock: could
not bind to address 0.0.0.0:80" error message occurred. When I stopped
IIS, apache worked well. Maybe my problem and your problem were not the
same. But this is just my suggestion.