Error [2002] the lobby server connection has encountered an error

[ivy_anne]

Also in Denton... Also using Verizon. I called earlier today and they told me it was a problem on the games end, not theirs. Couldn't get any help from them at all.

Also had some trouble connecting to Steam too. Anyone heard anything new?

[Prymal_Darkstar]

I'm also having the same lobby server problem and am in the DFW Texas area using Verizon FIOS. However, I only have a problem logging into Excalibur. I can create a new character and log into most other servers. So I'm not sold on it being a Verizon issue. Also, my entire raid group tonite got booted and had trouble getting back in, and they are all over the US and 1 in Canada.

[yangusis]

I'm not North Texas or Verizon, AZ with Cox Communications.

And the insane ping spikes ensue. So it's a combination of 2002, 90k, and terrible ping when I'm able to connect.

[MewCat]

Dallas as well, can't connect.

I can also say the problem doesn't seem to be verizon (or their awful openwrt routers).

Here's the test:

1. Try to connect, examine connection, get the following:

Note: minimal packet loss, no issues save mysteriously can't get characters
2. This failed, let's try and log into a different DC, result is success, connecting to the server 199.91.189.74
3. Since this server is known to be good (disregarding any behind the scenes segmentation and access to server resources), let's add the following hostfile entry:

199.91.189.93 199.91.189.74

Note: this routes the first IP to the second
4. Attempt to log in to the original dc with the modification, result failure pointing at formerly succeeding IP


Conclusion:

Since we have an established connection transferring data in both cases with near identical throughput and one of them actually contacts the lobby server, we can make 3 assumptions:

1. That the TCP socket is created and that's it's exchanging data greater than a simple keepalive.
2. That the TCP connection is (or damn well better be) encrypted.
3. That VZ isn't dedicating resources to decrypting and analyzing the traffic of every call that goes through their routers.

Based on that reasoning, we can arrive at a reasonable conclusion:

There's either a downed server or a bad route (poisoned, lost, lb misonfigured etc) in the square DC in Montreal.

Edit: It is also possible that the information being streamed is causing redirection to an unavailable resource, or the resource is simply misconfigured and whichever service is powering this is throwing errors or returning invalid data. Once it hits the DC it's impossible to tell what precisely goes on without being inside of it, but we can in this case eliminate external factors.

More info:

Tracert ->
 12    52 ms     *       56 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] <- Level 3 router to montreal by way of dallas and chicago Dcs
 13    73 ms    73 ms    75 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] <- route to another host in same DC
 14    61 ms    58 ms    59 ms  192.34.76.10 <- internal entrypoint
 15    56 ms    56 ms    55 ms  199.91.189.242 <- internal redirect
 16    55 ms    56 ms    56 ms  199.91.189.93 <- final destination

 12    52 ms     *       56 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] <- Level 3 router to montreal by way of dallas and chicago Dcs
 13    73 ms    73 ms    75 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] <- route to another host in same DC
 14    61 ms    58 ms    59 ms  192.34.76.10 <- internal entrypoint
 15    56 ms    56 ms    55 ms  199.91.189.242 <- internal redirect
 16    55 ms    56 ms    56 ms  199.91.189.74 <- final destination

[punitenshu]

I'm also having the same lobby server problem and am in the DFW Texas area using Verizon FIOS. However, I only have a problem logging into Excalibur. I can create a new character and log into most other servers. So I'm not sold on it being a Verizon issue. Also, my entire raid group tonite got booted and had trouble getting back in, and they are all over the US and 1 in Canada.

SE acknowledged the other issue you're mentioning. I have yet to see anything regarding the lobby-specific issue that is 100% restricted to those in DFW on FIOS (judging from the people who've given their location in this thread). Are you able to log into other NA servers? JP works fine for me, just not NA.

Edit: Okay, it was 100% until that guy from AZ posted while I was writing =3 Although, that guy is 90king and can still get in sometimes so it's probably not the same problem as the one where our characters just don't load.

[Exavior]

Can't even log in. Keep getting 90000, 2002, or 6002.
Can't connect to lobby server or something like that.
Server: Excalibur

[ExtraStabby]

I'm in Dallas on Verizon FIOS. Same issue. Can't get in. 2002 error.

[ExiaQuanta]

Server just died a few minutes ago again LOl was greeted by our long lost buddy Queue of 27k pple >D

Data Center: Aether
Server : Coeurl

[Redbullmass]

Same on Sargatanas. 4 90k errors in a row now.

[punitenshu]

The Dallas folk with just the 2002 error can WTFast or Battleping around the problem if they are so inclined. I can't say for certain whether SE would frown on that, but they don't seem to have any problem with that software being discussed at least.

It seems like there are plenty of other issues at the moment, so not sure if it's worth the risk (if you are worried it's risky in the first place) though.