Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2004
    Location
    Toronto, Canada
    Posts
    31

    ManageMyBox Packet Loss

    Hi everyone! I am somewhat of a noob and would like to ask you for your opinion. I have 2 new servers with ManageMyBox and am getting packet losses from multiple locations. I have also tried doing tests on another client of theirs with same results = packet losses. I've even checked my duplex settings of my NIC. Tech support keeps insisting that their network is fine and closing my ticket. Am I crazy and imagining this?

    Any comments or findings you can come up with will be greatly appreciated. Even better, a copy of your pings would be really nice. I don't know who else to turn to as response to tickets takes a long time and phone support is not available. Here are the results of my pings from other different locations:

    FROM ROGERS TORONTO
    -------------------
    Pinging server.mybro.com [66.79.168.140] with 32 bytes of data:

    Reply from 66.79.168.140: bytes=32 time=103ms TTL=56
    Request timed out.
    Reply from 66.79.168.140: bytes=32 time=101ms TTL=56
    Reply from 66.79.168.140: bytes=32 time=102ms TTL=56
    Request timed out.
    Reply from 66.79.168.140: bytes=32 time=101ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 66.79.168.140: bytes=32 time=102ms TTL=56

    Ping statistics for 66.79.168.140:
    Packets: Sent = 10, Received = 5, Lost = 5 (50% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 101ms, Maximum = 103ms, Average = 101ms


    Tracing route to server.mybro.com [66.79.168.140]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.10.1
    2 8 ms 8 ms 7 ms 10.174.64.1
    3 7 ms 7 ms 7 ms vl-201.gw03.mtmk.phub.net.cable.rogers.com [66.185.91.9]
    4 9 ms 9 ms 8 ms gi-3-1.gw01.mtmk.phub.net.cable.rogers.com [66.185.83.249]
    5 12 ms 11 ms 9 ms so-4-2-2.gw02.ym.phub.net.cable.rogers.com [64.71.240.185]
    6 8 ms 9 ms 9 ms so-2-0-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
    7 26 ms 26 ms 24 ms pos-2-0.igw01.ny8th.phub.net.cable.rogers.com [66.185.81.102]
    8 28 ms 27 ms 28 ms 64.71.240.18
    9 26 ms 27 ms 25 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
    10 39 ms 39 ms 39 ms te4-3.ccr02.ord01.atlas.cogentco.com [154.54.1.190]
    11 50 ms 49 ms 50 ms te3-4.ccr02.mci01.atlas.cogentco.com [154.54.5.173]
    12 85 ms 85 ms 85 ms te3-4.ccr02.sfo01.atlas.cogentco.com [154.54.6.161]
    13 87 ms 89 ms 86 ms te4-4.ccr02.sjc01.atlas.cogentco.com [154.54.2.138]
    14 86 ms 85 ms 87 ms vl3496.mpd01.sjc05.atlas.cogentco.com [154.54.6.70]
    15 90 ms 87 ms 86 ms managed-solutions-group.demarc.cogentco.com [38.102.194.158]
    16 * * * Request timed out.
    17 * 103 ms * ns1.mybro.com [66.79.168.140]
    18 105 ms 102 ms * ns1.mybro.com [66.79.168.140]
    19 * 105 ms * ns1.mybro.com [66.79.168.140]
    20 103 ms 101 ms * ns1.mybro.com [66.79.168.140]
    21 * 106 ms * ns1.mybro.com [66.79.168.140]
    22 * 103 ms * ns1.mybro.com [66.79.168.140]
    23 102 ms 101 ms 103 ms ns1.mybro.com [66.79.168.140]

    Trace complete.


    FROM DNSSTUFF.COM
    -----------------
    Pinging 66.79.168.140 [66.79.168.140]:

    Ping #1: Got reply from 66.79.168.140 in 48ms [TTL=58]
    Ping #2: * [No response]
    Ping #3: Got reply from 66.79.168.140 in 48ms [TTL=58]
    Ping #4: * [No response]


    Variation: 0.2ms (+/- 0%)

    Shortest Time: 48ms
    Average: 24ms
    Longest Time: 48ms

    Done pinging 66.79.168.140!

    http://www.dnsstuff.com/tools/tracer...c3258c02617019


    FROM WWW.HIS.COM (Greece, Athens, TEI - TECHNOLOGICAL EDUCATION INSTITUTE - Helios)
    -----------------------------------------------------------------------------------
    PING 66.79.168.140 (66.79.168.140): 56 data bytes
    64 bytes from 66.79.168.140: icmp_seq=0 ttl=54 time=71.899 ms
    64 bytes from 66.79.168.140: icmp_seq=1 ttl=54 time=71.798 ms

    --- 66.79.168.140 ping statistics ---
    5 packets transmitted, 2 packets received, 60% packet loss
    round-trip min/avg/max/stddev = 71.798/71.849/71.899/0.050 ms


    FROM USA, MD, Rockville, Heller Information Services via MCI-CAIS)
    ------------------------------------------------------------------
    PING 66.79.168.140 (66.79.168.140): 56 octets data
    64 octets from 66.79.168.140: icmp_seq=1 ttl=50 time=202.2 ms

    --- 66.79.168.140 ping statistics ---
    5 packets transmitted, 1 packets received, 80% packet loss
    round-trip min/avg/max = 202.2/202.2/202.2 ms


    FROM DOMAINTOOLS.COM
    --------------------
    Host IP Address Ping Time
    1. 66.79.168.140 66.79.168.140 25.66ms
    2. 66.79.168.140 66.79.168.140 25.48ms
    3. 66.79.168.140 Timed Out
    4. 66.79.168.140 66.79.168.140 25.49ms
    5. 66.79.168.140 66.79.168.140 25.75ms
    6. 66.79.168.140 Timed Out
    7. 66.79.168.140 66.79.168.140 25.36ms

    Total Duration: 127.74 ms
    Average Ping: 18.25 ms

    Please tell me I'm not crazy.

  2. #2
    I'm getting packet loss to the server too.

    --- ns1.mybro.com ping statistics ---
    95 packets transmitted, 59 received, 37% packet loss, time 94012ms
    rtt min/avg/max/mdev = 62.719/64.922/76.783/2.656 ms

    From your traceroutes, it doesn't look like an issue between the internet and their network, it looks like an issue between their network and your server.

  3. #3
    Join Date
    Dec 2004
    Location
    Toronto, Canada
    Posts
    31
    Thanks TarballX. I hope they will believe me soon and look into the issue. I would like to give them a chance to fix it as everything else is good except for the packet losses.

  4. Newsletters

    Subscribe Now & Get The WHT Quick Start Guide!

Related Posts from theWHIR.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •