I have 12 branches all connect to my server building via Point to Point T1 in a terminal server environment. From my servers I can ping all of my branches and they come back with times of ~5ms on average, except for one of them. When I run a 'ping 192.168.206.1 -t' (problematic branch) about 1 in every 15 pings is either a timeout or 1200ms - 1700ms, the other 14 are ~7ms. I'm running 2 Cisco 2600's going out to CSU/DSU's then to Cisco 1720's at the branches with CSU/DSU cards.
The reason why I think its the clock rates is because I had that Gilbert branch (192.168.206.X) go down, I thought it was Quest, they proved me wrong, so then I changed the interface on the router, and then the connection worked for 5 days. Then the connection went down again, I called Quest, once again they couldn't loop-back my CSU/DSU on the server side. So then I changed out the CSU/DSU on then server side and the interface on one of the 2600's again, the connection still didn't work, properly. I started another 'ping 192.168.206.1 -t' from the server, 1 in every 15 pings came back successful, then other 14 failed :-\. I then started messing with the clock rates on the interface that connects to that branch, they started improving but still not perfect. Then I set the CSU/DSU (The one that goes out to 192.168.206.1) Clock Rate to 'Internal' from 'Network' and it worked, but still with intermittent ping issues, 1 in every 15 fails, 14 successful.
Could someone point me in the right direction? I wouldn't be too worried about it but my users at that branch are complaining because it is very laggy for them, while typing they have to stop and let the computer catch up. Again, they are the only branch experiencing this problem, while sharing terminal servers with other branches. Also, if someone can tell me why this happened to the first interface card in the first place?