Hi guys
Have you ever thought how your request will travel to the server.
Actually when some request has been given from the client, the request will travel many intermediate nodes.
To know what are the intermediate nodes your request has traveled or will travel you can use the command
"tracert"
tracert -> trace route
this command will trace the route of the request that is being given from the client.
i have showed an example below how the request reaches google web page from my system
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PRAVEEN>tracert www.google.co.in
Tracing route to www.google.co.in [74.125.236.56]
over a maximum of 30 hops:
1 62 ms 74 ms 87 ms 220.224.141.145
2 87 ms 58 ms 53 ms 115.255.236.89
3 64 ms 55 ms 67 ms 124.124.239.189
4 113 ms 97 ms 106 ms 115.255.239.45
5 90 ms 94 ms 97 ms 72.14.212.118
6 114 ms 93 ms 90 ms 209.85.241.52
7 130 ms 123 ms 123 ms 209.85.251.95
8 118 ms 145 ms 364 ms 209.85.241.33
9 117 ms 140 ms 126 ms maa03s04-in-f24.1e100.net [74.125.236.56]
Trace complete.
C:\Users\PRAVEEN>
For example if the request takes 9 nodes to reach the server, we call it has 9 hops.
Execute the above command and know how your request travels
Have a great week..!!
Praveen Kumar Rajendran
CollabNet Software Private Limited,Chennai
Have you ever thought how your request will travel to the server.
Actually when some request has been given from the client, the request will travel many intermediate nodes.
To know what are the intermediate nodes your request has traveled or will travel you can use the command
"tracert"
tracert -> trace route
this command will trace the route of the request that is being given from the client.
i have showed an example below how the request reaches google web page from my system
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PRAVEEN>tracert www.google.co.in
Tracing route to www.google.co.in [74.125.236.56]
over a maximum of 30 hops:
1 62 ms 74 ms 87 ms 220.224.141.145
2 87 ms 58 ms 53 ms 115.255.236.89
3 64 ms 55 ms 67 ms 124.124.239.189
4 113 ms 97 ms 106 ms 115.255.239.45
5 90 ms 94 ms 97 ms 72.14.212.118
6 114 ms 93 ms 90 ms 209.85.241.52
7 130 ms 123 ms 123 ms 209.85.251.95
8 118 ms 145 ms 364 ms 209.85.241.33
9 117 ms 140 ms 126 ms maa03s04-in-f24.1e100.net [74.125.236.56]
Trace complete.
C:\Users\PRAVEEN>
For example if the request takes 9 nodes to reach the server, we call it has 9 hops.
Execute the above command and know how your request travels
Have a great week..!!
Praveen Kumar Rajendran
CollabNet Software Private Limited,Chennai
Good da..last column is ip address,but what about 1st 3 columns??( eliminating the numberings)
ReplyDeletei think it is timing but why it is splitted into 3 columns??
let me take the 1st one...first 3 number indicates the hops or the device via which the request has travel to reach a device that can be named using the ip address
ReplyDelete