A WEIRD Problem

[spidermanfan]

OK a little background first.
We have 2 divisions a west coast and a east coast. (I work at the east coast).
West coast uses eigrp on all routers, we use static on ours.
to communicate between the 2 divisions we use a static route between the two.
4 day's ago we could no longer ping one of their Risc Servers. We could however ping everything else on the subnet the Risc server was on, and they could ping their risc server. No changes were made to the Risc server so we ruled out the Nic.
As a little test I removed the static route from the east coast router that went to the west coast coast. Reloaded the East coast router and added the route back in.
This fixed the problem for a whole 10 seconds.
I am totally stumped! Any Clues?

 

[marsd]

Are the static routes being redistributed into eigrp?
If not you will now most probably have to, I can't imagine that you were getting away without redistributing the route before through route mapping or the like..

 

[jeter]

have you tried a trace route to see where the problem starts?
It looks like you may need a route built in the Risc Server.
the route should have the network of the far end. Jeter@LasVegas.com
J.Fisher CCNA

 

[munsonbrown]

It sound to me like you may have conflicting subnet masks in a routing table somewhere. Any reason why you don't all use eigrp?

 

[marsd]

redistribution of the route solves vlsm difficulties:
so would running eigrp.