Another week, same DC problems

valdisman

Posted last week about when X server NW starts, get disconnected and cannot force log in after speaking to General Helian.

Any fix for this coming soon or is it just going to be another [REMOVED] PWi have in game which they are going to ignore?​​

sylenthunder

1. Moved this to the right forum
2. Read the Sticky Threads. (That's two hyperlinks there.)
3. DO NOT circumvent the profanity filter.
4. After you've educated yourself and tried some troubleshooting that is noted in the Sticky Threads, post your results.

There's a HUGE chance that it's not the server having the issue, but that it's a problem with your path to the servers. It's remotely possible that it's on PWE's end, as I did discover an issue last week, but until you follow the steps listed above, all you're doing is talking ****. Fet your facts straight, then come here with the results and we can determine where the issue actually lies.​​

sylenthunder

Oh, and just cause, here's what I'm seeing this week...

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\SylenThunder>tracert pwieast3.perfectworld.com

Tracing route to pwieast3.perfectworld.com [198.49.243.17]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  homeportal [192.168.1.254]
  2    61 ms    20 ms    20 ms  76-250-208-3.lightspeed.livnmi.sbcglobal.net [76.250.208.3]
  3     *        *        *     Request timed out.
  4    21 ms    24 ms    23 ms  12.83.32.133
  5    29 ms    28 ms    30 ms  ggr4.cgcil.ip.att.net [12.122.133.33]
  6    29 ms    28 ms    28 ms  chi-b21-link.telia.net [213.248.87.253]
  7     *        *       57 ms  nyk-bb1-link.telia.net [62.115.116.32]
  8    63 ms    62 ms    65 ms  bost-b1-link.telia.net [62.115.115.204]
  9    50 ms    50 ms    51 ms  internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
 10    50 ms    51 ms    50 ms  border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
 11    50 ms    51 ms    51 ms  perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
 12    54 ms    53 ms    51 ms  198.49.243.250
 13   673 ms   805 ms   779 ms  198.49.243.253
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16    51 ms    51 ms    52 ms  198.49.243.17

Trace complete.

C:\Users\SylenThunder>

Hop 7 is dropping packets, so that's going to be a cause for disconnecting. This is on the internet, not your end or PWE's.
Hops 13-15 have a very high latency, so that's going to be a cause for lag. (high ping in-game and skill/effect delay) This is completely PWE, and an issue I pointed out last week.

Sadly though, until you bring something to the table.....​​

sylenthunder

Here we go with another update the the "mysterious" DisConnect issue.

We're getting a large number of DC's at the moment on the TT server. So I run a traceroute....

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\SylenThunder>tracert pwigc2.perfectworld.com

Tracing route to pwigc2.perfectworld.com [66.151.133.71]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  homeportal [192.168.1.254]
  2    31 ms    31 ms    29 ms  76-250-208-3.lightspeed.livnmi.sbcglobal.net [76.250.208.3]
  3     *        *        *     Request timed out.
  4    75 ms    60 ms    59 ms  12.83.32.173
  5   147 ms   133 ms   *  12.122.137.217
  6     *        *        *     Request timed out.
  7    89 ms   103 ms   112 ms  border2.t8-1-bbnet2.sje004.pnap.net [66.151.144.80]
  8   138 ms   165 ms   122 ms  perfectworld-10.border2.sje004.pnap.net [64.95.143.190]
  9   141 ms   103 ms   139 ms  66.151.133.71

Trace complete.

C:\Users\SylenThunder>

So, analyzing this..... Hop 3 is known to not return ping requests. That's a node in Ohio. It used to regularly be a real cause of issues for me, but since it's stopped returning ping requests, it's been a lot better. There is a little bit of a spike in ping after it, but not terrible.

Hop 5 though, there's definitely an issue going on there. Hard to say if 6 isn't returning pings, or if the packets are being dropped by 5.

It hits PWE at hop 8, but the numbers are moot at that point. Cause for disconnects is definitely dropped packets at hop 5.​​