Cannot access local internet gatway (linksys WRv54G) from a remote client that is connected to the local site via a dedicated T1 using two Cisco 1720 routers.
IP Path -> 220.127.116.11 <--> 18.104.22.168 <--> 10.1.1.1 <--> 10.1.1.108 <--> internet
Remote PC NIC settings
Remote Cisco 1720 Router
Local Cisco 1720 router
Ciso/Linksys WRV54G Internet Gateway
Trying to ping from 22.214.171.124 to 126.96.36.199 (google.com which is dynmic so I always ping from a system in the 10.1.1.X environment to be sure I have a valid IP to test with)
I could not ping internet goole ip address from 10.1.1.1 router so I added ip route 0.0.0.0 0.0.0.0 10.1.1.108 and I coudl ping the google.com ip.
I could not ping from 188.8.131.52 to 10.1.1.108 so I added a route to 10.1.1.108 to 184.108.40.206, mask 255.255.255.255.
It worked so I can ping to 10.1.1.108 and 220.127.116.11 from 18.104.22.168, but cannot ping to google internet ip address.
I added a route to 22.214.171.124 ip route 0.0.0.0 0.0.0.0 10.1.1.108 and ip route 0.0.0.0 0.0.0.0 10.1.1.1 neither resolved my being able to ping the internet ip address.
Can anyone tell me what I'm doing wrong?
From first glance, does the 10.1.1.108 router know how to get to the 126.96.36.199/24 subnet? Are you running a routing protocol or static routes? If static, on the 10.1.1.108 router, add a static route of 188.8.131.52/24 pointing to 10.1.1.1. Also, how many routers are we talking about? I see 2 (184.108.40.206 and 10.1.1.1 on 1 router and 10.1.1.108 and ISP address on the 2nd router) Is that not correct?
Thanks for the quick reply.
Linksys 10.1.1.108 has route table enteries
220.127.116.11 to 10.1.1.1
18.104.22.168 to 10.1.1.1
We only wnated internet access on the one device 22.214.171.124 this is why we did not use 126.96.36.199
RIP is not enabled
Two Cisco routers one is 10.1.1.1 and the other is 188.8.131.52 and One Lynksys 10.1.1.108.
All static routes - I did notice RIP enabled on 10.1.1.1 and 184.108.40.206 devices, will recheck this I'm thinking v 1.0.
If RIP is enabled only on one device, that wouldn't cause your issue because it's not really doing anything without a neighbor. So, your 2 Cisco routers will have 2 addresses per router: Lan side and Wan side.
What are the 2 addresses on the "10.1.1.1" router and the 2 addresses on the "220.127.116.11" router?
I am trying to ftp the run-config but it is not getting to destination.
The ftp server is giving a timed out error
I'm using copy run ftp://_user_account:_password@IP_Address
If I ftp from a windows computer it send fine.
Any ideas on this or how I can get the configuration saved to a text?
You could run up a free tftp server on the target machine, it's a simple and effective way to save configs as text to a remote host.
here is startupcfg for 10.1.1.1
here is runningcfg for 10.1.1.1
Here is startupconfig for 18.104.22.168
Here is runningconfig for 22.214.171.124
Here is routing table of linksys 10.1.1.108
Here is the routing confg for 10.1.1.108 [note i enabled RIP version 1 and 2 in an attempt to make it work]
The WAN side is the T1 line on both Cisco routers.
RIP V 2 is enabled on all three devices. Is this a problem? You had made this comment "If RIP is enabled only on one device, that wouldn't cause your issue".
I need to adjust my original answer of no routing protocol, but I see the RIP2 is enabled on both Cisco routers.
I just added the RIP on the linksys.
Could this be a problem?
All these devices are using static ip addresses.
Well I've been trying some things since I have been studying and comparing these configurations but it still is not working.
I noticed the RIP is version 2 on both Cisco routers and after research it looks like default type is multicast.
So in the linksys router I changed the RIP settings to only RIP2 and Rip2-Multicast. But alas not solved!
Where I am...
Successful ping to internet ip from 10.1.1.1 okay.
Fails pinging to internet ip from 126.96.36.199 failed.
I did notice on the 10.1.1.1 router that I can ping the ISP device (facing ip to internet) and ISP gateway
But on the 188.8.131.52 router I can only ping the ISP device (facing ip to internet) but not the ISP gateway. Is this a sign or a sympton of the problem *sigh*.