Locally, External IP Resolves to Router Admin

Solution 1:

When this problem is encountered on a router, the most common fix is to 'move' the router's admin port off 80 and onto something else so that NAT will then handle inbound requests properly, and port forwarding will take them to the designated device on the LAN. See whether your router allows you to change the admin interface port - for example, here's my Draytek:

Solution 2:

For example, let's say my laptop is set to 192.168.2.3, and my server is on 192.168.2.4, running Apache on port 80. If I go to my external IP (for example, 76.216.174.73), it takes me to 192.168.2.1 on port 80 (which is the router's admin page,) instead of 192.168.2.4 on port 80 (the Apache server.) If I visited my external IP (76.216.174.73) from the library, my router would connect me to 192.168.2.4 on port 80. I would like this to happen while I am at home, instead of just at the library, a cafe, or friend's house. Is that clear?

FINALLY, I understand the question, but unfortunately, there is no solution using most firewalls/routers, and doubtful there are any home models. The issue at hand is Network Address Translation, and there is a specific name for this problem, but I just can't remember right now: Basically, what it means, is that internally, you have to access resources by the internal IP address.