Mark,
Traceroute would be one of the best tools to use at this point. What do your
traceroutes show? Where are the biggest delays? Have you tried several
internet looking glasses to see if everyone shows similar problems trying to
reach that destination? Some of my favorite looking glasses are
www.traceroute.org and nitrous.digex.net. See how many hops you're
traversing and where the delay is introduced prior to suspecting the
router's processor or a routing problem. There could be several factors,
such as errors on WAN links or errors on LAN links causing retransmissions.
Is the final destination a host? It could be getting blasted with too much
to do. Remember, ping is low on the list of things to do if devices are
busy.
Chris
-----Original Message-----
From: mak [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 4:23 AM
To: [EMAIL PROTECTED]
Subject: problem on ping
Hi all,
When I ping to a internal network from Internet. The time is very long,
it is greater than 2500ms. I would like to know what factors make this
happen, is it the routers CPU work load? or there is a routing problem?
Thanks
mak
_________________________________
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]
