...
Traceroute Results from pinger.pern.edu.pk
Following error message was received while While trying to access pingerjms.pern.edu.pk (PoP Jamshoro) from pinger.pern.edu.pk (PoP Islamabad) following traceroute results were obtainedtraceroute server busy at the moment. Please try again later.
See The Naming System for information on host.domain and Addresses for information on Internet addresses.
Code Block |
---|
Executing exec(traceroute, -m 30 -q 3 -f 3, 121.52.154.2, 140)
traceroute to 121.52.154.2 (121.52.154.2), 30 hops max, 140 byte packets
4 rwp44.pie.net.pk (221.120.251.58) 35.530 ms 35.491 ms 35.424 ms
5 khi77.pie.net.pk (221.120.205.70) 36.129 ms 36.417 ms 36.490 ms
6 pinger.hyd.usindh.edu.pk (121.52.154.2) 35.945 ms 35.931 ms 35.916 ms
|
However, while accessing usindh (non PoP Jamshoro) following error message was encountered.) we found
Code Block |
---|
Executing exec(traceroute, -m 30 -q 3 -f 3, 121.52.155.62, 140)
traceroute to 121.52.155.62 (121.52.155.62), 30 hops max, 140 byte packets
4 rwp44.pie.net.pk (221.120.251.58) 35.473 ms 35.442 ms 35.451 ms
5 khi77.pie.net.pk (221.120.205.70) 36.107 ms 36.347 ms 36.388 ms
6 172.31.253.66 (172.31.253.66) 36.077 ms 36.201 ms 36.248 ms
7 usindh.edu.pk (121.52.156.130) 36.550 ms 36.583 ms 36.623 ms
8 (121.52.155.62) 36.917 ms !X 36.899 ms !X 36.885 ms !X
|
Extra hops can be seen in Usindh traceroute (hop 6 and 7). For both of the nodes, it takes 36.105 ~ 36.4 ms to reach the hop khi77.pie.net.pk, however, as Can't find address for host name pinger.usindh.edu.pk. Probably an unknown host.