NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port Forwarding
I have two web page servers on my lan. Their IP addresses are reserved. I have port 80 forwarded to one and port 8080 forwarded to the other. I can access both pages on the Lan by enterin the lan IP ...
> Attached is what I have setup for port forwarding.
Ok. The obvious problem there is in rule 2: Internal Port 8080.
> 1. Yes. Both are listening on 80.
If the web server at "192.168.0.17" is listening at port 80, then
forwarding to port 8080 there won't work. What you should have would be
something like:
External Port Internal Port Internal IP Address
80 80 192.168.0.23
8080 80 192.168.0.17
The internal ports are both 80. because that's the port where each web
server is listening. The external ports can be (almost) anything you
wish. 80 is the default for HTTP (but you get to use it only once as an
_external_ port), and 8080 is a memorable alternate (which you'll need
to specify explicitly in a URL, like, say, "http://67.9.xx.xxx:8080").
> The router will not accept duplicate port numbers.
That datum might have some value if you revealed what you were trying
to do, and what happened then, which led you to that conclusion.
> When you do what, exactly? "cannot" is not a useful problem
> description. It does not say what you did. It does not say what
> happened when you did it. As usual, showing actual actions with their
> actual results (error messages, LED indicators, ...) can be more helpful
> than vague descriptions or interpretations.
Still my advice. Always my advice. It's good advice.
Attached is what I have setup for port forwarding.
My external IP address begins with 67.9
I have tried connecting with 67.9.xx.xxx:8080 and it fails to connect.
I thought that 8080 is an alternate port fo HTTP 80. I'm new at this.
The router will not accept duplicate port numbers.
> Attached is what I have setup for port forwarding.
Ok. The obvious problem there is in rule 2: Internal Port 8080.
> 1. Yes. Both are listening on 80.
If the web server at "192.168.0.17" is listening at port 80, then
forwarding to port 8080 there won't work. What you should have would be
something like:
External Port Internal Port Internal IP Address
80 80 192.168.0.23
8080 80 192.168.0.17
The internal ports are both 80. because that's the port where each web
server is listening. The external ports can be (almost) anything you
wish. 80 is the default for HTTP (but you get to use it only once as an
_external_ port), and 8080 is a memorable alternate (which you'll need
to specify explicitly in a URL, like, say, "http://67.9.xx.xxx:8080").
> The router will not accept duplicate port numbers.
That datum might have some value if you revealed what you were trying
to do, and what happened then, which led you to that conclusion.
> When you do what, exactly? "cannot" is not a useful problem
> description. It does not say what you did. It does not say what
> happened when you did it. As usual, showing actual actions with their
> actual results (error messages, LED indicators, ...) can be more helpful
> than vague descriptions or interpretations.
Still my advice. Always my advice. It's good advice.
Thanks for all the help. Using 8080 for the external port and 80 for the internal port solved the problem.