Since I posted the message, I am now able to ping from the Workstation to Router A and Router B. No configuration changes to the Workstation or the Router were performed. This has happened in the past, and I am attempting to troubleshot and see why. I do not understand why it happens.
Also there are no access list and the configuration is a very simple one. Any help would be appreciated.
What can't the PC ping, a network on the other side of routerB? RouterB is only advertising one route to routerA, and that's already in routerA's table (directly connected). If there are routes on the other side of routerB, are they in routerA's routing table? Can routerA ping those networks? RouterB can ping the PC but the PC can't ping routerB?
As suggested I checked the arp table on the pc, and discovered the only entry is for RTR A E0 interface. At this point I am only able to ping RTR A at the ip address 22.214.171.124 (which is it's directly connected interface on E0). From the PC I can ping E0 but cannot ping RTR A Serial 1 at ip address 126.96.36.199.
However from RTR B, (which is connected to RTR A via S0), I can ping the PC. From RTR A I can also ping the PC. The only problem I have is pinging in reverse. Going from the PC to RTR A and to RTR B.
Just a question. Does the LAN the PC is attached have more than one router? The second router could be sending default gateway updates to the PC. Even another workstation attached to 2 LANs could be acting as a router. You may want to check the routing table on the PC the next time it fails to get to RtrB.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...