External Access to Apache on Windows Server 2003

I have apache installed on a Windows Server 2003 box. Intranet access
is working without a hitch. External access however will not work.

My network administrator has a Cisco Pix firewall configured with a
static list to handle IP translations. We have had no problems with
IIS which we are currently using on a couple of our sites.

I think that the problem is happening with the firewall. My network
admin believes that it is my virtual host configuration.

Why is the web site working internally then? I have 2 sites enabled -
"intranet2" and "www2".

What's going on here??

Any help will be greatly appreciated!

- Chad Brekke

"Chad Brekke" <ChadBrekke@gmail.com> schreef in bericht
news:1132013018.000540.241340@o13g2000cwo.googlegr oups.com...
> I have apache installed on a Windows Server 2003 box. Intranet access
> is working without a hitch. External access however will not work.
It does not work to what extend ...
.... no response, no page, wrong page???
Anything in the logs ??

> My network administrator has a Cisco Pix firewall configured with a
> static list to handle IP translations. We have had no problems with
> IIS which we are currently using on a couple of our sites.
Is Apache sharing the same public IP and port with those sites?

> I think that the problem is happening with the firewall. My network
> admin believes that it is my virtual host configuration.
> Why is the web site working internally then?
If the sites work well on the LAN it's probeably -cann't tell without
seeing- not your vhost setup. However, that does not instantly put the blame
on the firewall ...

> I have 2 sites enabled - "intranet2" and "www2".
Assuming name based virtuals, iow both sites share a single IP and port,
you HAVE to ALWAYS addres them by name -not IP-.
That implies, the sites must be known at public DNS -or listed in a hosts
file-

Just 2ct

HansH

Message: "The document contains no data."
No external IP's show in the access.log file

The Apache virtual sites are running on a seperate dedicated IP

VHOST Configuration
NameVirtualHost 172.31.1.102:80

<VirtualHost 172.31.1.102:80>
ServerAdmin webmaster@site1.com
DocumentRoot w:/site1.com
ServerName site1.com
ErrorLog logs/site1_error.log
</VirtualHost>

<VirtualHost 172.31.1.102:80>
ServerAdmin webmaster@site2.com
DocumentRoot w:/site2.com
ServerName site2.com
ErrorLog logs/site2_error.log
</VirtualHost>

We configure an on-site DNS. The sites have been added and configured
under the seperate and dedicated IP.

Hi Chad;

I recently set up Apache on a Windows NT4 box. My machine is behind a NAT
router (Netgear) and I had to use * instead of the actual IP address in the
vhost section(s), as in:

NameVirtualHost *:80

<VirtualHost *:80>
...
...
</VirtualHost>

You might try this.

Charles...



"Chad Brekke" <ChadBrekke@gmail.com> wrote in message
news:1132015827.117464.136670@g47g2000cwa.googlegr oups.com...
> Message: "The document contains no data."
> No external IP's show in the access.log file
>
> The Apache virtual sites are running on a seperate dedicated IP
>
> VHOST Configuration
> NameVirtualHost 172.31.1.102:80
>
> <VirtualHost 172.31.1.102:80>
> ServerAdmin webmaster@site1.com
> DocumentRoot w:/site1.com
> ServerName site1.com
> ErrorLog logs/site1_error.log
> </VirtualHost>
>
> <VirtualHost 172.31.1.102:80>
> ServerAdmin webmaster@site2.com
> DocumentRoot w:/site2.com
> ServerName site2.com
> ErrorLog logs/site2_error.log
> </VirtualHost>
>
> We configure an on-site DNS. The sites have been added and configured
> under the seperate and dedicated IP.
>

"Chad Brekke" <ChadBrekke@gmail.com> schreef in bericht
news:1132015827.117464.136670@g47g2000cwa.googlegr oups.com...
> Message: "The document contains no data."
> No external IP's show in the access.log file
Unsure whether logging is complete without any access_log being defined
below

> The Apache virtual sites are running on a seperate dedicated IP
Below shows shared IP ...

> VHOST Configuration
> NameVirtualHost 172.31.1.102:80
>
> <VirtualHost 172.31.1.102:80>
> ServerAdmin webmaster@site1.com
> DocumentRoot w:/site1.com
> ServerName site1.com
> ErrorLog logs/site1_error.log
> </VirtualHost>
>
> <VirtualHost 172.31.1.102:80>
> ServerAdmin webmaster@site2.com
> DocumentRoot w:/site2.com
> ServerName site2.com
> ErrorLog logs/site2_error.log
> </VirtualHost>
>
> We configure an on-site DNS.
Are the site names known in _public_ DNS?

What's the LANside IP of the Cisco router?

HansH

Unfortunately the *:80 did not work :(

- Chad

It looks as if the access log file is working OK. Seeing new entries.


Sorry - yes a shared IP.

I will have to talk with the network admin tomorrow about your other
questions regarding the DNS and router's LAN-side IP.

Thank you for your time.

- Chad

Update...

By using whatismyip.com I was able to find that the IP address listed
was different (last 3 digits) from the entry in our DNS. We changed
the DNS to translate from the new number. I am now able to
SLO-O-O-O-WLY pull in parts of the website externally - not sure why so
slow?? At this point it only works if I enter the IP address and not
the domain name.

There are 2 seperate IPs/Nics on this webserver.
Can this cause a problem when configuring an apache website??

- Chad