connection errors

[NaiaLalita]

Like Ostheim89, I was able to get a sprout alt logged in briefly and thought that meant the issue was resolved, but it's right back to 2002, 10105, and 90002 errors again after I went back to trying my main character.

Ran my own trace route, used the info provided in this lodestone post: https://na.finalfantasyxiv.com/lodes...a451d5a8daa66f
(this post shows the NA address as 204.2.29.112, with a note that it was updated April 3, 2023)

Tracing route to 204.2.29.122 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 9 ms 11 ms 67.59.237.89
4 11 ms 12 ms 18 ms opti37-8.nassau.cv.net [167.206.37.8]
5 14 ms 12 ms 11 ms 451be0fc.cst.lightpath.net [65.19.99.252]
6 11 ms 26 ms 12 ms 64.15.1.88
7 12 ms 12 ms 13 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 11 ms 13 ms 12 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
9 11 ms 13 ms 12 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
10 13 ms 14 ms 16 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 592 ms 20 ms 14 ms ae-16.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 34 ms 37 ms 37 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 34 ms 33 ms 32 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
14 * 81 ms 88 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
15 93 ms 82 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 84 ms 85 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 82 ms * * 204.2.29.241
18 81 ms 81 ms 81 ms 204.2.29.122

Trace complete.

Also ran the same as others in this thread, to 204.2.29.70:

Tracing route to 204.2.29.70 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 8 ms 9 ms 67.59.237.89
4 10 ms 10 ms 13 ms opti37-10.nassau.cv.net [167.206.37.10]
5 11 ms 13 ms 11 ms 451be0fe.cst.lightpath.net [65.19.99.254]
6 11 ms 11 ms 11 ms 64.15.1.88
7 11 ms 11 ms 12 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 11 ms 15 ms 11 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
9 14 ms 12 ms 12 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
10 11 ms 13 ms 14 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 15 ms 13 ms 13 ms ae-16.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 34 ms 43 ms 38 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 45 ms 35 ms 39 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
14 * * 80 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
15 83 ms 97 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 93 ms 89 ms 84 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * 84 ms 204.2.29.241
18 85 ms 87 ms 85 ms 204.2.29.70

Trace complete.

2:53 PM Eastern update: I WON THE LOG-IN GAMBLE. Just kept trying and eventually hit a stretch with no server disconnects I guess!
Sure hope there is some formal/official post sometime soon about this issue since it's been going on for over 10 hours by some reports!!

[DDRDiesel]

Reporting in that as of 2:30 PM EST, I'm able to get to the character selection screen but still error out after choosing a character to log in with. I also can't log into my main with the error message "Unavailable: Character is visiting on Dynamis data center". Can't change to Dynamis to log in on main either, get 2002 and kicked.

Does not appear resolved as of yet

[DDRDiesel]

FOLLOW-UP: I was able to finally get logged in and transfer my main back to Aether, then log in to Aether on my main and transfer between servers (Cactuar, Adam, etc, not datacenters!) with no issues.

As a test, I ran the following two commands from an elevated command prompt:
--
ipconfig /flushdns
netsh winsock reset
--

After a restart, I was able to switch to Dynamis and log into my main account. I logged out so I could transfer the character back to Aether, but got 2002'd when trying to log back into character select. I then ran the commands again and was able to get logged in and back to character select, and transferred main back to Aether. Afterwards, was able to log in on main and I'm stable now. Definitely not going to log out just in case

I understand this may not work for all players, but it's worth a shot. Hopefully this helps SE pinpoint the problem on their end as well

[Sensus]

Still a problem... @Square please fix your game.

[BettyHarlow]

Hello!! I've been playing for years but this is my first post here.

I wanted to add that I too am getting bounced from the title screen with 90002 or 2002 errors, and sometimes being bounced after selecting my main on Chrystal/Coeural then I make it to the loading screen, then I receive a 10105 error. I have been having these issues since about 4 am on the 14th. I'm on the east coast and I have Optimum internet. When I logged into the European data center, I was able to create a new character and then log in and play.

[lordpyro]

Had the same issue all day, made an alt on a japan server , got in first try. Skipped cutscens til I could log out. Got on with my main on aether first try after. Also an optimum customer near nyc

[justclay732]

recently picked the game back up, was able to play for about 3 or 4 hours over the weekend and haven't been able to play since, was literally able to login once. i have been back and forth looking for solutions, but still getting the 2002 and 90105 error codes.

Central Jersey on siren/cactuar servers.

[Sensus]

Still waiting for an SE tech. support team member to chime into this thread. Also an Optimum user on the East coast here and haven't been able to login properly for 2+ days now.

[fawlgaiy]

A few people seem to be repeating that the issue must be Optimum however as I mentioned earlier in the thread, I am Canadian where that ISP is not even an option. Pointing all fingers at one specific ISP does not help the issue and ultimately lets Square place all blame on the ISP.

[DDRDiesel]

A few people seem to be repeating that the issue must be Optimum however as I mentioned earlier in the thread, I am Canadian where that ISP is not even an option. Pointing all fingers at one specific ISP does not help the issue and ultimately lets Square place all blame on the ISP.

ThankYou.gif

I've been trying to say that several times. There are also issues as far down as SC and FL, where Optimum isn't available as an ISP. This is another NTT node issue and SE needs to work with their vendor to get it fixed