Jump to content
You need to play a total of 5 battles to post in this section.
ODYXXX

Conectivity problems

5 comments in this topic

Recommended Posts

Members
17 posts

I've been getting occasional periods where I get disconnected from the server.

So far I've been able to reconnect to finish the game, or just see my ship sink.

I did tracert on the server and got these results:

Normal:

Tracing route to dc11-sl-b21.fe.core.pw [162.216.229.21]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.10
  2     2 ms     1 ms     1 ms  192.168.2.1
  3    41 ms    44 ms    45 ms  10.11.2.217
  4    33 ms    20 ms    19 ms  10.178.206.82
  5    28 ms    38 ms    40 ms  10.178.206.83
  6    43 ms    39 ms    39 ms  tcore4-toronto21_2-4-0-1.net.bell.ca [64.230.104.250]
  7    52 ms    55 ms    52 ms  tcore4-chicagocp_hundredgige0-8-0-0.net.bell.ca [64.230.79.153]
  8    45 ms    45 ms    52 ms  bx6-chicagodt_0-7-0-0.net.bell.ca [64.230.79.87]
  9    43 ms    42 ms    33 ms  10gigabitethernet4-1.core1.chi1.he.net [206.223.119.37]
 10    54 ms    56 ms    69 ms  100ge4-2.core1.ash1.he.net [184.105.64.242]
 11    61 ms    63 ms    57 ms  eqix-dc3.gcore.lu [206.126.237.22]
 12    59 ms    56 ms    69 ms  dc3-a9006-edge-1-be20-2000.fe.core.pw [92.223.118.131]
 13    56 ms    55 ms    60 ms  dc11-n5596-fe-1-vl231.fe.core.pw [92.223.118.163]
 14    55 ms    52 ms    60 ms  dc11-sl-b21.fe.core.pw [162.216.229.21]

Trace complete.

Problem:

Tracing route to dc11-sl-b21.fe.core.pw [162.216.229.21]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  192.168.0.10
  2     1 ms     1 ms     1 ms  192.168.2.1
  3    30 ms    20 ms    19 ms  10.11.2.217
  4    37 ms    21 ms    21 ms  10.178.206.82
  5    31 ms    39 ms    20 ms  10.178.206.83
  6    36 ms    39 ms    40 ms  tcore3-toronto21_2-4-0-1.net.bell.ca [64.230.104.248]
  7    59 ms    57 ms    21 ms  tcore4-toronto01_0-1-0-0.net.bell.ca [64.230.50.234]
  8    32 ms    38 ms    22 ms  bx2-toronto01_et7-1-0.net.bell.ca [64.230.109.143]
  9    34 ms    47 ms    43 ms  ae55.bar2.Toronto1.Level3.net [4.28.138.45]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    40 ms    41 ms    40 ms  dc11-n5596-fe-1-vl231.fe.core.pw [92.223.118.163]
 13    38 ms    40 ms    37 ms  dc11-sl-b21.fe.core.pw [162.216.229.21]

Trace complete.

 

Any idea as to how to deal with this. I have to run the trace before I play now to make sure

I can stay connected.  It can begin while I'm playing so there is no sure way to play. I'm also

not sure how long it lasts, I usually give up for the day when it starts.

 

Share this post


Link to post
Share on other sites
Members
3,468 posts
6,161 battles

The times outs in the second image are not issues - hey are just not set to give priority to ping requests to prevent DDoS attacks.  What might be more telling is Pingplotter and if there is any packetloss that starts at a hop and then continues to the hops thereafter.

Is your PC hardwired (not using wireless)?  Are you connecting to NA server form North or South America?

Share this post


Link to post
Share on other sites
3,196
[GWG]
[GWG]
Alpha Tester, In AlfaTesters
15,581 posts
8,995 battles

The problem is happening before the packets are getting to WG so you will have to get on whoever owns them or have your ISP do that.

Share this post


Link to post
Share on other sites
Members
17 posts

 

10 hours ago, CylonRed said:

The times outs in the second image are not issues - hey are just not set to give priority to ping requests to prevent DDoS attacks.  What might be more telling is Pingplotter and if there is any packetloss that starts at a hop and then continues to the hops thereafter.

Is your PC hardwired (not using wireless)?  Are you connecting to NA server form North or South America?

I live near Toronto, Canada and my PC is hardwired. I see the reasoning in what you say but I only experience the disconnects when hops 10 and 11 aren't responding. I guess it could be unrelated.

Share this post


Link to post
Share on other sites
Members
3,468 posts
6,161 battles
1 hour ago, ODYXXX said:

I live near Toronto, Canada and my PC is hardwired. I see the reasoning in what you say but I only experience the disconnects when hops 10 and 11 aren't responding. I guess it could be unrelated.

That is why we need to see if there is packetloss.  If they are not responding - it could also be packetloss before those hops and it gets high enough by those hops that communication is dropped.  Though do note - the route for both images are different as well.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×