I believe that we need some clarification from Phillip about what the problem is. If the problem is attempting to access routerC and PIX from routerA itself, then the packets will be sourced from its serial interface by default and the solution to the problem is the route to 10.10.10.0/30 as Edison suggests (or the solution is to use extended ping, or traceroute, or specify the source interface for telnet, tftp, etc to be the Ethernet interface).
If the problem is attempting to access routerC or PIX from end stations on the Ethernet of routerA then the static route to 10.10.10.0/30 may or may not be required. If the static routes on routerC and the PIX for network 192.168.2.0 specify the serial interface on routerC as the next hop, then the static route is necessary. But if the static routes on routerC and the PIX specify the Ethernet of routerB as the next hop then routerC and the PIX do not need to know about the serial link or its address to access the 192.168.2.0 network. They only need to know that routerB can get to it.
I do note that the syntax given on routerC and the PIX for static routes is incorrect:
ip route 192.168.2.0 10.10.10.2
I assume that this is a typo for the forum posting rather than a cut and paste from the config. But if it were cut and paste from the config then the lack of a mask in the static route would be a syntax error.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...