Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a newbie to networking.

I tried using the tracert.exe command to the results were displayed after 1 minute or so including the many hops.

Whereas if I type in my browser it takes less than 10 seconds to show the home page or infact any search results too are displayed in less than a minute(just to remove the cache & proxy doubts).

My question is, why is there such a difference in the time taken if the originator and destination are same.

share|improve this question

closed as not constructive by mdpc, Zoredache, Bryan, Iain Dec 21 '12 at 7:53

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

In order to draw a conclusion from the fact that something didn't happen, you have to wait the longest it could possibly take for that thing to happen. Displaying a web page doesn't require drawing conclusions like that. – David Schwartz Dec 21 '12 at 6:42
Don't know why there is a -1 even after stating this is a question from newbie – bala Dec 21 '12 at 7:11
@bala, are you a professional acting as a system administrator? Do you believe this is a system administration question? Did you spend any time doing some homework, by looking up via Google how traceroute works, or how web browsers work? Some of us are a bit picky here, we do expect you to do some research on your own first, and to review our faq. – Zoredache Dec 21 '12 at 7:20

You realize that the programming for display a website page is different than a tracert. The speed in tracert is most likely due to all the DNS lookups/ICMP timeouts being processed for all the intermediate hosts involved in the trace.

Also in browsing you might be looking at your local cache in which case very little work / time needs to be done.

Thus this is normal behavior.

share|improve this answer

Because when you go to Google, you're just fetching data from Google. Not stopping at every hop along the way to query those systems too (which tracert does). And since some of those systems won't respond to ICMP queries, your tracert runs into timeouts, where as your connection to Google's web servers on a protocol they're intended to respond on does not.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.