The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Network failure(s), where is it and who is responsible?

Discussion in 'General Discussion' started by wolfjlupus, Apr 2, 2007.

  1. wolfjlupus

    wolfjlupus Member

    Joined:
    Sep 7, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    151
    We've migrated our WHM/CPanel server over to a new set of IP's and for some reason I can't connect to them without using a public proxy, this even includes the providers website now. I can't figure out exactly who is responsible and where the point of failure is exactly to get whoever is responsible to fix it......

    Traceroute/ping from my home location to the old server (which works)...

    ---

    traceroute to 85.17.13.20 (85.17.13.20), 64 hops max, 40 byte packets
    1 192.168.0.1 (192.168.0.1) 1.303 ms 0.872 ms 0.302 ms
    2 10.209.128.1 (10.209.128.1) 10.084 ms 8.325 ms 12.404 ms
    3 s10-2.cr01-knwk.wa.charter.com (68.186.73.13) 9.361 ms 28.299 ms 10.369 ms
    4 68.186.73.49 (68.186.73.49) 19.083 ms 25.163 ms 9.095 ms
    5 12.127.79.29 (12.127.79.29) 15.992 ms 30.138 ms 13.872 ms
    6 12.127.6.30 (12.127.6.30) 39.046 ms 60.329 ms 23.623 ms
    7 12.122.86.45 (12.122.86.45) 14.747 ms 24.446 ms 34.399 ms
    8 br1-a350s5.attga.ip.att.net (192.205.33.238) 25.601 ms 21.799 ms 37.404 ms
    9 te2-1-10g.ar2.ams1.gblx.net (67.17.92.153) 170.920 ms 170.827 ms 171.122 ms
    10 64.213.76.150 (64.213.76.150) 170.045 ms 169.986 ms 175.025 ms
    11 62.212.95.146 (62.212.95.146) 178.002 ms 178.664 ms 177.936 ms
    12 novosibirsk.v-unix.sbp.attikh.net (85.17.9.244) 182.034 ms 178.866 ms 179.335 ms
    13 rakebacknation.com (85.17.13.20) 179.246 ms 181.997 ms 189.018 ms

    ---

    Ping has started ...

    PING 85.17.13.20 (85.17.13.20): 56 data bytes
    64 bytes from 85.17.13.20: icmp_seq=0 ttl=48 time=178.690 ms

    --- 85.17.13.20 ping statistics ---
    1 packets transmitted, 1 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 178.690/178.690/178.690/0.000 ms

    ---

    Traceroute/ping from my home location to the new server (which fails)...

    ---

    traceroute to 77.235.37.113 (77.235.37.113), 64 hops max, 40 byte packets
    1 192.168.0.1 (192.168.0.1) 7.087 ms 0.303 ms 0.203 ms
    2 10.209.128.1 (10.209.128.1) 18.712 ms 38.402 ms 11.605 ms
    3 s10-2.cr01-knwk.wa.charter.com (68.186.73.13) 33.955 ms 41.386 ms 13.996 ms
    4 68.186.73.49 (68.186.73.49) 26.398 ms 13.656 ms 20.702 ms
    5 12.127.79.29 (12.127.79.29) 12.477 ms 28.289 ms 20.980 ms
    6 12.127.6.30 (12.127.6.30) 27.392 ms 19.994 ms 17.067 ms
    7 12.127.6.61 (12.127.6.61) 23.416 ms 15.131 ms 14.724 ms
    8 192.205.33.114 (192.205.33.114) 21.345 ms 15.118 ms 16.140 ms
    9 so-0-0-0.cr2.sea1.us.above.net (64.125.28.186) 16.115 ms 29.307 ms 17.559 ms
    10 so-2-0-0.cr2.ord2.us.above.net (64.125.30.222) 72.402 ms 70.323 ms 75.338 ms
    11 so-1-1-0.mpr2.lga5.us.above.net (64.125.27.34) 88.384 ms 88.768 ms 88.345 ms
    12 so-0-0-0.mpr1.lga5.us.above.net (64.125.27.237) 94.959 ms 86.645 ms 90.357 ms
    13 so-7-0-0.mpr3.ams1.nl.above.net (64.125.27.186) 172.967 ms 207.672 ms 201.681 ms
    14 ge1-1.sr1.esy.nl.leaseweb.net (82.98.247.34) 169.246 ms 166.772 ms 166.667 ms
    15 * * *
    16 * * *
    17 * * *
    //
    64 * * *

    ---

    Ping has started ...

    PING 77.235.37.113 (77.235.37.113): 56 data bytes

    --- 77.235.37.113 ping statistics ---
    1 packets transmitted, 0 packets received, 100% packet loss

    ---

    Traceroute/ping from dnsstuff to the old server (which works)...

    ---

    Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
    1 9 1 1 1.3 ms

    66.36.240.2 AS14361
    HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unix: 20:35:48. 71
    2 6 1 5 1.3 ms [+0ms]

    66.36.224.232 AS0
    IANA-RSVD-0 gec2.core1.dca2.hopone.net. 0 miles [+0] 254 US Unix: 21:35:29. 17
    3 12 2 1 1.3 ms [+0ms]

    66.36.224.18 AS0
    IANA-RSVD-0 ge3-0.core1.iad1.hopone.net. 0 miles [+0] 253 US Unix: 20:37:31.545
    4 1 2 1 1.7 ms [+0ms]

    206.223.115.86 AS2914
    NTTA-2914 ge-4-1-0.mpr1.iad10.us.mfnx.net. 0 miles [+0] 251 US Unix: 20:35:08.131
    5 1 2 3 1.9 ms [+0ms]

    64.125.30.118 AS6461
    MFNX so-4-0-0.mpr1.iad2.us.above.net. 0 miles [+0] 250 US Unix: 20:35:08.163
    6 4 2 2 2.4 ms [+0ms]

    64.125.27.74 AS6461
    MFNX so-6-0-0.mpr1.iad5.us.above.net. 0 miles [+0] 249 US Unix: 20:35:08.195
    7 2 2 4 2.5 ms [+0ms]

    64.125.29.229 AS6461
    MFNX so-4-0-0.mpr1.iad1.us.above.net. 0 miles [+0] 248 US Unix: 20:35:08.227
    8 3 3 3 3.0 ms [+0ms]

    64.125.28.125 AS6461
    MFNX so-1-0-0.mpr1.dca2.us.above.net. 0 miles [+0] 247 US Unix: 20:35:08.261
    9 123 74 74 74 ms [+71ms]

    64.125.27.58 AS6461
    MFNX so-0-1-0.mpr1.lhr2.uk.above.net. 0 miles [+0] 246 US Unix: 20:35:08.429
    10 92 89 90 89 ms [+14ms]

    64.125.27.178 AS6461
    MFNX so-7-0-0.mpr1.ams5.nl.above.net. 0 miles [+0] 249 US Unix: 20:35:08.486
    11 100 90 90 90 ms [+0ms]

    64.125.31.190 AS6461
    MFNX so-4-0-0.cr2.ams2.nl.above.net. 0 miles [+0] 249 US Unix: 20:35:08.549
    12 102 92 90 90 ms [+0ms]

    82.98.242.162 AS6461
    MFNX gi3-0.r1.sbp.leaseweb.net. 0 miles [+0] 248 DE Unix: 20:35:08.602
    13 91 90 91 90 ms [+0ms]

    85.17.9.244 AS16265
    LEASEWEB novosibirsk.v-unix.sbp.attikh.net. 0 miles [+0] 56 NL Unix: 20:35:09.147
    14 124 90 90 90 ms [+0ms]

    85.17.13.20 ASN=16265[Destination Unreachable] rakebacknation.com. 0 miles [+0] 56 Unix: 20:35:09.196
    15 * * * 99999 ms [+99909ms]

    [Unknown] [Unknown - Firewall did not respond] -1 miles [+0] 0 miles [+0]
    16 * * * 99999 ms [+0ms]

    [Unknown] [Unknown - Firewall did not respond] -1 miles [+0]

    ---

    Pinging 85.17.13.20 [85.17.13.20]:

    Ping #1: Got reply from 85.17.13.20 in 90ms [TTL=56]
    Ping #2: Got reply from 85.17.13.20 in 91ms [TTL=56]
    Ping #3: Got reply from 85.17.13.20 in 89ms [TTL=56]
    Ping #4: Got reply from 85.17.13.20 in 90ms [TTL=56]


    Variation: 2.0ms (+/- 2%)

    Shortest Time: 89ms
    Average: 90ms
    Longest Time: 91ms

    Done pinging 85.17.13.20!

    ---

    Traceroute/ping from dnsstuff to the new server (which works)...

    ---

    Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
    1 1 0 0 0.8 ms

    66.36.240.2 AS14361
    HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unix: 20:17:56.686
    2 0 0 2 0.8 ms [+0ms]

    66.36.224.232 AS0
    IANA-RSVD-0 gec2.core1.dca2.hopone.net. 0 miles [+0] 254 US Unix: 21:17:37.642
    3 5 2 1 1.6 ms [+0ms]

    66.36.224.18 AS0
    IANA-RSVD-0 ge3-0.core1.iad1.hopone.net. 0 miles [+0] 253 US Unix: 20:19:40.257
    4 2 4 2 1.6 ms [+0ms]

    206.223.115.86 AS2914
    NTTA-2914 ge-4-1-0.mpr1.iad10.us.mfnx.net. 0 miles [+0] 251 US Unix: 20:17:16.839
    5 6 1 2 1.6 ms [+0ms]

    64.125.30.118 AS6461
    MFNX so-4-0-0.mpr1.iad2.us.above.net. 0 miles [+0] 250 US Unix: 20:17:16.879
    6 2 3 5 2.1 ms [+0ms]

    64.125.29.133 AS6461
    MFNX so-4-0-0.mpr2.iad1.us.above.net. 0 miles [+0] 249 US Unix: 20:17:16.906
    7 33 8 2 2.1 ms [+0ms]

    64.125.27.210 AS6461
    MFNX so-1-0-0.mpr2.dca2.us.above.net. 0 miles [+0] 248 US Unix: 20:17:16.975
    8 76 83 74 74 ms [+72ms]

    64.125.27.166 AS6461
    MFNX so-0-1-0.mpr1.lhr3.uk.above.net. 0 miles [+0] 247 US Unix: 20:17:17.107
    9 104 88 86 83 ms [+8ms]

    64.125.27.221 AS6461
    MFNX so-1-0-0.mpr3.ams1.nl.above.net. 0 miles [+0] 250 US Unix: 20:17:17.208
    10 108 85 85 83 ms [+0ms]

    82.98.247.34 AS6461
    MFNX ge1-1.sr1.esy.nl.leaseweb.net. 0 miles [+0] 251 DE Unix: 20:17:17.241
    11 108 83 83 83 ms [+0ms]

    77.235.33.50 AS0
    IANA-RSVD-0 gianna.v-unix.esy.attikh.net. 0 miles [+0] 59 GR Unix: 20:19:10.519
    12 93 * * 93 ms [+9ms]

    77.235.37.113 AS0
    IANA-RSVD-0
    [Reached Destination]77.235.37.113 [No PTR] 59 GR Unix: 20:19:10.550

    ---

    Pinging 77.235.37.113 [77.235.37.113]:

    Ping #1: Got reply from 77.235.37.113 in 84ms [TTL=59]
    Ping #2: Got reply from 77.235.37.113 in 84ms [TTL=59]
    Ping #3: Got reply from 77.235.37.113 in 83ms [TTL=59]
    Ping #4: Got reply from 77.235.37.113 in 83ms [TTL=59]


    Variation: 1.2ms (+/- 1%)

    Shortest Time: 83ms
    Average: 83ms
    Longest Time: 84ms

    Done pinging 77.235.37.113!

    ---

    I tried pinging from the new server to 68.186.73.13 since that's showing on the traceroute path, then to 71.83.224.13 (which is the IP my router reports as it's WAN address).

    ---

    root@alpha7 [~]# ping -c 1 68.186.73.13
    PING 68.186.73.13 (68.186.73.13) 56(84) bytes of data.

    --- 68.186.73.13 ping statistics ---
    1 packets transmitted, 0 received, 100% packet loss, time 0ms

    ---

    root@alpha7 [~]# ping -c 1 71.83.224.131
    PING 71.83.224.131 (71.83.224.131) 56(84) bytes of data.
    From 12.127.79.30 icmp_seq=0 Packet filtered

    --- 71.83.224.131 ping statistics ---
    1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
    , pipe 2

    ---

    I tried pinging from the old server to 68.186.73.13 since that's showing on the traceroute path, then to 71.83.224.13 (which is the IP my router reports as it's WAN address).

    ---

    root@old [~]# ping -c 1 68.186.73.13
    PING 68.186.73.13 (68.186.73.13) 56(84) bytes of data.
    64 bytes from 68.186.73.13: icmp_seq=0 ttl=245 time=170 ms

    --- 68.186.73.13 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 170.487/170.487/170.487/0.000 ms, pipe 2

    ---

    root@old [~]# ping -c 1 71.83.224.131
    PING 71.83.224.131 (71.83.224.131) 56(84) bytes of data.
    64 bytes from 71.83.224.131: icmp_seq=0 ttl=53 time=179 ms

    --- 71.83.224.131 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 179.271/179.271/179.271/0.000 ms, pipe 2

    ---
     
    #1 wolfjlupus, Apr 2, 2007
  2. wolfjlupus

    wolfjlupus Member

    Joined:
    Sep 7, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    151
    Traceroutes from the old/new servers...

    --- old server ---

    --- 71.83.224.131 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 179.271/179.271/179.271/0.000 ms, pipe 2
    root@old [~]# traceroute 71.83.224.131
    traceroute to 71.83.224.131 (71.83.224.131), 30 hops max, 38 byte packets
    1 novosibirsk.v-unix.sbp.attikh.net (85.17.9.244) 0.289 ms 0.228 ms 0.146 ms
    2 Leaseweb.k196.cr2.ams2.nl.if.gi4-0.above.net (82.98.242.161) 0.387 ms 0.320 ms 0.350 ms
    3 pos3-0.cr1.ams2.nl.above.net (64.125.31.169) 0.687 ms 0.523 ms 0.543 ms
    MPLS Label=159 CoS=5 TTL=1 S=0
    4 so-3-2-0.mpr3.ams1.nl.above.net (208.184.231.53) 9.323 ms 1.003 ms 1.222 ms
    5 so-2-1-0.mpr1.lga5.us.above.net (64.125.27.185) 86.410 ms 86.480 ms 88.464 ms
    6 so-0-0-0.mpr2.lga5.us.above.net (64.125.27.238) 86.403 ms 86.398 ms 86.436 ms
    7 so-3-0-0.cr2.ord2.us.above.net (64.125.27.33) 106.635 ms 106.741 ms 106.799 ms
    8 so-3-0-0.cr2.sea1.us.above.net (64.125.30.221) 158.819 ms 158.570 ms 158.841 ms
    9 so-0-0-0.cr1.sea1.us.above.net (64.125.28.185) 158.866 ms 158.756 ms 158.769 ms
    10 192.205.33.113 (192.205.33.113) 164.822 ms 164.163 ms 164.887 ms
    11 12.127.6.62 (12.127.6.62) 165.510 ms 165.453 ms 165.749 ms
    MPLS Label=32350 CoS=5 TTL=1 S=0
    12 12.127.6.29 (12.127.6.29) 164.726 ms 164.928 ms 164.480 ms
    13 12.127.79.30 (12.127.79.30) 169.963 ms 169.436 ms 169.851 ms
    14 g9-3.dr1.knwc.wa.charter.com (68.186.73.50) 169.997 ms 169.460 ms 169.966 ms
    15 S2-0.cmts01-wnch.wa.charter.com (68.186.73.14) 171.237 ms 171.263 ms 171.040 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    --- new server ---

    traceroute to 71.83.224.131 (71.83.224.131), 30 hops max, 38 byte packets
    1 gianna.v-unix.esy.attikh.net (77.235.33.50) 0.226 ms 0.255 ms 0.150 ms
    2 85.17.100.149 (85.17.100.149) 1.051 ms 1.115 ms 0.952 ms
    3 10ge.ams.gblx.net (64.213.76.149) 1.480 ms 2.675 ms 1.463 ms
    4 192.205.33.241 (192.205.33.241) 84.293 ms 84.786 ms 84.506 ms
    5 tbr1-p010401.n54ny.ip.att.net (12.123.3.57) 153.900 ms 153.383 ms 153.263 ms
    MPLS Label=31563 CoS=5 TTL=1 S=0
    6 tbr1-cl14.cgcil.ip.att.net (12.122.10.2) 154.222 ms 154.036 ms 153.675 ms
    MPLS Label=32256 CoS=5 TTL=1 S=0
    7 tbr2-cl22.cgcil.ip.att.net (12.122.9.134) 153.896 ms 153.907 ms 154.299 ms
    MPLS Label=30732 CoS=5 TTL=1 S=0
    8 tbr2-cl11.st6wa.ip.att.net (12.122.10.62) 154.343 ms 154.491 ms 154.112 ms
    MPLS Label=32350 CoS=5 TTL=1 S=0
    9 12.127.6.29 (12.127.6.29) 152.979 ms 153.069 ms 153.140 ms
    10 * * *
    11 * 12.127.79.30 (12.127.79.30) 158.950 ms !X *
    12 12.127.79.30 (12.127.79.30) 158.148 ms !X * *
    13 * 12.127.79.30 (12.127.79.30) 158.112 ms !X *
    14 12.127.79.30 (12.127.79.30) 158.074 ms !X * *
    15 * * 12.127.79.30 (12.127.79.30) 158.058 ms !X
    16 * 12.127.79.30 (12.127.79.30) 158.157 ms !X *
    17 * 12.127.79.30 (12.127.79.30) 157.876 ms !X *
    18 * 12.127.79.30 (12.127.79.30) 157.936 ms !X *
    19 * * *
    20 12.127.79.30 (12.127.79.30) 158.879 ms !X * *
    21 * * 12.127.79.30 (12.127.79.30) 158.458 ms !X
    22 * 12.127.79.30 (12.127.79.30) 158.327 ms !X *
    23 * * *
    24 * * *
    25 12.127.79.30 (12.127.79.30) 158.866 ms !X * *
    26 * * *
    27 * 12.127.79.30 (12.127.79.30) 158.185 ms !X *
    28 * * 12.127.79.30 (12.127.79.30) 157.360 ms !X
    29 * 12.127.79.30 (12.127.79.30) 157.589 ms !X *
    30 12.127.79.30 (12.127.79.30) 158.166 ms !X * *

    (I don't know what to make of the end there, it seems quite screwy to me)
     
    #2 wolfjlupus, Apr 2, 2007
  3. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    8
    Trophy Points:
    193
    Looks like you are passing through a netsplit condition out on the open internet
    in route to your final destination and it would appear that the problem point
    is a gateway between AT&T's network and Global Crossing's network.

    There is probably very little you can do other than just sit and wait because
    based on the information you posted, I would say there is nothing wrong
    with either your server or your ISP.

    The problem is out on the open internet between those two destinations and
    you are just passing through a bad part of the internet. This can have the
    effect of making your destination address appear down or slow to you even
    though it may actually be fully online and working fast in reality.

    Think of it as trying to drive your car from New York to Los Angeles and
    when you get to Tennessee, the roads are all ripped up with road
    construction so you are stuck in traffic waiting to get through Tennessee
    and it takes you a much longer time to get to Los Angeles even though
    things may be running good both at your final destination and also
    the place where you started.

    These sort of things usually clear up on their own in a few days fortunately.
    If not, you can contact AT&T and Global Crossing and put on some pressure
    but that usually does not accomplish much as there are probably another
    million people out there already calling them on the same issue.
     
    #3 Spiral, Apr 2, 2007
(You must log in or sign up to post here.)
Loading...
Similar Threads - Network failure(s) where
  1. sabin rai

    Dig query connection timeout from outside network

    sabin rai, May 11, 2017, in forum: Bind / DNS / Nameserver Issues
    Replies:
    1
    Views:
    86
    cPanelMichael
    May 11, 2017
  2. Datalab

    Network is unreachable error

    Datalab, Feb 7, 2017, in forum: E-mail Discussions
    Replies:
    3
    Views:
    192
    cPanelMichael
    Feb 9, 2017
  3. Senor

    SOLVED cPanel + Hyper-V = slow network ?

    Senor, Jan 23, 2017, in forum: General Discussion
    Replies:
    3
    Views:
    336
    cPanelMichael
    Jan 26, 2017
  4. Ilyas

    API requests over internal network

    Ilyas, Jan 20, 2017, in forum: Workarounds and Optimization
    Replies:
    1
    Views:
    182
    cPanelMichael
    Jan 25, 2017
  5. rinkleton

    Networking hardware requirements

    rinkleton, Oct 7, 2016, in forum: General Discussion
    Replies:
    1
    Views:
    253
    cPanelMichael
    Oct 11, 2016

Share This Page