|
From: Geoff Lane on 13 Apr 2008 11:35 I was under the impression that Ping and Tracert were similar utilities with tracert giving a wee bit more information about the connection. Why is it then, if I ping bbc.co.uk I get response times of around 30ms whereas if I tracert the same address it appears to take much longer. Geoff Lane
From: Bit Twister on 13 Apr 2008 11:37 On Sun, 13 Apr 2008 16:35:06 +0100, Geoff Lane wrote: > I was under the impression that Ping and Tracert were similar utilities > with tracert giving a wee bit more information about the connection. > > Why is it then, if I ping bbc.co.uk I get response times of around 30ms > whereas if I tracert the same address it appears to take much longer. tracert is going to be timing each node/hop to bbc.co.uk with dns look ups along the way, Try again with tracert -d bbc.co.uk to suppress DNS look ups
From: Dave Uhring on 13 Apr 2008 11:44 On Sun, 13 Apr 2008 16:35:06 +0100, Geoff Lane wrote: > I was under the impression that Ping and Tracert were similar utilities > with tracert giving a wee bit more information about the connection. There is no tracert in Linux. Why are you asking a windows question here? Are the windows lusers too stupid to answer it?
From: Geoff Lane on 13 Apr 2008 12:27 Dave Uhring wrote: >> I was under the impression that Ping and Tracert were similar utilities >> with tracert giving a wee bit more information about the connection. > > There is no tracert in Linux. Why are you asking a windows question here? I was under the impression that the message header should have shown that I posted to two groups (uk.comp.home-networking) and the Followup-To: this group. I've checked it and it doesn't show this other group. As for my typing tracert, perhaps I should have said 'or traceroute in Linux > Are the windows lusers too stupid to answer it? Not really but Linux users are generally more techie :-) Geoff Lane
From: Geoff Lane on 13 Apr 2008 12:34 Bit Twister wrote: >> I was under the impression that Ping and Tracert were similar utilities >> with tracert giving a wee bit more information about the connection. >> >> Why is it then, if I ping bbc.co.uk I get response times of around 30ms >> whereas if I tracert the same address it appears to take much longer. > > tracert is going to be timing each node/hop to bbc.co.uk with dns > look ups along the way, > > Try again with > tracert -d bbc.co.uk > to suppress DNS look ups Right, done that and from my machine it gives 7 hops to bbc, all except my local machine give around 32ms Ping gives similar times but doesn't ping still have 7 hops to reach the bbc site. Geoff Lane
|
Next
|
Last
Pages: 1 2 3 4 5 6 7 Prev: 10 * 172.16 * 192.168 ... why? Next: 10/100/1000mbps speeds? |