Forum Discussion

DBWoodynz's avatar
DBWoodynz
10 years ago
Solved

[Guide] to identify network issues for Swtor

*Netstat/Pingpath/Tracert/Speedtest.net/PingPlotter Netstat OK with your game open and running please alt tab back to your desktop. Please click Start and in the search line down the bottom ...
  • proxos666's avatar
    proxos666
    10 years ago

    I consider this a Good Guide, over the years it has certainly helped narrow down issues in particular local network issues with SWTOR.

    I would be quite happy to point people to these directions, to look at the results.

    Beats a thread that says "I have Lag" and all the replies are "Me Too"

    problem is not all causes of lag are equal.

    And unless any tests are run and if it is consistent lag then it wont get fixed without looking for a cause.

    To Simplify testing I would just use the below IP addresses initially

    • If you play on an East Coast server: 159.153.92.28
    • If you play on a West Coast server: 159.153.68.252
    • If you play on a European server: 159.153.72.252

    As detailed here

proxos666's avatar
proxos666
Hero+
10 years ago

I consider this a Good Guide, over the years it has certainly helped narrow down issues in particular local network issues with SWTOR.

I would be quite happy to point people to these directions, to look at the results.

Beats a thread that says "I have Lag" and all the replies are "Me Too"

problem is not all causes of lag are equal.

And unless any tests are run and if it is consistent lag then it wont get fixed without looking for a cause.

To Simplify testing I would just use the below IP addresses initially

  • If you play on an East Coast server: 159.153.92.28
  • If you play on a West Coast server: 159.153.68.252
  • If you play on a European server: 159.153.72.252

As detailed here

420_Gopetoo's avatar
420_Gopetoo
10 years ago

Issues Logging on The Progenitor EU (so far): I am not able to make it to Server List when I Launch swtor.exe. If the game loads to Charecter Selection and I login, the game loads but with infinte "Connection Lost" indicator building up ms lag, going up to 200k before I close the game.

Spoiler
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>netstat -n -p tcp -b

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:2861         127.0.0.1:51568        ESTABLISHED
 Can not obtain ownership information
  TCP    127.0.0.1:50417        127.0.0.1:50418        ESTABLISHED
 [firefox.exe]
  TCP    127.0.0.1:50418        127.0.0.1:50417        ESTABLISHED
 [firefox.exe]
  TCP    127.0.0.1:51358        127.0.0.1:51578        TIME_WAIT
  TCP    127.0.0.1:51358        127.0.0.1:51582        TIME_WAIT
  TCP    127.0.0.1:51521        127.0.0.1:2862         TIME_WAIT
  TCP    127.0.0.1:51568        127.0.0.1:2861         ESTABLISHED
 [HD-Network.exe]
  TCP    127.0.0.1:51572        127.0.0.1:2861         TIME_WAIT
  TCP    127.0.0.1:51573        127.0.0.1:2862         TIME_WAIT
  TCP    127.0.0.1:51581        127.0.0.1:51358        TIME_WAIT
  TCP    127.0.0.1:51609        127.0.0.1:51610        TIME_WAIT
  TCP    192.168.0.102:49158    77.234.41.34:80        ESTABLISHED
 [AvastSvc.exe]
  TCP    192.168.0.102:50436    185.86.139.19:80       ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:50437    185.86.139.19:80       ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:50500    185.86.139.19:80       ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:50947    185.86.137.17:80       ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:51045    31.13.92.10:443        ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:51335    185.86.139.19:80       ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:51477    95.158.146.216:80      TIME_WAIT
  TCP    192.168.0.102:51478    95.158.146.216:80      TIME_WAIT
  TCP    192.168.0.102:51479    95.158.146.216:80      TIME_WAIT
  TCP    192.168.0.102:51480    95.158.146.216:80      TIME_WAIT
  TCP    192.168.0.102:51481    95.158.146.216:80      TIME_WAIT
  TCP    192.168.0.102:51511    74.125.136.141:443     TIME_WAIT
  TCP    192.168.0.102:51536    173.194.65.141:80      ESTABLISHED
 [HD-Network.exe]
  TCP    192.168.0.102:51541    74.125.136.141:443     TIME_WAIT
  TCP    192.168.0.102:51556    54.240.162.175:80      CLOSE_WAIT
 [HD-Network.exe]
  TCP    192.168.0.102:51560    74.125.136.188:5228    ESTABLISHED
 [HD-Network.exe]
  TCP    192.168.0.102:51567    216.58.208.110:443     ESTABLISHED
 [HD-Network.exe]
  TCP    192.168.0.102:51569    216.58.208.110:443     ESTABLISHED
 [HD-Network.exe]
  TCP    192.168.0.102:51570    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51571    74.125.136.141:443     TIME_WAIT
  TCP    192.168.0.102:51580    5.45.58.176:80         TIME_WAIT
  TCP    192.168.0.102:51584    5.45.58.174:80         TIME_WAIT
  TCP    192.168.0.102:51585    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51586    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51587    159.153.92.50:80       TIME_WAIT
  TCP    192.168.0.102:51588    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51589    74.125.136.121:80      TIME_WAIT
  TCP    192.168.0.102:51590    8.27.133.254:80        TIME_WAIT
  TCP    192.168.0.102:51591    5.45.58.175:80         TIME_WAIT
  TCP    192.168.0.102:51593    198.205.113.134:80     FIN_WAIT_2
 [System]
  TCP    192.168.0.102:51594    159.153.92.50:80       TIME_WAIT
  TCP    192.168.0.102:51595    159.153.92.50:80       TIME_WAIT
  TCP    192.168.0.102:51596    159.153.92.50:80       TIME_WAIT
  TCP    192.168.0.102:51600    198.205.113.134:80     TIME_WAIT
  TCP    192.168.0.102:51602    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51603    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51604    159.153.92.50:80       TIME_WAIT
  TCP    192.168.0.102:51605    5.45.58.176:80         TIME_WAIT
  TCP    192.168.0.102:51608    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51612    159.153.77.205:8995    TIME_WAIT
  TCP    192.168.0.102:51613    159.153.77.138:20065   ESTABLISHED
 [swtor.exe]
  TCP    192.168.0.102:51614    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51615    159.153.77.138:20066   ESTABLISHED
 [swtor.exe]
  TCP    192.168.0.102:51616    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51617    208.74.205.233:80      ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:51618    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51619    208.74.205.233:80      TIME_WAIT
  TCP    192.168.0.102:51620    208.74.205.233:80      ESTABLISHED
 [firefox.exe]
  TCP    192.168.0.102:51622    216.58.208.110:443     ESTABLISHED
 [HD-Network.exe]
  TCP    192.168.0.102:51623    216.58.209.74:443      CLOSE_WAIT
 [HD-Network.exe]
  TCP    192.168.0.102:51624    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51625    87.120.176.30:80       TIME_WAIT
  TCP    192.168.0.102:51626    87.120.176.30:80       ESTABLISHED
 [firefox.exe]

C:\Windows\system32>pathping -n159.153.77.138
A target name or address must be specified.

Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
                [-p period] [-q num_queries] [-w timeout]
                [-4] [-6] target_name

Options:
    -g host-list     Loose source route along host-list.
    -h maximum_hops  Maximum number of hops to search for target.
    -i address       Use the specified source address.
    -n               Do not resolve addresses to hostnames.
    -p period        Wait period milliseconds between pings.
    -q num_queries   Number of queries per hop.
    -w timeout       Wait timeout milliseconds for each reply.
    -4               Force using IPv4.
    -6               Force using IPv6.

C:\Windows\system32>pathping -n 159.153.77.138

Tracing route to 159.153.77.138 over a maximum of 30 hops

  0  192.168.0.102
  1  10.41.0.1
  2     *        *        *
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           192.168.0.102
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  10.41.0.1

Trace complete.

C:\Windows\system32>tracert 159.153.77.138

Tracing route to 159.153.77.138 over a maximum of 30 hops

  1    48 ms    49 ms    48 ms  10.41.0.1
  2     *        *        *     Request timed out.
  3    49 ms    49 ms    49 ms  97.129.158.95-rev.novatelbg.net [95.158.129.97]

  4    58 ms    58 ms    10 ms  145.236.236.110
  5    58 ms    10 ms    11 ms  145.236.236.166
  6    12 ms    11 ms    11 ms  254.128.158.95-rev.novatelbg.net [95.158.128.254
]
  7    57 ms    13 ms    10 ms  253.128.158.95-rev.novatelbg.net [95.158.128.253
]
  8    10 ms    14 ms    11 ms  sfia-b2-link.telia.net [80.239.135.185]
  9    31 ms    31 ms    31 ms  win-bb2-link.telia.net [213.155.132.184]
 10    50 ms    50 ms    49 ms  hbg-bb4-link.telia.net [62.115.136.26]
 11    62 ms    68 ms    62 ms  ldn-bb2-link.telia.net [62.115.142.117]
 12   127 ms    80 ms     *     dln-b1-link.telia.net [62.115.136.71]
 13    79 ms    80 ms    79 ms  bioware-ic-147166-dln-b3.c.telia.net [80.239.192
.78]
 14   127 ms    83 ms    80 ms  159.153.72.42
 15    79 ms   126 ms    80 ms  159.153.77.138

Trace complete.

C:\Windows\system32>
  • proxos666's avatar
    proxos666
    Hero+
    10 years ago

    @420_Gopetoo

    Your results look like a local issue

    if playing wireless try wired and see if it persists, both should be about 1ms

    Pathping - 1    1ms     0/ 100 =  0%     0/ 100 =  0%  10.41.0.1

    Tracert - 1    48 ms    49 ms    48 ms  10.41.0.1

About STAR WARS™: The Old Republic™

Check this forum for STAR WARS™: The Old Republic™ help, or to chat with other SWTOR players.18,808 PostsLatest Activity: 6 months ago