Kind of strange. What does debug ip packet give you. If you are running other IP data then use debug ip packet 101 with the access list below. That will make it easier to sort through the output. Have you tried slowing down the clock rate or switching which side is DCE?
access-list 101 permit icmp any any. Marc Russell www.ccbootcamp.com ""McHugh Randy"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Anyone have an ideas on this half successfull ping across two directly > connect serial interfaces? Clock rate, encapsulation, controllers and cables > look OK. Address on R4 is 172.16.1.4/24 and R2 is 172.16.1.5/24 . Here is > the ping from R4 > R4#ping 172.16.1.5 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 172.16.1.5, timeout is 2 seconds: > .!.!. > Success rate is 40 percent (2/5), round-trip min/avg/max = 32/32/32 ms > > Same thing from R2 to R4 > R2#ping 172.16.1.4 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 172.16.1.4, timeout is 2 seconds: > !.!.! > Success rate is 60 percent (3/5), round-trip min/avg/max = 28/30/32 ms > Thanks > Randy Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=30450&t=30449 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
