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 type cmd.

(you will see cmd.exe show up before you hit ENTER).

Right Click the Application and select "Run as Admin"

 *What we are intending to do here is to identify which connections are being made and to where.

Spoiler

now please type

netstat -n -p tcp -b (Hit Enter)

Blah blah blah you will get

Active Connections

Proto Local Address         Foreign Address        State

[swtor.exe]

TCP   XXX.XXX.X.XX:49524     159.153.69.30:20060   ESTABLISHED

[swtor.exe]

TCP   XXX.XXX.X.XX:49577     54.87.184.213:443     ESTABLISHED

*the X's would have been my info but I have changed them to X's for privacy reasons, and please take note the IP addresses I have connected to 1 is the Harbringer server and I guess the other is the Login server?

Pingpath

*What we are intending to do here is identify which paths/routes we are taking to get to our desired location and if any of them are problematic

Spoiler
Now type

pathping -n 159.153.69.30 (ENTER)





(*obviously change the IP address to the one that you are connecting to without the port number aka :20060 for example)

You should get something like



Tracing route to 159.153.69.30 over a maximum of 30 hops



0

1 blah blah

2 blah blah

3 blah

4 so on

5 & so on



Computing statistics for 300 seconds...

           Source to Here   This Node/Link

Hop RTT   Lost/Sent = Pct Lost/Sent = Pct Address



Blah blah blah πr² is the key blah blah



This will show if there are any Packet Losses.

 

Tracert 

Finally type

*What we are intending to do here is identify which paths/routes we are taking to get to our desired location

 
Spoiler
tracert 159.153.69.30

(*obviously change the IP address to the one that you are connecting to without the port number aka :20060 for example)

Tracing route to 159.153.69.30 over a maximum of 30 hops

1   blah blah blah.

Now please Right click the Blue Bar at the top of the Window and Select

Edit > Select All>

Right click again

Edit Copy.

*Come back to this post and replay, please throw all the technical jargon into a Spoiler please so only those that wish to see it will

 

If you didn't know before CNTRL V is Paste

Hope it helps

Speedtest.net

*This will tell us how much actual useable Bandwidth we have available at our selected destinations 

Spoiler

** also if you could be so kind as to go [URL="www.speedtest.net"]here[/URL] and run a test to the appropriate server please,

*I play on Harbringer which the servers are located in San Jose,CA which is Just South of San Francisco

(***** Grab the Green Square on your Screen and move it to the appropriate location "159.153.69.30 " is San Jose)

yes Jesus Geography lessons in play when all you want to do is play a game. click share Result and include link in post please.

http://www.speedtest.net/result/4721039811.png (SoftLayer Technologies server Tested)

If you play on an East Coast server test to the New York area should be fine (159.153.92.28)

If you play on a West Coast server test to San Jose, CA (Just south of San Francisco (159.153.68.252)

If you play on a European server Test to Dublin, Ireland (159.153.72.252)



(*not sure of exact locations but these locations will get you pretty damn close.)

"The Green Square is movable, so is the zoom in and out bar on the left to help you navigate to find the correct servers to test to".



"I should also point out that -

             a) while your 'download' test is happening you will see a small green 'graph' happening below the current download results you want this graph to be as solid a curve as possible, deep and sharp spikes tend to be bad.

           

             b) You are ideally wanting a range of ~4Mbps Down and ~1Mbps up per person in your house currently online playing swtor for seamless game play; anything under that will be marginally noticeable in larger raids and group environments."

PingPlotter.

For those that are not so good with the CMD; here is a nice small program that I have used for quite sometime that allows you to visually see many of the things previously discussed and is very easy to use in conjunction to the information provided above.

https://www.pingplotter.com/

**"Grr I totally Goofed this post now trying to understand "Insert Code".. Sorry will get better could not find a way to remove my silliness.

  • 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

51 Replies

  • ron_harmeling's avatar
    ron_harmeling
    10 years ago

    OK, this is nice in theory, but tells ou if you are able to join the destination server or not.

    This does NOT, and I mean NOT, tell you anything about where the bottleneck/laggy bit, etc is located, unless you get huge ping spikes after the 3rd or 4th hop.

    If your ping and debit is good from a Dublin, Ireland server, and SWTOR has ping spikes etc, does that mean the SWTOR server has issues ? Maybe. But not necessarily. May also be the login server, the actual game server cluster, the connection to the data center, hell, even traffic control by a firewall.

    Traceroutes only tel you the route which has been taken to reach the server. As long as you reach it with significantly lower values then the server's values, fine.

    Pathping is a viable test, BUT : computing the data you're treating when playing a game do not occur when executing a simple pathping. It just shows you if there is packet loss, but .... Who is at fault ? That is something you won't be able to determine with this test.

    And above all :

    These are momentary values. They may be completely different 3 seconds later. As  they sometimes do in gameplay.

    You can't make any solid conclusions based on this testing method.

  • DBWoodynz's avatar
    DBWoodynz
    10 years ago

    I understand and accept the premise of what you are saying; that said I labeled it as guide to identify network issues.

    Perfect world scenario it is extremely difficult  to do just one thing and 10 seconds later have a 'boom that is the problem' styled answer, but what these tools do is allow folks to gather more and more information.

    If things start to turn ugly at hop 3 in a 30 hop chain then it would be fair to say well hop 30 had nothing to do with hop 3.

    The internet works (Broad Layman Terms) where everyone's ISP's provide them with their own preferred 'road maps' to reach destinations and just like travelling using busses, trains and planes everyone will have similar but different experiences depending on what they choose to use and pay for.

    Somedays things can go wrong it is just one of those things, but what I am hoping to provide is basic information so that anyone can come back with the information that they have gained from running these tests and have some sense of clarity as to where they could look next, or even have a conversation with their ISP with factual information as to what they are seeing.

    It is completely possible to have a conversation with a 'Level 3' ISP technician with this information and say things like "hop 8 of 30 is routed to IP address 202.687.1.95 (*example) and things for me get real ugly; any chance you could provide me with an alternative route?" and they will do their best to assist/help.

    That said in the past I have been with an ISP where they had a super cheap deal with all the service providers and stuffed me into a completely useless plan, where as when I came home from work like everyone else and wanted to play a game I couldn't as my speeds where as slow as Dial-up... my neighbor was unaffected.

    That is an example where these tools allowed me get an idea of what was going on and I sub-sequentially swapped ISP's.

  • ron_harmeling's avatar
    ron_harmeling
    10 years ago

    Point taken, this is also correct.

    However, better have a good 3rd level tech at your ISP to diagnose these issues, usually you say "hop n°x, IP xxx.xxx.xxx.xxx gives a huge spike in latency", most of the time you lost them 🙂

  • 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>
  • karlwaite's avatar
    karlwaite
    10 years ago

    I'm at 50ms or over I did a ping and all came in under 32.1ms I'm on red eclips and live in north east of uk I'm a i5 3570k, 660oc gigabyte, 8gb 2100 rijaws, ssd and asrock pro3 gen 3 board and virgin media 60 mb broad band

  • 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

  • Anonymous's avatar
    Anonymous
    10 years ago
    Spoiler

    H:\WINDOWS\system32>netstat -n -p tcp -b

    Active Connections

    Proto Local Address Foreign Address State
    TCP 127.0.0.1:57967 127.0.0.1:57968 TIME_WAIT
    TCP 127.0.0.1:57970 127.0.0.1:57971 TIME_WAIT
    TCP 127.0.0.1:57976 127.0.0.1:57977 TIME_WAIT
    TCP 192.168.0.104:54662 74.125.136.188:5228 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:54666 157.55.236.122:443 ESTABLISHED
    [Explorer.EXE]
    TCP 192.168.0.104:54774 108.168.151.6:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56241 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56513 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56596 82.77.159.242:443 TIME_WAIT
    TCP 192.168.0.104:57865 95.131.122.232:443 TIME_WAIT
    TCP 192.168.0.104:57874 72.30.196.161:443 TIME_WAIT
    TCP 192.168.0.104:57880 66.196.116.112:443 TIME_WAIT
    TCP 192.168.0.104:57915 216.58.209.194:443 TIME_WAIT
    TCP 192.168.0.104:57917 82.77.159.118:443 TIME_WAIT
    TCP 192.168.0.104:57923 82.77.159.104:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:57962 159.153.77.143:20077 TIME_WAIT
    TCP 192.168.0.104:57963 159.153.77.143:20078 TIME_WAIT
    TCP 192.168.0.104:57973 159.153.77.205:8995 TIME_WAIT
    TCP 192.168.0.104:57974 159.153.77.195:20063 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57975 159.153.77.195:20064 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57981 193.226.178.214:443 ESTABLISHED
    [chrome.exe]

    H:\WINDOWS\system32>netstat -n -p tcp -b

    Active Connections

    Proto Local Address Foreign Address State
    TCP 127.0.0.1:57967 127.0.0.1:57968 TIME_WAIT
    TCP 127.0.0.1:57970 127.0.0.1:57971 TIME_WAIT
    TCP 127.0.0.1:57976 127.0.0.1:57977 TIME_WAIT
    TCP 192.168.0.104:54662 74.125.136.188:5228 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:54666 157.55.236.122:443 ESTABLISHED
    [Explorer.EXE]
    TCP 192.168.0.104:54774 108.168.151.6:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56241 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56513 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56596 82.77.159.242:443 TIME_WAIT
    TCP 192.168.0.104:57865 95.131.122.232:443 TIME_WAIT
    TCP 192.168.0.104:57874 72.30.196.161:443 TIME_WAIT
    TCP 192.168.0.104:57880 66.196.116.112:443 TIME_WAIT
    TCP 192.168.0.104:57915 216.58.209.194:443 TIME_WAIT
    TCP 192.168.0.104:57917 82.77.159.118:443 TIME_WAIT
    TCP 192.168.0.104:57923 82.77.159.104:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:57962 159.153.77.143:20077 TIME_WAIT
    TCP 192.168.0.104:57963 159.153.77.143:20078 TIME_WAIT
    TCP 192.168.0.104:57973 159.153.77.205:8995 TIME_WAIT
    TCP 192.168.0.104:57974 159.153.77.195:20063 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57975 159.153.77.195:20064 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57981 193.226.178.214:443 ESTABLISHED
    [chrome.exe]

    H:\WINDOWS\system32>netstat -n -p tcp -b

    Active Connections

    Proto Local Address Foreign Address State
    TCP 127.0.0.1:57967 127.0.0.1:57968 TIME_WAIT
    TCP 127.0.0.1:57970 127.0.0.1:57971 TIME_WAIT
    TCP 127.0.0.1:57976 127.0.0.1:57977 TIME_WAIT
    TCP 192.168.0.104:54662 74.125.136.188:5228 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:54666 157.55.236.122:443 ESTABLISHED
    [Explorer.EXE]
    TCP 192.168.0.104:54774 108.168.151.6:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56241 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56513 193.226.178.214:80 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:56596 82.77.159.242:443 TIME_WAIT
    TCP 192.168.0.104:57865 95.131.122.232:443 TIME_WAIT
    TCP 192.168.0.104:57874 72.30.196.161:443 TIME_WAIT
    TCP 192.168.0.104:57880 66.196.116.112:443 TIME_WAIT
    TCP 192.168.0.104:57915 216.58.209.194:443 TIME_WAIT
    TCP 192.168.0.104:57917 82.77.159.118:443 TIME_WAIT
    TCP 192.168.0.104:57923 82.77.159.104:443 ESTABLISHED
    [chrome.exe]
    TCP 192.168.0.104:57962 159.153.77.143:20077 TIME_WAIT
    TCP 192.168.0.104:57963 159.153.77.143:20078 TIME_WAIT
    TCP 192.168.0.104:57973 159.153.77.205:8995 TIME_WAIT
    TCP 192.168.0.104:57974 159.153.77.195:20063 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57975 159.153.77.195:20064 ESTABLISHED
    [swtor.exe]
    TCP 192.168.0.104:57981 193.226.178.214:443 ESTABLISHED
    [chrome.exe]

    H:\WINDOWS\system32>-pathping 193.226.178.214
    '-pathping' is not recognized as an internal or external command,
    operable program or batch file.

    H:\WINDOWS\system32>pathping -n 193.226.178.214

    Tracing route to 193.226.178.214 over a maximum of 30 hops

    0 192.168.0.104
    1 192.168.0.1
    2 10.0.0.1
    3 * * *
    Computing statistics for 50 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 192.168.0.104
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    100/ 100 =100% |
    2 --- 100/ 100 =100% 0/ 100 = 0% 10.0.0.1

    Trace complete.

    H:\WINDOWS\system32>pathping -n 159.153.77.195

    Tracing route to 159.153.77.195 over a maximum of 30 hops

    0 192.168.0.104
    1 192.168.0.1
    2 10.0.0.1
    3 * * *
    Computing statistics for 50 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 192.168.0.104
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    100/ 100 =100% |
    2 --- 100/ 100 =100% 0/ 100 = 0% 10.0.0.1

    Trace complete.

    H:\WINDOWS\system32>tracert 193.226.178.214

    Tracing route to 193.226.178.214 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192-168-0-1.rdsnet.ro [192.168.0.1]
    2 2 ms 1 ms 1 ms 10.0.0.1
    3 * * * Request timed out.
    4 5 ms 5 ms 5 ms xr02.bucuresti.rdsnet.ro [213.154.101.219]
    5 6 ms 5 ms 5 ms 81.196.193.198
    6 6 ms 5 ms 6 ms r02-as0-0.ard2.ro.gtsce.net [85.9.9.17]
    7 5 ms 5 ms 6 ms r11-Ge1-11.buh7.ro.gtsce.net [85.9.9.30]
    8 6 ms 5 ms 5 ms 193.226.178.214

    Trace complete.

    H:\WINDOWS\system32>

    I keep getting disconnected from the game, I've tried a lot of stuff from the forums, nothing seems to help, I've bought the CE for SWTOR, and even played a fair bit at launch and a bit after. I would like to try the new content and subscribe, but I have to get the game to work first, please help. How can I maintain a steady connection?

    I would like to mention that I have a roommate who has a separate PC, but uses the same connection to the internet (we are both using wired connections to the same router). He doesn't get disconnected from the game, but I do. 

    After I connect to the server and begin playing with my character I get disconnected after a few minutes. It seems to get me disconnected faster in the evening and less fast in the morning, but still at most I can play around 5-10 mins before getting DC'ed. I am running windows 10, my drivers are up to date. I've played other games and MMOs and none have this issue. Please Help.

    Kind Regards,

    Ace

  • DBWoodynz's avatar
    DBWoodynz
    10 years ago

    @Ace_Hammerheart

    Morning, nice work on looking for this stuff...

    you did notice that hop 1 192.168.0.1 has 100% packet loss yes?

     Odds are your firewall settings are going Nom Nom Nom on your game signal like the cookie monster with chocolate chip..

    Jump into your Router and see if you can loosen up it's death grip on your connection; don't forget Windows has it's own firewall also.

    *incase you have not seen http://answers.ea.com/t5/STAR-WARS-The-Old-Republic/Guide-quot-How-to-install-Swtor-Correctly-and-address-Windows-10/td-p/4851036

    *Don't forget the Speedtest.net part of those tests, lots of great information to be found with that.

    With regards to testing your individual ports to save you some time...

    This is what you want open....
    http://www.swtor.com/support/helpcenter/2010

    This will walk you through step by step.
    http://portforward.com/

    http://portforward.com/help/portcheck.htm
    *This is the tool of tools, checks with ease and clarity; I find putting on socks harder then this.

  • Anonymous's avatar
    Anonymous
    10 years ago

    @DBWoodynz

    Hello, thanks for helping out. 

    Yes of course I noticed the packet loss, I've got no clue what to do about it. My roommate uses the same connection and plays just fine.

    I've configured the firewall as per the instructions, but I'm pretty sure it is not the issue, since I've tried to run the game with firewall turned OFF, it would impede the connection if it was turned off, would it? Same disconnections with firewall OFF.

    I've tried to port forward before, I've repeated the procedure now with some help from searching the internet. This is where I have an issue, but again if my roommate is playing connected to the same router I don't think this is causing any problem. I've added a screenshot below to let you see if it was done right.

    Port Forwarding Screenshot

    I've done speedtests to Dublin since I am from Europe and that's where the servers are AFAIK. It was over 90MB for both download and upload.

    Speedtest result

    BTW I want to thank you @DBWoodynz and @proxos666 you guys are the first humans who helped me in any way, I've been trying to get this thing to work for a very very long time.

    All the best,

    Ace Hammerheart

About STAR WARS™: The Old Republic™

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