Routing issue on home network

[libbistovall1]

Please take a look at the attached diagram; I made the diagram in packet tracer, but it is just a diagram of my home network. I have also attached the config and route info for both routers.

The PC in Raleigh can ping the Seattle router, but the Seatlle router can't ping the Raleigh PC. The Seattle traceroute to the Raleigh PC dies at the Raleigh routers serial port.

[Jon Marshall]

so you didn't expect the ping to successfully get to the PC, just that they would register on the acces list.

I didn't know whether the ping was getting there or not but the acl would have shown if the ping packet was leaving the router going to the PC. If was leaving the router then the next check would have been to see if the PC was sending a packet back to the router.

If you did change the interface on Raleigh it may be that the route took time to propogate to Dallas and Seattle.

Difficult to say.

Jon

[libbistovall1]

Thanks again Jon for your help. It helps to have someone go through problems with when you are learning. Just articulating the problem helps. If you get a chance, please do look at my telnet posting - I can telnet to Dallas, but not Seattle or Raleigh https://supportforums.cisco.com/comment/9563981#comment-9563981

[libbistovall1]

Problem still not resolved: Neither Dallas nor Seattle can see the 4.0 network. I did resolve the screwy wan card issue; it was the slot. I removed a card I wasn't using and moved the wan card over there. Now the ports are what they say. That did not resolve my issue. I guess I need to try Jon's access list test.

[Jon Marshall]

Just to clarify the Seattle and Dallas routers need to have a route for the 192.168.4.0/24 network before testing with the acls.

Without that route nothing will work.

Jon

[libbistovall1]

I mistakenly noted this as the correct answer. The answer was that ethernet port was bad on the Raleigh router and the slot with that I had the serial card in on the Dallas router was bad. What do you want for a $20 router.