03-16-2006 08:44 PM - edited 03-05-2019 11:48 AM
Hi all,
I am using a 2611 Router with IOS 12.2.
Currently, I have my router configured to portforward Inside_Local:80 to Inside_Global:8080.
The command I used is [ip nat inside source static tcp 10.0.0.200 80 int e0/0 8080]
This works fine, and people can access my webserver from the outside.
However, I myself am unable to access my webserver from Inside_Global:8080, as my browser is unable to connect to it. It works fine with Inside_Local:80 though.
Can someone please enlighten me on how I can resolve this issue?
Thanks in advance.
Solved! Go to Solution.
03-16-2006 08:54 PM
Hi,
What you are describing is not quite possible because of the manner in which NAT operates. The only way to access your web-server from your inside network is by using it's inside local address.
If you wish to access your web-site using its public address, you can only do that from outside your network.
Hope that helps - pls rate the post if it does.
Paresh
03-16-2006 08:54 PM
Hi,
What you are describing is not quite possible because of the manner in which NAT operates. The only way to access your web-server from your inside network is by using it's inside local address.
If you wish to access your web-site using its public address, you can only do that from outside your network.
Hope that helps - pls rate the post if it does.
Paresh
03-16-2006 09:01 PM
Ah.. I was afraid that would be the case.
I suppose there isn't much I can do about it then.
But of course, thanks alot!..
11-04-2006 09:11 AM
Hi,
I am having the same problem with a 1841 cisco router. So far I was using a pretty cheap low end router provieded by my ISP and that problem never occured. I could access my inside hosts with their official address.
Any ideas?
Regards,
Oliver
11-04-2006 10:13 AM
You can get around this by using one of two methods, depending on thenumber of clients affected.
If you set your internal DNS to the *inside* address of the server, then you can reference the server by name internally as well as the outside (assuming the external DNS points to your NAT'd address).
Also make sure that the DHCP server is passing out the internal DNS server address as primary ... or that your static IP assignments are such that the internal DNS is primary).
For a few clients, you can edit the "hosts" file; put the internal name and address of the server in each client's "hosts" file (on XP it's in C:\Windows\System32\drivers\etc ).
If your system is a laptop, and it'll also be trying to access from the outside, then this methos will screw up access from outside you network.
The Internal DNS method will work internally and externally, since the name is the same (assuming that the DNS primary is now pointing to an external DNS, like from your ISP).
Good Luck
Scott
11-11-2006 09:26 AM
Hi all,
I will enter the URL http://127.0.0.1:80 into the web browser on your web server.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide