Comcast causes port forwarding to be unsuccessful

The solution to the problem is that most inexpensive routers do not permit connecting to an external forwarded port from an internal IP. This applies to multiple computers, so if an old server has a rule for port forwarding, HTTP server forwarding, or DMZ creation, it must be removed before external access is possible. Another option is to use the same IP address as the previous machine, and the reason for not doing this is not clear.


Question:

After successfully setting up
port forwarding
on my Router, I found that the Router’s IP on the Modem’s subnet is

10.0.0.2

. When I visit

10.0.0.2

, it forwards to my local server, which is located at

192.168.1.10

.

I activated
Port Forwarding
on port 80 of my modem and assigned it to

10.0.0.2

.

Despite being “open”, the
public IP
cannot be accessed.

Am I doing something wrong?

After forwarding the Modem’s IP to the Router’s IP, which are 10.0.0.1 and 10.0.0.2 respectively, the issue persists. It seems that my public IP address is not the same.


Solution:

Connecting from
internal IP
to an external
forwarded port
using home or inexpensive routers is typically not possible, as they do not support internal IP connections. This may result in it appearing as though the connection is not functioning when attempting to access it from within.

The type of NAT that was once referred to as hairpin NAT.

Request someone external to attempt to connect.

Frequently Asked Questions

Posted in Uncategorized