// Troubleshooting guide
Inside hosts cannot reach the internet through NAT/PAT
Symptoms
- Inside hosts can ping their gateway but nothing on the internet
- show ip nat translations is empty
- The router itself can ping the internet but hosts cannot
- Some inside subnets work and others do not
First, split the problem
From the router, ping a public address. The router's own traffic is not translated, so:
- Router fails too → not a NAT problem. Check the outside interface, the default route and the ISP link.
- Router works, hosts fail → NAT, the ACL, or host settings. Continue below.
Step 1 — inside and outside roles
show ip nat statistics
The output lists the outside and inside interfaces. Every LAN interface or subinterface that carries hosts must be ip nat inside; the internet-facing interface must be ip nat outside. A new VLAN subinterface added later without ip nat inside is the most common cause of "only some subnets work".
Step 2 — the ACL that selects traffic
show running-config | include ip nat inside source
show access-lists
- Does the ACL in the
ip nat inside source listcommand actually exist, with that exact name or number? - Does it permit the hosts' subnet, with the right wildcard mask (0.0.0.255, not 255.255.255.0)?
- Are its hit counters increasing when a host tries to reach the internet?
Step 3 — the overload statement
ip nat inside source list NAT-INSIDE interface GigabitEthernet0/0/1 overload
Without overload, only one inside host at a time can use the interface address. With a pool, check that the pool addresses are valid and routed to you by the ISP.
Step 4 — routing
- The router needs a default route (
show ip route 0.0.0.0). - Hosts need the router as their default gateway.
- With more than one router inside, every router must send internet traffic towards the NAT router.
Step 5 — read the translation table
show ip nat translations
clear ip nat translation *
After a ping from a host, an entry like icmp 203.0.113.2:1 192.168.10.25:1 … proves translation works — the problem is then beyond the router (ISP, DNS, a firewall). No entry means the traffic never matched: go back to steps 1–2.
Step 6 — DNS
If ping 8.8.8.8 works from a host but browsing does not, NAT is fine — check the DNS server configured on the host or in the DHCP pool.
Checklist
| Check | Healthy |
|---|---|
| Router can reach the internet | Yes |
| Inside/outside roles | Every LAN inside, WAN outside |
| NAT ACL | Exists, correct wildcard, hits increasing |
| Overload | Present for PAT on an interface |
| Default route | Present on the router; hosts use the router as gateway |
| Translations | Entries appear when hosts send traffic |