Frieda
There are parts of the configuration of the 3com that I do not fully understand (such as the nat outbound 2002 on serial1/0. And the specification of the static routes seems a bit odd (why are there a group of host specific routes since there is also a more general static route?).
But I am pretty sure that I understand the problem with attempting to ping Ethernet 0/0 of the 3com from the Cisco. The problem is that the addresses overlap. The Cisco believes that the addresses of the 3com are locally connected on the Cisco and therefore will not go over the serial to get to them. From the 3com configuration:
interface Ethernet0/0
ip address 191.166.28.15 255.255.254.0
note that the subnet mask of 255.255.254.0 means that the address space includes both 191.166.28 and 191.166.29.
And from the Cisco config:
interface Ethernet0
ip address 191.166.29.19 255.255.254.0
And note that it is using the same subnet mask and therefore is claiming exactly the same address space as the 3com.
That is why the Cisco can not ping the Ethernet of the 3com. I am surprised that 3com can ping Cisco. To make it work you will need separate address spaces on the 3com and the Cisco.
HTH
Rick
HTH
Rick
