Packet loss / Server hoster problem?

Discussion in 'Empire Help & Support' started by RandomZh, Apr 29, 2013.

  1. Couldn't work out how to copy paste from cmd, but:

  2. Microsoft Windows [versie 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.

    C:\Users\Dirkjan>tracert smp1.empireminecraft.com

    Traceren van de route naar smp1.empireminecraft.com [198.178.120.206]
    via maximaal 30 hops:

    1 1 ms <1 ms <1 ms mijnmodem.kpn [192.168.2.254]
    2 26 ms 21 ms 67 ms 195.190.242.16
    3 28 ms 23 ms 36 ms nl-rt-dc2-ice-ir02.kpn.net [213.75.64.114]
    4 54 ms 35 ms 23 ms nl-rt-dc2-ice-ir02.kpn.net [213.75.64.114]
    5 32 ms 23 ms 60 ms 213.75.64.166
    6 18 ms 17 ms 17 ms rt2-rou-1022.NL.eurorings.net [134.222.93.140]
    7 113 ms 124 ms 111 ms asd2-rou-1022.NL.eurorings.net [134.222.231.129]

    8 110 ms 111 ms 117 ms nyk-s1-rou-1001.US.eurorings.net [134.222.231.23
    0]
    9 106 ms 106 ms 106 ms nyk-s1-rou-1021.US.eurorings.net [134.222.231.23
    8]
    10 111 ms 115 ms 110 ms ahbn-s1-rou-1041.US.eurorings.net [134.222.228.1
    0]
    11 107 ms 121 ms 105 ms 134.222.248.22
    12 113 ms 105 ms 105 ms lag9.csr1.DCA3.gblx.net [67.16.146.25]
    13 105 ms 105 ms 105 ms 67.16.166.205
    14 127 ms 128 ms 127 ms po5.ar1.MIA2.gblx.net [67.16.148.102]
    15 139 ms 139 ms 154 ms 64.214.140.178
    16 139 ms 139 ms 146 ms ve225.ds01-r136.tpa.hivelocity.net [206.51.235.2
    12]
    17 139 ms 139 ms 139 ms smp1.empireminecraft.com [198.178.120.206]

    De trace is voltooid.

    C:\Users\Dirkjan>
  3. i had no problem copying out of cmd
    chickeneer likes this.
  4. problem seems fixed now though
  5. Ive had some extreme block the last couple of weeks. My ping has risen to over 1500 so somethings up....

    Could this be related? Im in sweden, Stockholm.
    I dont know since I have no more understanding of the internet more then its a world wide web :)

    This is my tracer thingy:

    Tracing route to utopia.empire.us [198.178.120.219]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms dsldevice.lan [192.168.1.1]
    2 20 ms 18 ms 20 ms gw6-no99.tbcn.telia.com [213.64.181.1]
    3 19 ms 23 ms 18 ms s-b1-link.telia.net [213.155.130.63]
    4 19 ms 24 ms 20 ms s-b3-link.telia.net [80.91.249.250]
    5 21 ms 20 ms 19 ms s-akix-i1-link.telia.net [80.91.246.41]
    6 20 ms 19 ms 19 ms te8-3-10G.ar2.ARN3.gblx.net [64.208.110.41]
    7 143 ms 141 ms 144 ms 64.214.140.178
    8 157 ms 162 ms 156 ms ve225.ds01-r136.tpa.hivelocity.net [206.51.235.2
    12]
    9 148 ms 149 ms 147 ms 198.178.120.219

    Trace complete.
  6. Can everyone who's having issues put this in the command prompt

    ping 198.178.120.219 -t

    and leave it running for half an hour or so, this'll give it time to show up any lag spikes with your connection.

    Once half an hour or so has passed press CTRL+C and then post the statistics that come up.
  7. http://pastebin.com/rUEtYYgC
  8. An explanation to tracert, for those interested:

    A packet goes over several routers to its destination. Lets say the connection between some two routers is bad, losing 50% packets. So how we find out between which routers this happens? Tracert executes 3 times a ping to each router. Some routers do never ever respond to that ping but still route packets. These routers are ok and always timeout (which is displayed as a star * ) And when for example the first 8 lines of tracert all shows a millisecond value, then the connection up to router 8 is fine. But when sometimes at line 9 there is a star *, then the connection from you to router 9 is not good. Since we now know the connection is well up to router 8 and not well to router 9, the problem is likely to be between router 8 and 9. Tracert does only do 3 pings, so if by accident all of these 3 tries come through you would not find the culprit. Therefore run tracert multiple times. And if by accient at e.g. line 9 all 3 tries show timeout (a star *) then it could also be one of those routers not responding to ping at all but still working. Thats sometimes hard to tell. But when some pings to a certain router timeout while other pings do not, then there is packetloss on the route to that router. Exercise: Analyze the tracert's that I've pasted. :)
    thestar19 likes this.