Routing - ping A-B, can't ping B-A

Question

Hi,
First time setting up routing on real equipment, and can't seem to get it right. Equipment is:
1. 5500 (CatOS 4.3, IOS 11.3) (old equipment, not under maintenance, being thrown into the battle due to a new building that has to open, and the Cisco equipment order got hung up in contract negotiations and wont be here in time for the building opening...)
2. 3620 (IOS 12.1)
3. Two workstations.
Connections are:
ws1 (10.70.5.100) -> 5500, 3/1.
ws2 (10.70.1.100) -> 5500, 3/2.
3620, Fa0/1 (10.70.200.2) -> 5500, 3/24.
On ws2, I can ping 3620.
Also on ws2, I can telnet to 3620.
On 3620, in the telnet session from ws2, I can NOT ping ws2. (Can't ping ws2 from 3620 in a terminal session either.)
On 5500, in terminal session with switch (CatOS), can ping 10.70.1.1, 10.70.1.250, 10.70.5.1, 10.70.200.1 (those 4 are various switch interfaces), and can ping 10.70.200.2 (3620 Fa0/1). Can NOT ping ws1, ws2.
On 5500, terminal session with MSFC, can ping all switch interfaces. Can NOT ping ws1, ws2.
On 3620, terminal session, can ping all switch interfaces. Can NOT ping ws2, ws1.
Ws1 can NOT ping ws2. And ws2 can NOT ping ws1.
Configs attached. (The 3620 config, and the MSFC config also have "sh ip route" output at the bottom of the files.)
Could someone tell me what I doing wrong? (BTW - I'm pretty sure I've got the default-routes and gateway of last resort mucked up, but that wouldn't explain the above, since all subnets above are routes in ospf, right?)
TIA...

Answer 1

Linnea
I have a theory about part of your problem and some observations which might help. I suspect that the problem with pinging TO the workstations may be that they are running a private firewall which blocks ping.
Your message is explicit that ws2 can ping and telnet to the 3620 but does not say whether ws1 can access anything. If ws1 can not access other resources then I would check to see if its default gateway is set.
I note that the MSFC has configured a static default route and that it does show up in the routing table. That is good. I note that the 3620 has configured a static default route but that it does not show up in the routing table. That is not good. I believe the reason for that is that the default route specifies a next hop of 10.0.70.1 which is out interface FastEthernet0/0. But it looks like FastEthernet is protocol down state - the interface does not show up in the routing table - and so the default route does not work. If you fix the problem with the interface the default route will probably work.
I also note that the 3620 defines a default-gateway and defines a default route. This is not necessarily bad but I want to be sure that you understand what this is doing. Default route and default gateway are two very different things. Default route is used when the 3620 is acting as a router and is forwarding packets. Default gateway would be used when the 3620 is acting as an IP host (but not as a router). The default gateway here is just the same as default gateway on a PC. There are a couple of circumstances where the 3620 may use the default gateway: if you configure "no ip routing" which would make the 3620 into a bridge, or if the 3620 boots into rxboot mode.
HTH
Rick