Error code 2002 and 90000

[Alexika]

Raist, at first I was really thinking you may be right, but I don't think our ISP is to blame at all. I have done numerous long term pings now to my server and the problem does not arise until it leaves my ISPs network. In fact, the majority of my packet loss is actually once it hits SEs network. I am starting to believe that SE is not paying for enough bandwidth.

I thought I was seeing issues there, but it turns out it is just an anti-DDoS feature. Want the MTR I am running right now?

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|          Wireless_Broadband_Router.home -    1 | 1060 | 1058 |    0 |    4 |  473 |    2 |

|lo0-100.PRVDRI-VFTTP-306.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  428 |    6 |

|  T0-2-0-9.PRVDRI-LCR-22.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  422 |    8 |

|  xe-1-0-8-0.BOS-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |    6 |   24 |  428 |    7 |

|xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |   17 |   27 |  461 |   21 |

|                0.ae7.BR1.NYC1.ALTER.NET -    0 | 1068 | 1068 |   15 |   21 |  410 |   17 |

|                   No response from host -  100 |  213 |    0 |    0 |    0 |    0 |    0 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1053 | 1049 |   56 |   89 |  652 |  108 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1052 | 1048 |   56 |   89 |  620 |  270 |

|   ORMUCO-COMM.car2.Montreal2.Level3.net -    1 | 1041 | 1034 |   56 |   63 |  534 |   60 |

|                            192.34.76.10 -   13 |  719 |  632 |   68 |   78 |  534 |   72 |

|                          199.91.189.242 -   15 |  682 |  585 |    0 |   78 |  492 |   74 |

|                           199.91.189.33 -   17 |  645 |  539 |    0 |   81 |  503 |   75 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Raist]

I thought I was seeing issues there, but it turns out it is just an anti-DDoS feature. Want the MTR I am running right now?

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|          Wireless_Broadband_Router.home -    1 | 1060 | 1058 |    0 |    4 |  473 |    2 |

|lo0-100.PRVDRI-VFTTP-306.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  428 |    6 |

|  T0-2-0-9.PRVDRI-LCR-22.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  422 |    8 |

|  xe-1-0-8-0.BOS-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |    6 |   24 |  428 |    7 |

|xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |   17 |   27 |  461 |   21 |

|                0.ae7.BR1.NYC1.ALTER.NET -    0 | 1068 | 1068 |   15 |   21 |  410 |   17 |

|                   No response from host -  100 |  213 |    0 |    0 |    0 |    0 |    0 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1053 | 1049 |   56 |   89 |  652 |  108 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1052 | 1048 |   56 |   89 |  620 |  270 |

|   ORMUCO-COMM.car2.Montreal2.Level3.net -    1 | 1041 | 1034 |   56 |   63 |  534 |   60 |

|                            192.34.76.10 -   13 |  719 |  632 |   68 |   78 |  534 |   72 |

|                          199.91.189.242 -   15 |  682 |  585 |    0 |   78 |  492 |   74 |

|                           199.91.189.33 -   17 |  645 |  539 |    0 |   81 |  503 |   75 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

O M G.

It is staring us right in the face. Practically screaming at you.

Even if you want to write off the massive lag spike and lost packets on your local network (which you shouldn't--it is after all the first link in the chain and can affect everything after)...it looks like jitter may be on the high side with Verizon. Then it goes bonkers at Level3.

Based on the data you have presented, you appear to have networking issues that would have an impact on the most perfectly tuned server.

Even if the 600+ spikes were a once-only fluke spike at each of those hops, Level3 is running 56 to 108 with an average of 89 on one hop, and then 56 to 27-0 with an average of 89 at another. That is NOT acceptable. And imagine that... it is LEvel3's car2 hops in Montreal---notorious for being flakey as all get out. They get reported continuously all over the place for a variety of service issues.

Verizon is keeping you on that troubled route. They can take you off of it, just like Time Warner does for me on a regular basis... as demonstrated in the edit I made in my previous post.

[Alexika]

O M G.

It is staring us right in the face. Practically screaming at you.

Even if you want to write off the massive lag spike and lost packets on your local network (which you shouldn't--it is after all the first link in the chain and can affect everything after)...it looks like jitter may be on the high side with Verizon. Then it goes bonkers at Level3.

Based on the data you have presented, you appear to have networking issues that would have an impact on the most perfectly tuned server.

I fix cars not networks. You might as well speak in Egyptian, because that would mean more to me than anything you just said. Who has networking issues? What kind of issues? How did you determine that? What the heck is jitter? How do I get that fixed? What do I say to the monkey on the phone at Verizon to get them to stop blowing me off?

[Raist]

As noted in Blizzard's tracert guide that I keep referring people to, the response times should be tight. There should not be a massive variance between the times at the same hop. That is a big warning sign that something is going bad around that point of the route--could be signalling issue, or over-utilization...congestion is on the rise and their is potential for lost/delayed/retransmitted packets because of it. If you see intermittent * events at one hop, that means you lost packets. Again...often a sign of an overloaded network segment or other technical difficulties are negatively impacting the session. That is part of the problem with using some tools like WinMTR... you aren't able to get a better picture of just where the numbers actually stand. Tracert and ping are the more popular tools--simple, quick snapshots that allow you to better track the numbers to see just what/where the anomalies are rearing their ugly heads.

Basically, you should NOT see a swing of even 50% across the response times at one hop. Granted, depending on what the norm is you can still manage with a high variance, but if it jumps by 100% you are pretty much looking at trouble...and in your example you go beyond even that point.

Think of it like reading your O2 sensor data. If you see the downstream sensor bouncing all over the map from extremely low to extremely high in an erratic fashion...it sets off a red flag for you to take a closer look at your exhaust system and such.

Just for some recent examples, using tracert as described in that blogpost:

This is a trace from the other night when Time Warner, TATA, Level3, Verizon and others were reporting problems in NY/NJ, Atlanta, Ashburn, Nashville, Memphis, and Austin. Things were getting choppy in the game for me, but it was still playable because I am in SC and was only mildly affected by Ashburn, but it was frustrating when you are used to smooth gameplay--for others it was completely debilitating because they were getting a double/triple whammy along the way:

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    40 ms    13 ms    18 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    23 ms    31 ms    33 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    14 ms    15 ms    14 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    26 ms    26 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    33 ms    34 ms    90 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    31 ms    29 ms    62 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    53 ms    48 ms    51 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9   133 ms   155 ms    74 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    62 ms    62 ms    70 ms  64.86.85.1
 11   175 ms   147 ms   173 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    66 ms    73 ms    70 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    65 ms    75 ms    80 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    75 ms    76 ms    78 ms  66.198.96.50
 15    79 ms    82 ms    80 ms  192.34.76.2
 16    79 ms    78 ms    78 ms  199.91.189.234
 17    75 ms    79 ms    78 ms  199.91.189.74

Trace complete.

Now look at it tonight, where things are running considerably more smoothly (detected a slight stutter once in a while, but no rubberbanding or big skips):

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    29 ms    23 ms    24 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    25 ms    31 ms    31 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    12 ms    14 ms    15 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    26 ms    26 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    31 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    31 ms    30 ms    44 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    60 ms    55 ms    72 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    70 ms    74 ms    71 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    67 ms    69 ms    67 ms  64.86.85.1
 11    71 ms    78 ms    79 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    68 ms    75 ms    82 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    74 ms    75 ms    72 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    77 ms    73 ms    66 ms  66.198.96.50
 15    72 ms    69 ms    68 ms  192.34.76.2
 16    65 ms    70 ms    70 ms  199.91.189.234
 17    58 ms    60 ms    69 ms  199.91.189.74

Trace complete.

[Alexika]

They are sending me a new router for tomorrow, but I don't see how that will fix this.

[TheDuxun1977]

They are sending me a new router for tomorrow, but I don't see how that will fix this.

try doing a system restore to a point when you could log in hope that helps