Apache behind WAG320N not working on remote networks- HELP!

[SupaMonkey]

Ok, so Im having a really tough time here at a client.

ADSL Router: Linksys WAG320N
ADSL Firewall: Off
"Block Anonymous Internet Requests" : Off
Port Forwarding for TCP:80 => Server IP : Done

If I access http://internet-ip from anywhere on the network, the apache page shows up.
If I access the above from any other network, "The connection has timed out" : fail.

Ive disabled everything from windows firewalls, to "allow from all" on apache and what not. still nada.

This is a new server with a new adsl router.
Previous server with Netgear router - worked 100z.

 

[zamicro]

I had similiar issues, when I moved a server behind a new firewall. In my case, the server was creating it's own pppoe connection. After moving it behind the router/firewall, I wanted to keep the own connection going until everything was sorted. I failed to get it to accept outside traffic. After disabling the pppoe connection and rebooting the server, it worked 100%. I am still thinking what exactly was the problem, so that there will not be a need for a reboor the next time. I wasted a lot of time thinking the port forwarding was not working correctly.

 

[Anthro]

Have you checked that Apache itself allows from remote IP addresses ?

 

[syntax]

first, check logs of the router and see that it is indeed port forwarding properly. (also make sure you are forwarding the correct port, remember it must be a destination port that needs to be forwarded...simple i know, but i gotta ask )
Double check the apache server has the right default gateway
dump on the apache servers interface or check logs to see if it is receiving the http request from external sources
The dump will also tell you if the server is replying, and replying correctly

 

[SupaMonkey]

Remote Desktop -> Forwarding to server correctly
Ventrilo Server -> Forwarding to server correctly
Apache -> Fail

Checking Apache logs, theyre clean as a whistle. Deleted the logs and restarted the server to double check - and nada.

Changed Apache port to 8012 and made the relevant port forwards on the router and BAM! It works.
Phoned MWEB (std. Uncapped) and they said it wasnt being blocked by them.

 

[SupaMonkey]

PS: Wouldnt want to tell my clients to access port 8012 - its hard enough sometimes explaining what a web browser is - and a url without "www", nevermind a url with colons and numbers at the end So would be great if someone out there could help me out in getting this to work with std port 80.

 

[zamicro]

Have a look at your MWeb control panel

Select ADSL on the left.

On the right hand there is a section called ADSL Protected Access

Disable it.

Try and access your server now on port 80.

 

[SupaMonkey]

Spot on - someone else suggested this in another thread - worked like a charm. Pity the mweb tech couldn't of told me this when I phoned in asking if they block port 80
Thanks though zamicro

 

[zamicro]

Spot on - someone else suggested this in another thread - worked like a charm. Pity the mweb tech couldn't of told me this when I phoned in asking if they block port 80
Thanks though zamicro

I know, because I went through the same headache.

I also phoned tech support and asked about blocking of port 80, and the tech also had no idea. Luckily someone else helped me on MyBB as well.