Internal hosts cannot access the outside network because NAT does not translate


Jun 18, 2009 3:51 PM
Jun 18th, 2009

Core Issue

The most common reason for this problem is a misconfiguration of the Network Address Translation (NAT), such as not having the ip nat inside and ip nat outside commands on the appropriate interfaces. Another possible reason is that there is no Access Control List (ACL) configured for NAT specifying which hosts are permitted to use NAT.


Ensure that the ip nat inside and ip nat outside commands are assigned to the correct interfaces. Check the ACL configured for NAT and make sure the inverse mask is correct.

For more information, refer to Verifying NAT Operation and Basic NAT Troubleshooting.

Another situation in which NAT would not work is if IP Routing is disabled globally.  If this is the case, you can turn up IP Routing with the ip routing global (default) command.

What Can You Not Ping

Cannot ping beyond the NAT router

Cannot ping NAT global address

Average Rating: 0 (0 ratings)


Login or Register to take actions

This Document

Posted June 18, 2009 at 3:51 PM
Comments:1 Avg. Rating:0
Views:2307 Contributors:1

Documents Leaderboard