We have a small network. A 2620 on either side of a T1. Computers A, B, and C are on one side. Computers D, E, and F are on the other side. Sometimes, E will decide it won't communicate with C. E can't ping C. C can't ping E. E can ping A and B. C can ping D and F. A and B can ping D, E, and F. After a few minutes, E will be able to ping C. A while later, B will decide it can't communicate with F, and so on. It seems to happen when the T1 hiccups (the large, well-known multinational company we got it from can't seem to make it work consistently). I think it may happen if the two machines are communicating when the T1 hiccups. I'm not really sure on this - it is a casual observance. Sometimes the pings will get "request timed out", and other times "destination host unreachable". What is causing this, and how can I prevent it? I don't recall seeing this in any other networks I have worked on. Thanks, Benjamin Walling BTW, our T1 provider is blaming the Super Bowl (we're in Tampa) for all of our troubles. They say their cross connects keep getting stolen by people hooking up lines for the Super Bowl. _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
