08-04-2010 12:09 PM - edited 03-04-2019 09:18 AM
08-04-2010 12:12 PM
Can you ping the linksys from your router ?
Is the linksys responsible for NAT or is to meant to be this router ?
Does "sh ip int brief" on the router show both interfaces up ?
What does "sh ip route" show on the router ?
Jon
08-04-2010 03:06 PM
You have NAT configured, but I don't see any NAT statements. Traffic will not route unless you configure the NAT rules for exemptions and NAT traffic.
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094e77.shtml
Try:
ip nat inside source list 1 interface g0/0 overload
access-list 1 permit 172.16.10.0 0.0.0.255
08-04-2010 06:38 PM
I really appreciate the response I am getting from this forum:
I have tried running:
ip nat inside source list 1 interface g0/0 overload
access-list 1 permit 172.16.10.0 0.0.0.255
Below is detail my result from all my ping tests:
ip address of my laptop via dhcp connected on the g0/1 interface:
C:\Documents and Settings\admin.HOME-0H5JYFL4V7>ipconfig /all
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : dns.mydomain.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-E2-94-G0-D3-71
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 172.16.10.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.16.10.1
DHCP Server . . . . . . . . . . . : 172.16.10.1
DNS Servers . . . . . . . . . . . : 4.10.101.20
6.8.10.2
Lease Obtained. . . . . . . . . . : Wednesday, August 04, 2010 7:35:40 P
M
Lease Expires . . . . . . . . . . : Wednesday, August 04, 2010 9:35:40 P
pinging gateway from the my laptop:
C:\>ping 172.16.10.1
Pinging 172.16.10.1 with 32 bytes of data:
Reply from 172.16.10.1: bytes=32 time<1ms TTL=255
Reply from 172.16.10.1: bytes=32 time<1ms TTL=255
Reply from 172.16.10.1: bytes=32 time<1ms TTL=255
Reply from 172.16.10.1: bytes=32 time<1ms TTL=255
Ping statistics for 172.16.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
pinging int G0/0 interface from the laptop:
Pinging 192.168.20.15 with 32 bytes of data:
Reply from 192.168.20.15: bytes=32 time<1ms TTL=255
Reply from 192.168.20.15: bytes=32 time<1ms TTL=255
Reply from 192.168.20.15: bytes=32 time<1ms TTL=255
Reply from 192.168.20.15: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.20.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging the linksys (gateway) from the laptop:
Pinging 192.168.20.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.20.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
On the router:
"Show ip int brief" gives:
GigabitEthernet0/0 192.168.20.15 YES NVRAM up up
GigabitEthernet0/1 172.16.10.1 YES NVRAM up up
"show ip route" gives:
Gateway of last resort is 192.168.20.1 to network 0.0.0.0
C 192.168.20.0/24 is directly connected, GigabitEthernet0/0
C 172.16.10.0/16 is directly connected, GigabitEthernet0/1
S* 0.0.0.0/0 [1/0] via 192.168.20.1
On the router:
Sending 5, 100-byte ICMP Echos to 172.16.10.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
router#ping 192.168.20.15
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.20.15, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
router#ping 192.168.20.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.20.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
router#ping google.com
Translating "google.com"...domain server (4.10.101.20) [OK]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 66.102.7.99, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/92/96 ms
08-04-2010 09:33 PM
Can your host, 172.16.10.x ping an internet host? For example, 4.2.2.2?
I would guess that your Linksys has no idea how to return packets to 172.16.10.x if NAT is not properly happening... Can we get an updated sanitized "show run" from your Cisco Router?
08-05-2010 02:25 AM
I think what Tim suggested on having NAT could solve your problem.
try it ip nat inside source .... interface x/x overload
then your ACL statement..
Best Regards,
Christopher
08-07-2010 01:44 PM
Thank you all for help. The problem was actually my NAT configuration. I cleaned up my config and applied your suggestions. It is now working.
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