[Troubleshooting] Network Lag!

Discussion in 'Login / Client Support' started by Schism, Nov 28, 2015.

?

Was(is) this helpful?

  1. Yes

    83.3%
  2. No

    16.7%
  1. Schism

    Schism Journeyman

    Joined:
    Nov 12, 2015
    Messages:
    127
    Likes Received:
    39
    Trophy Points:
    28
    Gender:
    Male
    Location:
    Texas
    Howdy!
    Today we are speaking about Networking lag (for Client side, see [Link: Client Lag!])! This little devil can be a game breaker for many players and is also the biggest turn-off in any game. Ultima Online is odd because of being such and old game that relied on older technology IT CAN STILL LAG! I was once the victim of the plague that is known as lag on UO and I am reaching out to others that may have experienced this to give them the help they need.

    Networking Issues / Troubleshooting:
    Network connection. Lag is often defined as: "A period of time between one event or phenomenon and another." As your computer attempts to communicate with the game servers, there are several other hardware components it passes through (switches, routers, computers, etc) Each of these have the ability to affect your network speed (Example in spoiler below.) As you can see, when attempting to connect to aos.ultima-shards.com I pass through 10 different systems!
    Code:
    HOST: 0x1p2-lp                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
      1.|-- router.asus.com                                 0.0%     1    2.0   2.0   2.0   2.0   0.0
      2.|-- 96.120.16.77                                    0.0%     1   14.7  14.7  14.7  14.7   0.0
      3.|-- xe-3-0-1-0-sur03.humble.tx.houston.comcast.net  0.0%     1    6.3   6.3   6.3   6.3   0.0
      4.|-- ae-36-0-ar01.bisbee.tx.houston.comcast.net      0.0%     1   10.3  10.3  10.3  10.3   0.0
      5.|-- 4.68.71.89                                      0.0%     1   10.7  10.7  10.7  10.7   0.0
      6.|-- ???                                            100.0     1    0.0   0.0   0.0   0.0   0.0
      7.|-- INMOTION-HO.ear3.Washington1.Level3.net         0.0%     1   38.3  38.3  38.3  38.3   0.0
      8.|-- ???                                            100.0     1    0.0   0.0   0.0   0.0   0.0
      9.|-- ???                                            100.0     1    0.0   0.0   0.0   0.0   0.0
    10.|-- ehub42.webhostinghub.com                        0.0%     1   41.2  41.2  41.2  41.2   0.0
    
    So let's define some tools that help troubleshoot networking issues:
    • Ping - A Basic command that checks if the remote host you are trying to connect to is alive. It will display the amount of time in milliseconds that it took to reach the remote location.
      - Ping comes pre-installed with all Operating Systems.
    • Traceroute / tracert - Both are the same tool that perform the same function. Traceroute is *nix systems and tracert is Windows. It the most simple of terms- it pings each step of the way (every system it reaches) and stores that amount of time it took to get there. The example first given is an example of a traceroute. This is helpful because if you high amounts of latency, you can see where the issue is starting.
      - Windows: comes pre-installed on Windows as "tracert."
      - *Nix it comes pre-installed as traceroute. Arch Linux requires you to install it from the repositories.
    • MTR - My Traceroute is a tool that performs a traceroute over an allotted amount of time. This is by far the most helpful tool to diagnose any issues you are having. By using MTR, you can check the stability of the connection. Running a single traceroute has the ability to produce various results depends on the load of the distant hardware. MTR collects each traceroute and produces averages, minimum time to reach, maximum time to reach, and the hostname (if available) of the machine.
      - MTR does not come pre-installed. This was an independently created tool and originally named Matt's TraceRoute (MTR.)
      - Windows It is available for free [Link: Here] and is known as WinMTR.
      - *Nix will need to check your repositories for a "mtr" package.

    How-to-Use (Windows Based)
    Ping:
    Code:
    ping -c 4 aos.ultima-shards.com
    Code:
    Result:
    
    PING aos.ultima-shards.com (192.223.24.42) 56(84) bytes of data.
    64 bytes from d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com (192.223.24.42): icmp_seq=1 ttl=113 time=52.9 ms
    64 bytes from d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com (192.223.24.42): icmp_seq=2 ttl=113 time=55.3 ms
    64 bytes from d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com (192.223.24.42): icmp_seq=3 ttl=113 time=52.6 ms
    64 bytes from d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com (192.223.24.42): icmp_seq=4 ttl=113 time=52.9 ms
    
    --- aos.ultima-shards.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 52.616/53.475/55.381/1.120 ms
    Traceroute:
    Code:
    tracert aos.ultima-shards.com
    Code:
    Result:
    Tracing route to aos.ultima-shards.com [192.223.24.42]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
      2     8 ms     9 ms    11 ms  96.120.16.77
      3     8 ms    16 ms     9 ms  xe-3-0-1-0-sur03.humble.tx.houston.comcast.net [68.85.252.181]
      4    11 ms    12 ms    11 ms  ae-36-0-ar01.bisbee.tx.houston.comcast.net [68.85.87.245]
      5    11 ms    16 ms    12 ms  ae-1-0-ar01.bearcreek.tx.houston.comcast.net [68.85.245.153]
      6    20 ms    19 ms    20 ms  be-33662-cr02.dallas.tx.ibone.comcast.net [68.86.92.61]
      7    19 ms    17 ms    20 ms  be-11-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.134]
      8    25 ms    22 ms    21 ms  66.208.229.170
      9    53 ms    78 ms   115 ms  0.xe-2-1-6.XT1.NYC4.ALTER.NET [152.63.3.6]
    10    67 ms    56 ms    58 ms  TenGigE0-6-0-4.GW5.NYC4.ALTER.NET [152.63.17.102]
    11    53 ms    51 ms    52 ms  internap-gw.customer.alter.net [65.217.199.202]
    12    61 ms    52 ms    52 ms  border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.15]
    13    53 ms    51 ms    51 ms  inap-b2.e3.router.nyc.nfoservers.com [70.42.74.254]
    14    57 ms    52 ms    53 ms  d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com [192.223.24.42]
    
    Trace complete.
    WinMTR:
    WinMTR Window:
    Type into the "Host:" portion the hostname of the server you are troubleshooting too.
    [​IMG]
    Code:
    |------------------------------------------------------------------------------------------| 
    |                                      WinMTR statistics                                   |
    |                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    |                         router.asus.com -    0 |  300 |  300 |    0 |    0 |    1 |    0 |
    |                            96.120.16.77 -    0 |  300 |  300 |    3 |    8 |   29 |    8 |
    |xe-3-0-1-0-sur03.humble.tx.houston.comcast.net -    0 |  300 |  300 |    4 |    9 |   47 |   10 |
    |ae-36-0-ar01.bisbee.tx.houston.comcast.net -    0 |  300 |  300 |    7 |   14 |   99 |   10 |
    |ae-1-0-ar01.bearcreek.tx.houston.comcast.net -    0 |  300 |  300 |    6 |   13 |   85 |   11 |
    |be-33662-cr02.dallas.tx.ibone.comcast.net -    0 |  300 |  300 |   12 |   19 |   34 |   14 |
    |be-11-pe02.1950stemmons.tx.ibone.comcast.net -    3 |  269 |  261 |   15 |   19 |   32 |   31 |
    |                          66.208.229.170 -    0 |  300 |  300 |   14 |   23 |   37 |   28 |
    |           0.xe-2-1-6.XT1.NYC4.ALTER.NET -    0 |  300 |  300 |   47 |   61 |  165 |   67 |
    |       TenGigE0-6-0-4.GW5.NYC4.ALTER.NET -    0 |  300 |  300 |   49 |   57 |   68 |   57 |
    |          internap-gw.customer.alter.net -    0 |  300 |  300 |   47 |   52 |   60 |   52 |
    |    border2.pc1-bbnet1.ext1.nym.pnap.net -    0 |  300 |  300 |   47 |   59 |  259 |   49 |
    |    inap-b2.e3.router.nyc.nfoservers.com -    0 |  300 |  300 |   47 |   51 |   62 |   54 |
    |d-192-223-24-42.ded-machine.internap-nyc.nfoservers.com -    0 |  300 |  300 |   49 |   53 |   61 |   53 |
    |________________________________________________|______|______|______|______|______|______|
       WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
    
    [​IMG]
    *Of the two export options, I prefer HTML due to it displaying the columns correctly.

    Reading the information:
    As you can see on the final row, the "Best", "Avrg", and "Wrst" display the amount of time it took to reach the destination. Another source of important information is "Sent" and "Recv" columns. They display the amount of packets sent to the target and how many succeeded. Dropped packets mean lost data, so the less there is- the better.

    What we have covered thus far:
    • We have learned several valuable tools to diagnose issues with a connection to a server.
    • Determining areas of possible problems.
    • Reading the information these tools provide.
    • How to export information to request assistance from others.
    You may be asking... WHAT CAN I DO SCHISM BRO?
    The Good, the Bad, and The Ugly... There may not be much you CAN do.
    • If the issue of high latency is between you and your router, try the following:
      • If using WiFi, move closer to your router. Try to be in the same room as it.
      • Try to find drivers for your WiFi NIC (Network Interface Card), these can normally be found on the website of the manufacture of the laptop (Asus, Lenovo, Dell, Acer, etc) Updating these can result in increased performance if issues were discovered after you purchased your device. Patching it could increase packet transmission and reception.
      • Ethernet Connection (RJ-45 cable.) Typically, a physical (hardware) connection to your router can increase the speed of your connection to your router and then to the World Wide Web! Hardware is typically faster than WiFi.
      • Relocating your Router
      • Updating the firmware of your Router (Very much like updating the drivers for your WiFi NIC, but for your router.)
    • Outside your router:
      • There isn't much. You do not control that hardware and there isn't much you can do.
      • Look into a VPN (alternative routing of your connection.)
    Next up will be resolving issues that may be client side! If you have anything to add to this network troubleshooting guide, feel free to comment below! I will add it to the top!
    Comments, concerns, issues, etc? Feel free to leave below!

    - Schism
     
    Last edited: Jul 24, 2016
    Coheed likes this.
  2. Schism

    Schism Journeyman

    Joined:
    Nov 12, 2015
    Messages:
    127
    Likes Received:
    39
    Trophy Points:
    28
    Gender:
    Male
    Location:
    Texas
    [reserved for le' future]
     
    Last edited: Nov 28, 2015
  3. Punkte

    Punkte Administrator Community Manager Developer

    Joined:
    Jun 5, 2015
    Messages:
    471
    Likes Received:
    225
    Trophy Points:
    43
    Gender:
    Male
    Location:
    Sweet Dreams Inn
    Great guide! This has been stickied!