Hi,

Slow response but where. Step one check your interface to see what traffic you have at 
the time, check the drops etc. 

If this is ok. 

Do a traceroute to discover the path taken. A traceroute might indicate where to find 
a problem. 

First try trace,  then try a ping to the first point in the WAN, then the next address 
the trace goes to and so on.  

If you are using something like ISDN for you 512K make sure your bundles are correct 
(PPP Multi or whatever).

These problems can be anywhere in the net but are usually close to home.

Just some thoughts,

Teunis,
Hobart, Tasmania
Australia
  



On Tuesday, February 06, 2001 at 09:50:43 AM, Evan Francen wrote:

> All of your times are slow.  1891ms ave., with 3 timeouts/11 echoes.  This
> could be due to alot of different things, check times from your router to
> your ISP router, then continue checking routers from there.  A trace would
> give your more information on where the latency is occurring.
> 
> These are my ping times:
> 
> Pinging 198.133.219.25 with 32 bytes of data:
> 
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=61ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> Reply from 198.133.219.25: bytes=32 time=60ms TTL=246
> 
> Ping statistics for 198.133.219.25:
>     Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 60ms, Maximum =  61ms, Average =  60ms
> 
> So, to answer your question, no this is not a normal symptom, and you will
> have to employ some troubleshooting to find out where/what the problem is.
> 
> HTH,
> Evan
> 
> -----Original Message-----
> From: Alex Boh [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 06, 2001 9:15 AM
> To: [EMAIL PROTECTED]
> Subject: Intermittent ping
> 
> 
> Hi everyone,
>     Hope someone can enlighten me on the preceding issue. Recently I
> acquired a 512Kb lease line point-to-point connection. When I ping from my
> PC to cisco.com (c>ping 198.133.219.25 -t), I got reply and some "request
> time out", Is this a normal symptom?
> 
> Pinging cisco.com [198.133.219.25] with 32 bytes of data:
> 
> Reply from 198.133.219.25: bytes=32 time=1778ms TTL=244
> Request timed out.
> Reply from 198.133.219.25: bytes=32 time=1878ms TTL=244
> Request timed out.
> Reply from 198.133.219.25: bytes=32 time=1661ms TTL=244
> Reply from 198.133.219.25: bytes=32 time=2091ms TTL=244
> Reply from 198.133.219.25: bytes=32 time=1801ms TTL=244
> Request timed out.
> Reply from 198.133.219.25: bytes=32 time=2056ms TTL=244
> Reply from 198.133.219.25: bytes=32 time=1977ms TTL=244
> Reply from 198.133.219.25: bytes=32 time=1890ms TTL=244
> 
> 
> 
> 
> 
> _________________________________
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> 
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> 
> 


--
www.tasmail.com


_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to