- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Port Forwarding
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 address and path to the pages. I can access the web page being forwaded thru port 80 but I cannot access the page on 8080. I cannot telnet to 8080. If i change the page on 8080 to 80 I can access it with no problem. How can I access both pages from the internet?
What am I missing here?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> 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.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
The port 8080/TCP might be in use already, ie. in ReadySHARE or by UPnP PMP by a UPnP client on your LAN (a NAS, computer, ...) - check the related areas on the router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
> I have two web page servers on my lan. Their IP addresses are
> reserved.
So, two different systems, with different LAN IP addresses? And
those reserved LAN IP addresses are...? Are both web servers listening
on (LAN) port 80?
> [...] I have port 80 forwarded to one and port 8080 forwarded to the
> other. [...]
That's not a useful/complete description of port-forwarding rules.
Copy+paste the actual port-forwarding rules.
> [...] I can access both pages on the Lan by enterin the lan IP address
> and path to the pages. [...]
Copy+paste the actual URLs which you are using.
> [...] I can access the web page being forwaded thru port 80 [...]
Are you now talking about access from the outside world? "access"
how, exactly?
> [...] but I cannot access the page on 8080.
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.
What are the actual URLs which you are using (from where)? Hide your
public IP address if you want, but otherwise, copy+paste is your friend.
> [...] I cannot telnet to 8080. [...]
"cannot"? See above.
> [...] If i change the page on 8080 to 80 I can access it with no
> problem. [...]
I don't know what any of that means.
> [...] How can I access both pages from the internet? [...]
Appropriate port forwarding (and web server configuration).
> What am I missing here?
I can't tell without a clear description of what you're doing, and
what happens when you do it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
> 1. Yes. Both are listening on 80.
Ok. That sounds normal.
> 2. Lan addresses are 192.168.0.17 to 8080 and 192.168.0.23 to 80. Both
> are reserved addresses. See attachment 1
Addresses are addresses; ports are ports. What does "to 8080" mean
to you? (I trust that you've noticed that only one attachment is
allowed per posting.)
> 3. When I just enter the Lan ip address, I can access the page. See
> attachment 2
"enter the Lan ip address" in a web browser's address window? And
that works for both "http://192.168.0.17" and "http://192.168.0.23"?
> 4. Yes. I'm trying to access the page from the outside world. [...]
Have you tried it from within the LAN using the external IP address?
What are the first two octets ("a.b" out of "a.b.c.d") in your public
IP address? Is that what the R6900 says is its WAN/Internet IP address
(ADVANCED > ADVANCED Home : Internet Port : Internet IP Address)?
> Copy+paste the actual port-forwarding rules.
Still waiting for that.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
For pure http or https (Web) you need just tcp (no udp).
The one with the port 8080 is named Arlo http - to my knowledge Arlo does not have any local Web based access. Is there a system listening on port 8080/TCP on that LAN IP (different from an Arlo?)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> 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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port Forwarding
Thanks for all the help. Using 8080 for the external port and 80 for the internal port solved the problem.
User | Count |
---|---|
4 | |
3 | |
1 | |
1 | |
1 |
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more