Cisco Router - Website Doesn't Work Locally Because Public IP Directs to Router Itself!

[s_valmont]

I have an RV220W but this issue may apply to other Cisco routers.

My website is deployed at public IP address 123.45.67.89/MyWebsite/Default.htm. My web server has an internal IP to which port forwarding directs HTTP requests.

Problem is, whenever I'm on the local network, typing in the above address gives me a 404 error. The reason being 123.45.67.89 is interpreted as the router itself! And not the web server that's supposed to receive the browser request.

Using any external network to access the website is fine. Using the internal IP of the web server when on this router's network also works (e.g., 192.168.0.123/MyWebsite/Default.htm).

But, despite Cisco support saying it's impossible, surely there's a way to stop the router from doing this?

[Riju Kalarickal]

When sitting  on the inside LAN segment, you cannot access the internal server using  its Public NATted ip. This is a NAT limitation with routers.

You will have to use the private ip to access that server.

There are workarounds if you are using dns name to access the server instead of IP - https://supportforums.cisco.com/docs/DOC-8936

-Riju

[cal_nguyen]

Riju, any ideas why a consumer-grade D-Link router I use, the DGL-4300, doesn't have this problem?  When you enter the public IP of a locally hosted website, it simply delivers the website.

[Ty Melrose]

Calvin, I had the same issue trying to get smart phoines to connect to our exchange server locally.  The issue is called hairpinning (I never heard the term until I had this router) and Cisco has a beta firmware to correct the issue.  You'll need to contact Cisco to get the beta firmware and instructions to create a special rule. 

BTW, if you are using the ProtectLink web filtering, make sure it's active and working BEFORE you install the beta firmware.  I didn't and am still having an issue with getting it active after a month.