Packetloss Problem

[ocb]

Hello guys, im pretty new in tw but i cant actually play .

My PLOSS is at 20.0% when i log!!

Everything closed, not downloading, and using desktop :/

i just did a trace and here r the results :

Tracing Zone: SSCU Trench Wars IP Address: 66.36.241.110

H

op IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 192.168.0.1     <unknown>                           0.0      0    0    0
  2 10.12.82.1      <unknown>                           5.5      0    0   10
  3 190.196.63.126  <unknown>                           5.5      0   10   70
  4 190.196.125.54  <unknown>                           0.0      0   10   10
  5 190.196.125.113 <unknown>                          94.4      0    0    0
  6 64.208.26.9     GigabitEthernet1-2.ar2.SCL1.gblx    0.0      0   30  140
  7 209.160.62.150  ge11-2.core2.dca3.hopone.net        0.0    140  140  140
  8 64.208.26.9     GigabitEthernet1-2.ar2.SCL1.gblx    5.5      0   30  140
  9 209.160.62.142  ge6-1.core1.dca2.hopone.net        94.4    140  140  140
 10 66.36.224.244   vl3.msfc1.distb1.dca2.hopone.net   94.4    140  140  140
 11 66.36.241.110   sls-cb9p7.dca2.superb.net           5.8    140  140  150

Cycles: 17

It even goes higher if i wait more. My router is a "planet" wrt-414 and im only computer plugged.

PLZ HELP ME!!

[roxxkatt]

hopone.net

theres your problem

[kthx]

hopone's packetloss is a fake packetloss, it doesn't mean you actually have it because it shows up in the trace.

What kind of connection do you have, do you have wireless zero turned off, how well maintained is your comp, where do you live, all important questions.

[ocb]

What kind of connection do you have, do you have wireless zero turned off, how well maintained is your comp, where do you live, all important questions.

Well i have a 3m connection, i dont know what is that wireless zero, ya my comp works fine and its not that coz i have other computer connected and has the same problem, i live in Chile southamerica but i guess thats not a problem coz i got some other friends who play w/o problems.

Someone told me something about getting in the router and close some ports but i dont know what he ment.

[M_M God]

Make sure your router doesn't block the ports Continuum is using. If that's the case, lookup what ports Continuum uses and go into your firewall configuration (192.168.1.1) and make sure that port is allowed (UDP/TCP). After that, check if your port if properly forwarded with http://portforward.com/. And make sure if you have a firewall that you allow Continuum as well.

If that's not your problem, then post it here again..and we'll try to solve it again :P

[Doc Flabby]

These two routers look like they might be causing your problem, are you able to compare your trace with your friends (if they can play fine, it should make where the problem is more clear).

2 10.12.82.1      <unknown>                           5.5      0    0   10
3 190.196.63.126  <unknown>                           5.5      0   10   70

[Dutch_]

Doc flabby got it right. Since ure local friends can play without these problems, its most likely that u have a local problem. This also shows in ure route:

2 10.12.82.1 <unknown> 5.5 0 0 10
3 190.196.63.126 <unknown> 5.5 0 10 70

Here's what u do:

1. Get a traceroute with more then 17 cycles (cuz its better).
2. Get a traceroute from one of ure friends that does not have lag problems.
3. Dont call, rather email the traceroutes to ure internetprovider explaining ure problem. They "should help you".

[Darkmoor]

Do at least 100 cycles and consider using the Windows pathping utility (Command Prompt -> pathping 66.36.241.110), it outputs the results in an easier to read/understand format.

As an example here is mine:

C:\Windows\system32>pathping 66.36.241.110

Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]
over a maximum of 30 hops:
  0  ares [192.168.0.102]
  1  hermes [192.168.0.1]
  2  riirki1.fi.elisa.net [88.114.168.1]
  3  10-1-1.hyvhyv1.fi.elisa.net [139.97.9.157]
  4  ae3.helpa-p2.fi.elisa.net [139.97.9.153]
  5  ae11.helpa-p1.fi.elisa.net [139.97.21.78]
  6  ae2.heltli-gw1.fi.elisa.net [139.97.6.246]
  7  ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49]
  8  so2-3-0-0.bbr1.nyc1.us.eunetip.net [213.192.191.174]
  9  nyc1.ge11-2.core2.dca2.hopone.net [66.36.224.209]
 10  vl2.msfc1.distb2.dca2.hopone.net [66.36.224.229]
 11  sls-cb9p7.dca2.superb.net [66.36.241.110]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ares [192.168.0.102]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  hermes [192.168.0.1]
                                0/ 100 =  0%   |
  2  ---     100/ 100 =100%   100/ 100 =100%  riirki1.fi.elisa.net [88.114.168.1]
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  10-1-1.hyvhyv1.fi.elisa.net [139.97.9.157]
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  ae3.helpa-p2.fi.elisa.net [139.97.9.153]
                                0/ 100 =  0%   |
  5   10ms     0/ 100 =  0%     0/ 100 =  0%  ae11.helpa-p1.fi.elisa.net [139.97.21.78]
                                0/ 100 =  0%   |
  6    9ms     0/ 100 =  0%     0/ 100 =  0%  ae2.heltli-gw1.fi.elisa.net [139.97.6.246]
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49]
                                0/ 100 =  0%   |
  8  116ms     0/ 100 =  0%     0/ 100 =  0%  so2-3-0-0.bbr1.nyc1.us.eunetip.net [213.192.191.174]
                                1/ 100 =  1%   |
  9  ---     100/ 100 =100%    99/ 100 = 99%  nyc1.ge11-2.core2.dca2.hopone.net[66.36.224.209]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%    99/ 100 = 99%  vl2.msfc1.distb2.dca2.hopone.net [66.36.224.229]
                                0/ 100 =  0%   |
 11  121ms     1/ 100 =  1%     0/ 100 =  0%  sls-cb9p7.dca2.superb.net [66.36.241.110]

Trace complete.

The only relevant part is highlighted, which shows that only 1 packet of 100 got lost in transit to the end node (TW). The rest is irrelevant in this case. Unfortunately people usually misinterpret trace results.

Also port forwarding has nothing to do with this problem.

[Turban]

Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]

over a maximum of 30 hops:



  1     1 ms     1 ms    <1 ms  buffalo.setup [192.168.11.1] 
  2     1 ms     1 ms     1 ms  192.168.254.254 
  3    73 ms    75 ms    77 ms  heltli1.fi.elisa.net [88.112.0.1] 
  4    94 ms   102 ms   121 ms  xe3-1-0.heltli-p2.fi.elisa.net [139.97.6.221] 
  5   111 ms   117 ms   155 ms  ae11.heltli-p1.fi.elisa.net [139.97.21.90] 
  6    15 ms    10 ms    18 ms  ae1.heltli-gw1.fi.elisa.net [139.97.6.238] 
  7    14 ms     *        5 ms  ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49] 
  8   130 ms   114 ms   134 ms  so2-3-0-0.bbr1.nyc1.us.eunetip.net [213.192.191.174] 
  9   772 ms   786 ms   788 ms  nyc1.ge11-2.core2.dca2.hopone.net [66.36.224.209] 
 10   119 ms   119 ms   120 ms  vl2.msfc1.distb2.dca2.hopone.net [66.36.224.229] 
 11   120 ms   120 ms   120 ms  sls-cb9p7.dca2.superb.net [66.36.241.110] 



Trace complete.

So what you are saying is that even though #9 seems to be lagging (a lot), for a period of two hours (everyday), it is not the source of the problem?

The problem is not just in Finland. A lot of players from UK, Netherlands, Sweden and Norway have this problem, not to mention some (of the few) players in Lithuanua.

HopOne phailz. :fear:

[Darkmoor]

So what you are saying is that even though #9 seems to be lagging (a lot), for a period of two hours (everyday), it is not the source of the problem?

No, I was not discussing the latency issues that some European users experience, that is an entirely different matter...

[ocb]

Problem Solved Just changed moden and lag gone

ty guys for ur help, i really apreciate it. see u in game