asked on

How to manually decide the route www.yahoomail.com

As www.yahoomail.com is not opening on my internet conenction
As www.yahoomail.com is opening on my friend internet connection So i ask my friend to tracert the route to www.yahoomail.com.

So i want to know can i manually decide the route.
C:\>tracert www.yahoomail.com

Tracing route to rc.fy.b.yahoo.com [206.190.60.37]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 32 ms 47 ms 25 ms triband-del-59.178.31.254.bol.net.in [59.178.31.
254]
4 20 ms 19 ms 19 ms triband-del-59.179.0.60.bol.net.in [59.179.0.60]

5 100 ms 101 ms 101 ms 121.241.106.26.static-delhi.vsnl.net.in [121.241
.106.26]
6 244 ms 241 ms 241 ms 59.163.16.146.static.vsnl.net.in [59.163.16.146]

7 245 ms 247 ms 251 ms if-12-2.icore1.NTO-NewYork.as6453.net [209.58.26
.13]
8 242 ms 241 ms 241 ms if-12-0-0-13.core2.NTO-NewYork.as6453.net [216.6
.97.5]
9 251 ms 249 ms 247 ms if-1-0-0.core3.AEQ-Ashburn.as6453.net [216.6.51.
5]
10 253 ms 251 ms 247 ms ix-3-0-9.core3.AEQ-Ashburn.as6453.net [216.6.51.
30]
11 247 ms 247 ms 255 ms ae-6.pat1.dce.yahoo.com [216.115.102.172]
12 248 ms 247 ms 247 ms ae1-p150.msr2.re1.yahoo.com [216.115.108.21]
13 247 ms 253 ms 247 ms te-8-3.bas-a1.re4.yahoo.com [216.39.49.1]
14 248 ms 248 ms 247 ms w2.rc.vip.re4.yahoo.com [206.190.60.37]

Trace complete.

C:\>

ASKER CERTIFIED SOLUTION

gtworek

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

pankusareen

ASKER

in my case it is like this

racert www.yahoomail.com
Tracing route to rc.fy.b.yahoo.com [68.180.206.184]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 42 ms 33 ms 32 ms triband-del-59.180.127.254.bol.net.in [59.180.12
7.254]
3 35 ms 32 ms 31 ms triband-del-59.179.0.119.bol.net.in [59.179.0.11
9]
4 39 ms 32 ms 32 ms 220.225.251.158
5 54 ms 54 ms 58 ms 115.255.230.31
6 49 ms 51 ms 49 ms 115.255.239.18
7 * * * Request timed out.
8 * 124.124.246.162 reports: Destination net unreachable.

Trace complete.

But when i try to ping 124.124.246.162 it is replying back but in tracert the same ip
(124.124.246.162 ) Destination net unreachable
ping 124.124.246.162

Pinging 124.124.246.162 with 32 bytes of data:

Reply from 124.124.246.162: bytes=32 time=51ms TTL=57
Reply from 124.124.246.162: bytes=32 time=51ms TTL=57
Reply from 124.124.246.162: bytes=32 time=64ms TTL=57
Reply from 124.124.246.162: bytes=32 time=52ms TTL=57

Ping statistics for 124.124.246.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 64ms, Average = 54ms

pankusareen

ASKER

As u see the ip of www.yahoomail.com (It is some time 68.180.206.184 or 206.192.60.37) but both the case the same result

8 * 124.124.246.162 reports: Destination net unreachable.

gtworek

It's error at one of core routers in your provider infrastructure.
You cannot repair it. Just wait. Providers usually detects such configuration errors and the issue reapairs itself.

pankusareen

ASKER

As it is the second day unable to open the mail still thanks for info

pankusareen

ASKER

can u please and post the route of it
tracert www.relianceinsider.com

gtworek

C:\Windows\system32>tracert www.relianceinsider.com
 
Tracing route to relianceinsider.com [97.74.144.171]
over a maximum of 30 hops:
 
  1     5 ms     1 ms     1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  ip-77-222-238-1.spray.net.pl [77.222.238.1]
  3     3 ms     2 ms     2 ms  do-r1.spray.net.pl [83.143.40.193]
  4     3 ms     3 ms     3 ms  host-40-185.spray.net.pl [83.143.40.185]
  5     5 ms     3 ms     3 ms  do-atman-f.spray.net.pl [193.111.37.113]
  6    17 ms    17 ms    18 ms  xe-10-0-0-321.prg-001-score-2-re0.interoute.net
[84.233.160.117]
  7    27 ms    26 ms    47 ms  ae0-0.prg-001-score-1-re0.interoute.net [84.233.
138.205]
  8    27 ms    25 ms    25 ms  ae2-0.fra-006-score-2-re0.interoute.net [84.233.
138.210]
  9    25 ms    25 ms    25 ms  ae0-0.fra-006-score-1-re0.interoute.net [84.233.
207.93]
 10    26 ms    26 ms    27 ms  xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26]
 11    31 ms    27 ms    25 ms  xe-0-0-0.mpr1.fra3.de.above.net [64.125.31.217]
 
 12    57 ms    36 ms    36 ms  xe-0-1-0.mpr1.cdg11.fr.above.net [64.125.31.233]
 
 13    43 ms    41 ms    46 ms  xe-3-1-0.mpr1.lhr2.uk.above.net [64.125.24.1]
 14   117 ms   118 ms   117 ms  so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
 
 15   150 ms   151 ms   150 ms  so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]
 16   175 ms   221 ms   172 ms  xe-1-1-0.mpr4.phx2.us.above.net [64.125.28.73]
 17   174 ms   172 ms   187 ms  xe-1-0-0.mpr3.phx2.us.above.net [64.125.27.97]
 18     *        *        *     Request timed out.
 19   172 ms   171 ms   172 ms  ip-208-109-112-153.ip.secureserver.net [208.109.
112.153]
 20   175 ms   172 ms   172 ms  ip-208-109-112-142.ip.secureserver.net [208.109.
112.142]
 21   175 ms   173 ms   171 ms  ip-216-69-188-77.ip.secureserver.net [216.69.188
.77]
 22   174 ms   172 ms   173 ms  ip-208-109-112-2.ip.secureserver.net [208.109.11
2.2]
 23   172 ms   171 ms   172 ms  ip-216-69-188-126.ip.secureserver.net [216.69.18
8.126]
 24   171 ms   169 ms   170 ms  p3nlh171.shr.prod.phx3.secureserver.net [97.74.1
44.171]
 
Trace complete.

Open in new window