Link to home
Start Free TrialLog in
Avatar of it-kourt
it-kourtFlag for United States of America

asked on

Help configuring Apache Web Server behind a firewall.

I have a new website/server running Windows 2003 Server, Apache 2.2.9, PHP 5.2.6, MYSQL 5.0.67 and WordPress 2.6.2.

It is running fine for internal users (private network) but the connection times out on the public network (external users).  

I have correctly set the internal and external A records correctly.  And I have port 80 forwarded to the ip address of the webserver.

When I run a trace I can see a request come in to the webserver but nothing goes out from the server.  It is like the request dies at the webserver.

Thanks in advance - Dave
Avatar of thebradnetwork
thebradnetwork
Flag of United States of America image

So if you run the internal IP in the browser it works but what happens if you run the external address ( go to www.ipchicken.com to find it )
If running the external IP works then its something to do with your DNS and if its doesn't work and times out we know its something on your web server.
Avatar of it-kourt

ASKER

I actually have 10 external IP addresses.  I have our external dsn set to forward:
www.siteA.com to xxx.xxx.xxx.aaa
www.siteB.com to xxx.xxx.xxx.bbb
I used www.network-tools.com to check the A records and they are correct.

www.siteA.com is forwarded with our Watchguard 750e firewall with http filter to internal IP of our IIS webserver.
www.siteB.com is forwarded with our Watchguard 750e firewall with http filter to internal IP of our Apache webserver.

I can browse www.siteA.com from the public network as well as our internal network.
I can browse www.siteB.com from our internal network but not the public network.  For some reason the incoming http packets are reaching the Apache webserver but do not get a response packet from the Apache webserver.
Ok with site A your problem is with the DNS. Reason why i say that is you know that the server is running because you can access the side via an internal address. Also you know that it doesnt have anything to do with your firewall because its showing up on external address.

With side B you know its not the web server because it works from an internal address but you could have a problem with your firewall.

I would either DMZ or disable the firewall to those internal address just for testing purposes. Once you have ruled out the firewall move on the the DNS. It doesn't should like its a problem with your web server but the problems inlay somewhere else. If the web site pulls everytime from the internal address then your server is working fine.
ASKER CERTIFIED SOLUTION
Avatar of it-kourt
it-kourt
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial