You could also set up a host file for your internal hosts. Further try
traceroute without DNS resolution to narrow your scope of possible
troubles.
mak wrote:
Dear All,
I would like to know, suppose when I traceroute to www.cisco.com.
Each entry within my network displays very slow, once
You might find it will still try to resolve addresses via a DNS. Do the traceroute
without the lookup option set. Traceroute -n xxx.xxx.xxx.xxx. in a Unix environment.
Teunis
Hobart, Tasmania
Australia
On Thursday, December 28, 2000 at 12:43:42 PM, Anil Yadav wrote:
Do you get the same
I would say it is due to DNS lookups and your inside network is not listed
on your DNS server.
Jason...
mak
best if you could provide the trace route results in
details otherwise it would be latency issues
regards,
suaveguru
--- mak [EMAIL PROTECTED] wrote:
Dear All,
I would like to know, suppose when I traceroute to
www.cisco.com.
Each entry within my network displays very slow,
once outside
Do you have an internal DNS server? If so, then
something may be misconfigured. If not, then the
traceroute may be trying to resolve and that is what
is taking so long.
--- mak [EMAIL PROTECTED] wrote:
Dear All,
I would like to know, suppose when I traceroute to
www.cisco.com.
Each entry
Do you get the same results when Trace with the ip address instead ?
anil
On Wed, 27 Dec 2000, Rick Thompson wrote:
Do you have an internal DNS server? If so, then
something may be misconfigured. If not, then the
traceroute may be trying to resolve and that is what
is taking so long.
I've
seen something similar and the problem was that we had accidentally
put
clockrate statements on both routers instead of just
the DCE.
Other
than that, layer 1???. Has that cable tested good elsewhere?
-Francis
-Original Message-From: Richard Holland
[mailto:[EMAIL
7 matches
Mail list logo
