Network overview:
One 2611 connected via E0 to 172.16.105.0/24 network
E1, S1, and S2 are on 172.18.0.0 network subnetted various ways
Problem/Analysis:
Any router connected to the 2611 cannot ping the 172.16.105.0 network. The 2611 can however ping anything on the 172.16.105.0 network and out to the Internet (The 172.16.0.0 network is behind a Linux box with IPtables doing NAT). The 172.16.0.0 network is routed using RIPV2, and the 172.18.0.0 network is using OSPF. The 2611 has learned about all of the 172.16.0.0 subnets via RIP and has all of the 172.18.0.0 networks via OSPF. Also, the gateway of last resort has been set as 172.16.105.2 (E0 on the 2611) and is being redistributed. On the other routers, we can tracrt to and IP on the 172.16.0.0 network and it gets to the 2611 but dies there. Why is this happening. We have determined that the 2611 is the problem point be we cannot figure out why.
One 2611 connected via E0 to 172.16.105.0/24 network
E1, S1, and S2 are on 172.18.0.0 network subnetted various ways
Problem/Analysis:
Any router connected to the 2611 cannot ping the 172.16.105.0 network. The 2611 can however ping anything on the 172.16.105.0 network and out to the Internet (The 172.16.0.0 network is behind a Linux box with IPtables doing NAT). The 172.16.0.0 network is routed using RIPV2, and the 172.18.0.0 network is using OSPF. The 2611 has learned about all of the 172.16.0.0 subnets via RIP and has all of the 172.18.0.0 networks via OSPF. Also, the gateway of last resort has been set as 172.16.105.2 (E0 on the 2611) and is being redistributed. On the other routers, we can tracrt to and IP on the 172.16.0.0 network and it gets to the 2611 but dies there. Why is this happening. We have determined that the 2611 is the problem point be we cannot figure out why.