cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
303
Views
0
Helpful
4
Replies

Need help on nating for internal user can access web server from public ip address

Rajesh Kamble
Level 1
Level 1

Hi,

Need help on nating for internal user can access web server from public ip address 

4 Replies 4

Mark Malone
VIP Alumni
VIP Alumni

Hi

A static NAT just for that user will do , without any info all I can give you is the doc the information is in this how exactly to do it

http://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/13773-2.html#configs

thanks for your reply ...

i give the configuration of my router

interface FastEthernet0/0
 ip address 172.16.100.2 255.255.255.0
 ip nat inside
 ip virtual-reassembly in
 duplex auto
 speed auto
 service-policy input block
!
interface FastEthernet0/1
 bandwidth 15360
 ip address 115.113.163.1 255.255.255.252
 ip flow ingress
 ip nat outside
 ip virtual-reassembly in
 duplex full
 speed 100
 crypto map MUPUVPN
 service-policy output VOICEQoS

ip nat inside source route-map NONAT interface FastEthernet0/1 overload
ip nat inside source static 172.16.100.8 115.113.141.145

Hi, I have internal web server with IP Address 172.16.100.8 which is natted with public ip 115.113.141.145 My requirement is that I should able to access the web server internally (on local LAN) with public ip 115.113.141.145 I checked this on Cisco and I am able to find out the following We normally define ip nat inside on local interface and ip nat outside on outside interface. INSTEAD OF THIS WE SHOULD USE ip nat enable on both interfaces to enable this. My current NAT Statement is as follows Ip nat inside source static 172.16.100.8 115.113.141.145 WHICH NEEDS TO BE CHANGED AS Ip nat source static 172.16.100.8 115.113.141.145 Let me know is this a correct way of doing this and if yes then what are the implications of this.

Hello Ravindra,

>> 

My requirement is that I should able to access the web server internally (on local LAN) with public ip 115.113.141.145

Gius> No, this should not be supported internal users should use the private ip address to access the web server. I have seen a few threads about the same issue and most of them end up with this result.
NAT action is triggered when from a NAT inside interface the traffic flow goes to a NAT outside interface.
You are asking to the router to go through NAT and then to send back the traffic to the LAN internal interface.

Hope to help
Giuseppe

any suggestion on this.....  

Review Cisco Networking for a $25 gift card