traceroute issues....

  • Thread starter Thread starter Larry
  • Start date Start date
L

Larry

When our sister company in Australia does a traceroute to
our Public IP Address everything looks okay with one
exception: when it "hops" from Sprintlink to nTelos ( our
DSL provider ) the "request timed out" message occurs -
although the traceroute continues ( it is hop 11 of the 17
or 18 hops ). Australia is telling us that we need to fix
this. I contacted nTelos and they are telling me that it
is simply due to the fact that their router does not do
DNS Reverse Lookup - thus the request timed out message.
They are saying that there is no problem. I would tend to
agree. However, I am realitively new to the "networking"
side of things ( mostly software on servers /
workstations ).

The traceroute does reach our Public IP Address. There is
simply the request timed out message that concerns
Australia....

Thanks,

Larry
 
So long as you have end to end connectivity, then there is no issue. you
will find that some people configure their equipment to not reply whatsoever
to an ICMP packet. This is normal practice. If you didn't reach the
opposite site, then you'd have need for concern.
 
Back
Top