How to set router configuration properly?

Score

0

ijack April 5, 2011 at 12:41:58 Pacific

Silly question, but do you have a firewall on the machine hosting the web server (what OS is it running)? And, if so, does place any restrictions on port 80?

Score

0

forum user April 5, 2011 at 12:52:01 Pacific

Yes, is on Win 7. It was setted by me to allow apache to use TCP and UDP at any local port, remote port, users and computers (behind router and without router). I restarted and still nothing. How to resolve the problem?

Score

2

ijack April 5, 2011 at 13:41:38 Pacific

You might want to try turning your Windows firewall off completely, just for a minute, to check if that is the problem. It probably isn't, but it wouldn't hurt to try. I find that sometimes firewalls aren't doing quite what I think they should be doing.

Score

0

paulsep April 5, 2011 at 14:45:24 Pacific

Can you access the apache from another computer in your network, by using the servers local ip address 192.168.2.100 ? If yes, the problem is not local firewall at the server, but at the router. If you try to access the server from a machine inside your network to the public ip address of the router, it mostly will not work. Therefore, you should use the online port scanner, to make sure, that the port is shown as open. Click Here on HowTo ask good Question to get best Help Let us know, if the problem is solved !!!

Score

0

ijack April 5, 2011 at 23:56:50 Pacific

Not necessarily true. Firewall rules may be different for access from the local network and the Internet. The Windows 7 firewall certainly allows this. The best way to check whether it is the local firewall is to turn it off and see what happens.

Score

0

forum user April 6, 2011 at 04:04:56 Pacific

I turned the firewall off and now is working. The purpose of the router was to switch from one computer with linux server(24h/day) to two computers, one linux(12h/day), second win 7(12h/day). I now have to try the second os and if i have problems i will post. Thanks.

Score

0

ijack April 6, 2011 at 05:15:42 Pacific

That's good. Now that you have established that it was the firewall you can configure the firewall to let port 80 trhough. Have a look in "Advanced Settings" and see if you can see the rules pertaining to port 80, http, or IIS. There must be something there that allows port 80 on the local network but not the Internet. All you need to do is to modify this rule to apply to all connections, or create a new one that does so. On the other hand, as you are already running a firewall on your router you may consider it unnecessary to also run one on the server.

Score

0

forum user April 6, 2011 at 13:47:58 Pacific

yes, is working also with the firewall on. i put a rule to allow 80 at "inbound" and i think thats enaugh. i also deactivate "virtual server" and let only TCP at the router conf at port forwarding.