1.

Solve : Site can't be accessed though the external ip?

Answer»

I got a computer, running a site. The computer connects to the router. The router have an external IP, and I port FORWARD the ports(80,8080,22) to my computer, and expect them to work with the external IP. I know my ISP blocked port 80, but the other 2 suppose to work.
But it doesn't.
other computer connect to mine using the internal IP, there is no problem.
I can use my computer ping the external ip, and I can access my router's configuration with the external ip.
but I can't use the external ip to access my computer even though I already did the port forwading.
Is this my router's problem or my computer's configuration? how to fix it?
I'm using linux. gOS based on Ubuntu.I suggest you let an external source scan the ports in order to detect whether the ports are being forwarded properly. Go to the site linked to below.
https://www.grc.com/x/ne.dll?bh0bkyd2
Press proceed to enter
Type in a port number in the text field and press Use specified custom probe.
If the probe reports your port as open it is forwarded correctly.
(In order for it to be open you need to have a program listening on the port and any firewall should be configured to allow the inbound traffic.)

Quote from: Mgccl on January 18, 2008, 08:22:28 AM

other computer connect to mine using the internal IP, there is no problem.
I can use my computer ping the external ip, and I can access my router's configuration with the external ip.
but I can't use the external ip to access my computer even though I already did the port forwading.
Is this my router's problem or my computer's configuration? how to fix it?
I'm using linux. gOS based on Ubuntu.

Other computers from your LAN? I mean after the router?
What router do you have?
To me it seems to be a security setting on the router, it does not allow you to connect back to your local area network through your external network connection from your local area network - it's a firewall setting, it does not allow such type of connections and YOU REALLY DON'T WANT TO DISABLE IT. The rule says: don't allow as input on the external interface any messages that SAY they are coming from your internal interface because this is NOT well-intentioned communication.
Please give me more informations: how many LANs are behind your router? Where is the server located?

Why do you think ISP blocked your 80 port?I did a check... the ports are open
I know the ISP block 80 because I read stuff about verizon on blogs.
the firewall allows all traffic

There are 5 computers at home, all connect to the router by WIRELESS. Server is one of them.

so is it anything to do with the route? because there was something similar happened:the computer can connect to the router but not outside, so I add the default route to my router and then my computer can access the outside.
now my route are like this
DestinationGatewayGenmask192.168.1.0*255.255.255.0link-local*255.255.0.0defaultdslrouter0.0.0.0This is the routing table on which computer? On the web server? It should work (I assume link-local is in fact "localhost" or 127.0.0.1).

Then from outside of your network you should be able to connect to your web server using the IP given to you by ISP or more simple, using a dynamic DNS service - free or paid. See www.dyndns.org and see if your router has the option to be a client, an "intermediary". Maintain the port forwarding to your web server (I assume that your web server has a static IP in your LAN).

Your router has a firewall, and there the rule that we talk about is activated. I am not sure that you can disable the firewall on the router (and I don't recommend you to do that).

If you want to access your web server from ANOTHER computer of your LAN, use the private IP of the server and not the public IP (of the router).



Discussion

No Comment Found