1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved Destination host unreachable.

Discussion in 'Networking (Hardware & Software)' started by memo5200, 2013/02/22.

Page 2 of 3
  1. 2013/02/23
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    Goooooooooooooood :D,I feel relief to know its not only me but i dunno explanation about how my close friend (live nearby) has ping :mad: do u ?
     
    memo5200,
    #21
  2. 2013/02/23
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    Nope. And without access to the people and/or equipment involved, all we can do is keep on guessing.
     
    Last edited: 2013/02/23
    SpywareDr,
    #22
    memo5200 likes this.


  3. to hide this advert.

  4. 2013/02/24
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    ok lets say we can do nothing about it , but cant we do a thing about reducing delay , latency or lag?
     
    memo5200,
    #23
  5. 2013/02/24
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Not much you can do about that either. Latency depends upon many factors:
    your Internet connection,
    your computer's TCP/IP settings,
    your ISP's network,
    the routers between you and the destination,
    the destination server's configurations.

    Here's an example. This trace route is between my computer and Yahoo. Notice that the first 5 hops are from my router through my ISP network (COX - 68.x.x.x) and no latency, but the Yahoo network's routers are slower and the destination server is slowest of all. Of course, the latency will vary at any given time of day.

    Code:
    C:\WINDOWS\system32>tracert yahoo.com
Tracing route to yahoo.com [206.190.36.45]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2     8 ms     8 ms     7 ms  10.2.200.1
  3     7 ms     6 ms     7 ms  ip68-100-2-161.dc.dc.cox.net [68.100.2.161]
  4     7 ms     9 ms     7 ms  172.22.70.137
  5     7 ms     7 ms     9 ms  68.1.4.133
  6     9 ms     8 ms     9 ms  68.105.30.114
  7     8 ms     8 ms     9 ms  ae-6.pat2.dce.yahoo.com [216.115.102.176]
  8    34 ms    55 ms    55 ms  ae-6.pat2.dax.yahoo.com [216.115.96.21]
  9    96 ms   133 ms   109 ms  ae-5.pat2.pao.yahoo.com [216.115.101.130]
 10   111 ms   134 ms   132 ms  ae-6.pat2.swp.yahoo.com [216.115.100.91]
 11   138 ms   130 ms   141 ms  ae-1.msr2.gq1.yahoo.com [66.196.67.3]
 12   121 ms   129 ms   175 ms  ae-1.msr1.gq1.yahoo.com [66.196.67.5]
 13   145 ms   130 ms   122 ms  et-17-1.fab4-1-gdc.gq1.yahoo.com [98.137.31.176]

 14   124 ms   123 ms   122 ms  po-12.bas1-7-prd.gq1.yahoo.com [206.190.32.19]
 15   [B]249 ms   311 ms   276 ms[/B]  ir1.fp.vip.gq1.yahoo.com [206.190.36.45]

Trace complete.
     
    TonyT,
    #24
    memo5200 likes this.
  6. 2013/02/24
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    My Internet connectio is :ADSL2
    TCP/IP setting : Default
    My ISP: Te-Date Egypt

    here is my yahoo tracert it seems troubled I guess


    Code:
    C:\Windows\System32>tracert yahoo.com

Tracing route to yahoo.com [206.190.36.45]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.16.1
  2    15 ms    13 ms    14 ms  EMBABA-R03C-GZ-EG [163.121.170.79]
  3   175 ms   186 ms   189 ms  host-163.121.213.22.tedata.net [163.121.213.22]

  4    34 ms    40 ms    26 ms  host-163.121.213.22.tedata.net [163.121.213.22]

  5   195 ms    93 ms   199 ms  host-163.121.212.161.tedata.net [163.121.212.161
]
  6   173 ms   120 ms   159 ms  10.44.0.6
  7   161 ms   158 ms   172 ms  10.44.3.1
  8   190 ms   185 ms   173 ms  host-163.121.185.149.tedata.net [163.121.185.149
]
  9     *        *      242 ms  pos5-2-0.palermo9.pal.seabone.net [195.22.197.10
1]
 10   362 ms   344 ms   424 ms  xe-1-1-1.ashburn2.ash.seabone.net [195.22.216.14
9]
 11   382 ms   371 ms   384 ms  g2-12-bas2.dce.yahoo.com [206.126.236.2]
 12   407 ms   345 ms   385 ms  ae-4.pat2.che.yahoo.com [216.115.101.145]
 13   477 ms   438 ms   425 ms  ae-6.pat1.dnx.yahoo.com [216.115.96.207]
 14   467 ms   465 ms   438 ms  ae-6.pat2.swp.yahoo.com [216.115.100.91]
 15   432 ms   463 ms   464 ms  ae-1.msr2.gq1.yahoo.com [66.196.67.3]
 16   440 ms   410 ms   398 ms  ae-1.msr2.gq1.yahoo.com [66.196.67.3]
 17   401 ms   437 ms   260 ms  et-17-1.fab1-1-gdc.gq1.yahoo.com [98.137.31.164]

 18   535 ms   426 ms   424 ms  et-17-1.fab6-1-gdc.gq1.yahoo.com [98.137.31.184]

 19   463 ms   436 ms   477 ms  po-10.bas1-7-prd.gq1.yahoo.com [206.190.32.15]
 20   653 ms   584 ms   451 ms  ir1.fp.vip.gq1.yahoo.com [206.190.36.45]

Trace complete.
     
    memo5200,
    #25
  7. 2013/02/24
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Yes, there is latency on your ISP's network.
     
    TonyT,
    #26
    memo5200 likes this.
  8. 2013/02/24
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    Looks like Seabone was also a problem.
     
    SpywareDr,
    #27
    memo5200 likes this.
  9. 2013/02/24
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1


    dunno what are u talking about :)
    any suggestion to fix it excluding call my ISP's technical support because they mostly wont help :(
     
    memo5200,
    #28
  10. 2013/02/24
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Nothing you can do to fix their problems.
     
    Admin.,
    #29
    memo5200 likes this.
  11. 2013/02/24
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338


    Your post #25 showed:
    Code:
     9     *        *      242 ms  pos5-2-0.palermo9.pal.[b][color=red]seabone.net[/color][/b] [195.22.197.101]
10   362 ms   344 ms   424 ms  xe-1-1-1.ashburn2.ash.[b][color=red]seabone.net[/color][/b] [195.22.216.149]

    peering.seabone.net/map.html
    See the map:
     

    Attached Files:

    SpywareDr,
    #30
    memo5200 likes this.
  12. 2013/02/25
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    software like TCP Optimizer ...etc , could help !
     
    memo5200,
    #31
  13. 2013/02/25
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Nope. Again, their network has problems, nothing you can do about it.
     
    Admin.,
    #32
    memo5200 likes this.
  14. 2013/02/26
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    If you're in say Egypt and the server you're trying to access is in the U.S., the sheer distance is going to cause a delay.
     
    SpywareDr,
    #33
    memo5200 likes this.
  15. 2013/02/26
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Only if the routers along the way are functioning improperly or overloaded. Packets travel at near speed-of-light rates.
     
    TonyT,
    #34
    memo5200 likes this.
  16. 2013/02/26
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well, as indicated by Tony... hardly noticeable. The original server that started this discussion in located in Singapore.

    I'm only around 1,100 miles away from memo5200, but my ISP connects through Level3, so I have better performance.

    Code:
      1     9 ms    11 ms    12 ms  192.168.149.129 
  2     9 ms     9 ms     7 ms  c133-5.i01-2.onvol.net [212.56.133.5] 
  3    13 ms    14 ms    12 ms  212.56.129.98 
  4    39 ms    39 ms   114 ms  212.73.241.201 
  5    48 ms    59 ms    49 ms  ae-14-14.ebr1.Frankfurt1.Level3.net [4.69.142.194] 
  6    47 ms    44 ms    47 ms  ae-81-81.csw3.frankfurt1.level3.net [4.69.140.10] 
  7    68 ms    90 ms    47 ms  ae-3-80.edge4.Frankfurt1.Level3.net [4.69.154.136] 
  8    57 ms    47 ms    49 ms  glbx-level3-10G.Frankfurt1.Level3.net [4.68.63.242] 
  9    52 ms    62 ms     *     ae8.scr4.FRA4.gblx.net [67.16.145.241] 
 10   199 ms   199 ms   197 ms  xe11-0-0-10G.scr4.SNV2.gblx.net [67.16.164.46] 
 11   208 ms   202 ms   207 ms  e5-3-40G.ar5.SJC2.gblx.net [67.17.72.14] 
 12   316 ms   317 ms   312 ms  starhub-ltd.pos15-1.ar5.sjc2.gblx.net [159.63.48.14] 
 13   308 ms   304 ms   304 ms  tenge-1-1-an-atl-int10.starhub.net.sg [203.118.3.177] 
 14   312 ms   316 ms   313 ms  203.116.9.42 
 15  203.116.186.18  reports: Destination host unreachable.
     
    Arie,
    #35
    memo5200 likes this.
  17. 2013/02/26
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    I got more confused , lets discuss one by one
    First I don't think the distance is the cause ; I've mentioned before everything was OK and I've not any delay , lag or connection issue as result of what I said before I thought it was problem could be solved but unfortunately every day its become worse and worse

    Here is my Singapore Ping for Now:
    Code:
    Reply from 203.116.186.18: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 203.116.186.18: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 203.116.186.18: Destination host unreachable.
Reply from 203.116.186.18: Destination host unreachable.
Request timed out.
Request timed out.


    Yahoo Track :
    Code:
    C:\Users\MEMO>tracert yahoo.com

Tracing route to yahoo.com [98.139.183.24]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.16.1
  2     *        *        *     Request timed out.
  3    14 ms    14 ms    16 ms  host-163.121.215.9.tedata.net [163.121.215.9]
  4    17 ms    15 ms    14 ms  host-163.121.215.9.tedata.net [163.121.215.9]
  5    18 ms    18 ms    22 ms  host-163.121.228.125.tedata.net [163.121.228.125
]
  6    19 ms    19 ms    19 ms  10.44.0.6
  7    16 ms    18 ms    17 ms  10.44.3.1
  8    16 ms    16 ms    17 ms  host-163.121.185.149.tedata.net [163.121.185.149
]
  9   177 ms   179 ms   177 ms  pos6-0.palermo5.pal.seabone.net [213.144.181.73]

 10  203.116.186.18  reports: Destination host unreachable.

Trace complete.
     
    memo5200,
    #36
  18. 2013/02/26
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    It is super simple: Nobody can do anything about your problem EXCEPT your Internet Service Provider.
     
    Arie,
    #37
    memo5200 likes this.
  19. 2013/02/26
    memo5200

    memo5200 Inactive Thread Starter

    Joined:
    2009/05/21
    Messages:
    59
    Likes Received:
    1
    Thanks You all Guys ,I'm so grateful for your concern.
    You did more than you could , I'll mark the post as solved one , cya soon with another stupid problem ;)
     
    memo5200,
    #38
  20. 2013/02/26
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338

    Light travels at 299,792.458 meters (186.2824 miles) per millisecond (in a vacuum). The circumference of the earth is 40,075,000 metres (24,901 miles). 40,075,000 / 299,792.458 = 133.6758 milliseconds ... with absolutely no interference. (See Cisco.com > Bandwidth, Packets Per Second, and Other Network Performance Metrics).
     
    SpywareDr,
    #39
  21. 2013/02/26
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Agreed, I should have been more precise but was in a hurry and had to get off to a job. (my intent was not to prove you wrong, apologies)

    But the delay caused by increased distance is negligible. The delays caused by routers, amplifiers and other hardware can be noticeable, but usually they too are negligible.

    But the main factor of delays is caused by the processing done at the destination. Pings and traceroutes don't account for the destination computer doing anything with the received packets except returning an acknowledgement. Get & Post packets cause the computer to process something, e.g. database queries, documents, etc. That is where delays become noticeable.
     
    TonyT,
    #40
Page 2 of 3

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...