90002 Disconnect error

It has returned and reared its ugly head... AGAIN.

What do I need to do to fix it even though FFXIV is the ONLY thing I engage in that gets these constant disconnects.

These disconnects are bad enough that I lag out and get disconnected when trying to do dungeons, trials, raids or frontlines. It's also horrible when attempting to participate in any of the Moon events like Mech Ops, Red Alerts or CE's... basically any of the FATE events.

You'll need to provide a trace route.

If running windows:
Ping plotter has a free version that will show historical stats and a graphical view or open up command prompt and run tracert 204.2.29.241.

I recommend not listing the first couple of hops publicly in your trace route and only provide the full trace route to SE.

Having same issue this morning. No internet problems of any kind. No packet loss.

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 2 ms 4 ms 2 ms 192.168.68.1
2 5 ms 3 ms 3 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 5 ms 2 ms 3 ms 10.108.1.122
4 5 ms 3 ms 3 ms 2c.be.425e.riseb.net [66.94.190.44]
5 4 ms 3 ms 2 ms 26.be.425e.riseb.net [66.94.190.38]
6 3 ms 2 ms 3 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 * 3 ms 4 ms ae3.er1.phx4.us.zip.zayo.com [64.125.30.108]
8 * * * Request timed out.
9 5 ms 3 ms 3 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
10 5 ms 2 ms 3 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
11 36 ms 43 ms 38 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 48 ms 49 ms 49 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 50 ms 82 ms 49 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 50 ms 50 ms 50 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 47 ms 49 ms 47 ms 204.2.29.241

Trace complete.

Quote:

---

Originally Posted by Dharnyle

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 2 ms 4 ms 2 ms 192.168.68.1
2 5 ms 3 ms 3 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 5 ms 2 ms 3 ms 10.108.1.122
4 5 ms 3 ms 3 ms 2c.be.425e.riseb.net [66.94.190.44]
5 4 ms 3 ms 2 ms 26.be.425e.riseb.net [66.94.190.38]
6 3 ms 2 ms 3 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 * 3 ms 4 ms ae3.er1.phx4.us.zip.zayo.com [64.125.30.108]
8 * * * Request timed out.
9 5 ms 3 ms 3 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
10 5 ms 2 ms 3 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
11 36 ms 43 ms 38 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 48 ms 49 ms 49 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 50 ms 82 ms 49 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 50 ms 50 ms 50 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 47 ms 49 ms 47 ms 204.2.29.241

Trace complete.

---

Your hop 10
10 5 ms 2 ms 3 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]

is the NTT ALT-TX hard failover that I reported about here https://forum.square-enix.com/ffxiv/...P-NTT-...AGAIN

NTT sucks sorry, they are impacting a lot of player throughout the day.

Is there anything I can do?

Good morning! Thank you for posting in the Final Fantasy XIV Technical Support Forums.

I apologize for the delay in our response to your concern. We would like to recommend the following troubleshooting:

Open the control panel of the PC and go to ‘Network and Internet’. Once there select ‘Internet Options’
- Under the "General" tab, please delete ALL browser history.
- Under the "Security" tab, please move the slider to the lowest possible settings or no higher than "Medium"
- Under the "Privacy" tab, click “Advanced” and select ‘Accept’ under both First Party and Third Party Cookies.
- Under the "Advanced" tab, please make sure that "Allow software to run or install even if signature is invalid" is CHECKED.
- Make sure that all SSL and TLS (EXCEPT SSL 3.0) are CHECKED. [SSL 3.0 should be UNCHECKED]
- Hit "Apply" to save the settings, and then "OK, to close the Internet Options menu.
- Right-Click on the FFXIV launcher icon and select "Properties"
- Hit "Apply", then "OK" to save the changes.
- Please RESTART your PC now. Once your PC has been restarted, Right-Click the FFXIV launcher icon once more and select "Run as Administrator"

- Flush DNS: Within the "Command Prompt" of the device, please type the command "ipconfig /flushdns".
- Reset TCP/IP: Also within the Command Prompt, type the command "netsh int ip reset" and then restart the computer.


Lastly, we suggest power cycle the router by shutting it down and leaving the power supply unplugged for 5-10 minutes.


We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

I did all that and then did another trace and got almost the exact same numbers.

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.68.1
2 5 ms 2 ms 2 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 6 ms 2 ms 3 ms 10.108.1.122
4 5 ms 4 ms 3 ms 2c.be.425e.riseb.net [66.94.190.44]
5 6 ms 3 ms 3 ms 26.be.425e.riseb.net [66.94.190.38]
6 4 ms 3 ms 3 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 8 ms 3 ms 8 ms ae3.er1.phx4.us.zip.zayo.com [64.125.30.108]
8 * * * Request timed out.
9 30 ms 42 ms 12 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
10 5 ms 2 ms 2 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
11 38 ms 37 ms 38 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 57 ms 49 ms 49 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 49 ms 73 ms 53 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 49 ms 50 ms 49 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 49 ms 49 ms 49 ms 204.2.29.241

Trace complete.

I especially enjoy being selected as a pilot for a Mech Ops. Getting to the operation zone and then getting disconnected, losing the pilot license and the big bag. That's oh so much fun! It's amazing how I get to pay to play but can't actually play because of a persistent problem that is NOT on my end.

Good morning! Thank you for posting in the Final Fantasy XIV Technical Support Forums.

Please try the following troubleshooting suggestions as it may help resolve the issue:

Check to see if the following port ranges are opened on your router. You can contact your ISP and request they open them for you
▼TCP
54992 through 54994,
55006 through 55007,
55021 through 55040

- Delete the Patch Folder: Navigate to the folder using this path This PC > Docs > My Games> FFXIV ARR > Downloads > FFXIV patch (Use for either the version update error or cannot download patch files error)
Then either rename or remove the folder, the next time FINAL FANTASY XIV is launched, the client will repair the folder.
- Change local DNS: Please try changing the local DNS server to 8.8.8.8 and 8.8.4.4
- Delete local files with corrupted character data, please note this will not delete the associated characters.

If you have properly configured your router, and you are still experiencing these issues, our next suggestion is to bypass the router, and connect your console directly to your modem. Please ensure that you power down both the modem and the console for at least five minutes before attempting to connect to FINAL FANTASY XIV.

If you continue to receive these same errors when you are connected directly to the modem, then the problem lies with your ISP. We would recommend contacting them and advising them that one or more of the ports previously provided to you are being blocked or filtered, and that you do need access on these ports.

We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

Thank you for posting in the Final Fantasy XIV Technical Support Forums.

We apologize for any inconvenience experienced when trying to play Final Fantasy XIV. For us to better assist you, may you please respond with the following information:

Are you using a VPN?
Are you using a wired or wireless connection?
What Platform are you using? (Steam/Windows etc.)
Does the issue occur with one character or multiple characters?
How often would you say does the issue occur?

Internet Service Provider:
Region/State:

To confirm for troubleshooting, have you already reset your network equipment and/or contact your ISP?


Thank you once again for visiting the Final Fantasy XIV Technical Support Forums!

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.68.1
2 5 ms 3 ms 2 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 6 ms 3 ms 2 ms 10.108.1.122
4 9 ms 2 ms 2 ms txd-rtc-nfo-core-2-hu0-0-1-0.riseb.net [66.94.190.50]
5 6 ms 3 ms 2 ms 26.be.425e.riseb.net [66.94.190.38]
6 5 ms 3 ms 2 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 5 ms 2 ms 4 ms ae12.cs1.dfw2.us.zip.zayo.com [64.125.30.108]
8 8 ms * * ae8.cr1.dfw1.us.zip.zayo.com [64.125.27.13]
9 3 ms 3 ms 3 ms ae7.mcr1.dfw2.us.zip.zayo.com [64.125.24.143]
10 * * * Request timed out.
11 6 ms 4 ms 3 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
12 * 54 ms 53 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
13 37 ms 34 ms 34 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
14 53 ms 45 ms 45 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
15 46 ms 46 ms 47 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
16 45 ms 45 ms 49 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 47 ms 44 ms 44 ms 204.2.29.241

Trace complete.

Good morning! Thank you for posting in the Final Fantasy XIV Technical Support Forums.

We understand you may be experiencing disconnection issues while playing FINAL FANATSY XIV. Our team would like for you to check to see if the following port ranges are opened on your router.

If you have properly configured your router, and you are still experiencing these issues, our next suggestion is to bypass the router, and connect your console directly to your modem. Please ensure that you power down both the modem and the console for at least five minutes before attempting to connect to FINAL FANTASY XIV.

If you continue to receive these same errors when you are connected directly to the modem, we would recommend contacting your ISP and advising them that one or more of the ports previously provided to you are being blocked or filtered, and that you do need access on these ports.

Thank you for visiting the Final Fantasy XIV Technical Support Forums!

THREE times disconnected today with 90002 error. Twice within 10 - 15 seconds of logging in.

I've done everything you've asked me to do in this thread, multiple times.

It's not me. It's YOU.

I have ZERO issues with anything else.

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.68.1
2 4 ms 2 ms 2 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 5 ms 3 ms 3 ms 10.108.1.122
4 5 ms 3 ms 3 ms txd-rtc-nfo-core-2-hu0-0-1-0.riseb.net [66.94.190.50]
5 22 ms 3 ms 3 ms 26.be.425e.riseb.net [66.94.190.38]
6 4 ms 13 ms 3 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 6 ms 7 ms 9 ms ae12.cs1.dfw2.us.zip.zayo.com [64.125.30.108]
8 9 ms * * ae8.cr1.dfw1.us.zip.zayo.com [64.125.27.13]
9 4 ms 7 ms 4 ms ae7.mcr1.dfw2.us.zip.zayo.com [64.125.24.143]
10 * * * Request timed out.
11 26 ms 5 ms 4 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
12 5 ms 3 ms 3 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
13 38 ms 36 ms 36 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
14 84 ms 92 ms 83 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
15 93 ms 89 ms 90 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
16 89 ms 92 ms 89 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 81 ms 81 ms 79 ms 204.2.29.241

Trace complete.

Thank you for posting in the Final Fantasy XIV Technical Support Forums.

We apologize for any inconvenience experienced when trying to play Final Fantasy XIV. For us to better assist you, may you please respond with the following information:

Are you using a VPN?
Are you using a wired or wireless connection?
What Platform are you using? (Steam/Windows etc.)
Does the issue occur with one character or multiple characters?
How often would you say does the issue occur?

Internet Service Provider:
Region/State:

To confirm for troubleshooting, have you already reset your network equipment and/or contact your ISP?


Thank you once again for visiting the Final Fantasy XIV Technical Support Forums!

Quote:

---

Originally Posted by Dharnyle

I did all that and then did another trace and got almost the exact same numbers.

Tracing route to 204.2.29.241 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.68.1
2 5 ms 2 ms 2 ms 01.a0.d12c.cidr.airmail.net [209.44.160.1]
3 6 ms 2 ms 3 ms 10.108.1.122
4 5 ms 4 ms 3 ms 2c.be.425e.riseb.net [66.94.190.44]
5 6 ms 3 ms 3 ms 26.be.425e.riseb.net [66.94.190.38]
6 4 ms 3 ms 3 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
7 8 ms 3 ms 8 ms ae3.er1.phx4.us.zip.zayo.com [64.125.30.108]
8 * * * Request timed out.
9 30 ms 42 ms 12 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
10 5 ms 2 ms 2 ms ae-13.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.46]
11 38 ms 37 ms 38 ms ae-4.r26.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 57 ms 49 ms 49 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 49 ms 73 ms 53 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 49 ms 50 ms 49 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 49 ms 49 ms 49 ms 204.2.29.241

Trace complete.

---

Try WinMTR. It will run a tracert 1 time every second and record the results for you.

Is anyone who is having these problems also using Discord, that seems to be when i get the most trouble.

My constant disconnects in Dawn Trail zones is back.

I had fixed the issue by using a VPN and that worked for about a month. But this week when AWS and Azure went down, BOOM, no more being in DT zones for me.

Every other part of this game works perfectly. But as soon as I go into a DT zone, withing a couple minutes or LESS, DC with the 90002 error.

Good morning fellow adventurers and thank you all for posting in the Final Fantasy XIV Technical Support Forums.


I apologize for the delay in our response to your concern. If you are still experiencing frequent stutters or significant latencies while playing FINAL FANTASY XIV and you think it's due to packet loss, please submit your information using this form. Please submit a report through the 'Providing information on packet loss and lag' section at the bottom of the page. For instructions on how to perform a traceroute please visit the following Lodestone Announcement.




Thank you once again for visiting the Final Fantasy XIV Technical Support Forums!

i got this 15 times today

We're getting DDOSed again. Well NA is anyways.

12 times today i got find some 1 who can raid furnture in my new house beth mist 15 8 i need 5 thing raised

We're getting DDOSed like crazy for the past 3 days now. Well NA is. Can something please be done about this already?

On tuesday my fixed party attempted and got 90001 AS A WHOLE PARTY in Pilgrim's Traverse.
On the 3rd attempt we called it and decided to retry this evening.
This evening, we again convened and were disconnected 90001 on Stone 81 after 3 hours of progress through this deep dungeon.

Our save, representing 3 hours of our time, was voided.

All 3 of us.
At once.
THIS IS NOT OUR INTERNET WE'RE IN 3 SEPARATE GEOGRAPHIC LOCATIONS.

There needs to be a total overhaul of ddos protection for FFXIV.
I know of several "cancelled" websites whose lone proprietors do a better job handling ddos despite being denied service by literally everyone.

DDOSers need to get a life, and SE needs to do more to mitigate it.

Logged in to Dynamis, Seraph, got a couple of quests done and then hung on a quest and booted off. Tried to get back in and saw a queue of 222. This is not just DDoS, but a lot of accounts (bots) flooding the queues. SE needs to find out from where and what proxy services and just blanket ban. Sucks to be those that use proxy to mask their IPs, but that's just how it goes until they can find the accounts and permanently ban them. Also, the free trial thing needs to be temp disabled, because I believe that the bad actors are using that vector of attack, and paying customers should be your priority.

Lost another solo run on floor 71 due to these ddos attacks. last time i was on the final floors when it happened. they need to have some failsafe in place for dc's in deep dungeons if this keeps happening

Game is unplayable today. DDOS cutting connection every 20 mins this am (every less than 5 mins now) or so. It is especially bad for Pilgrim's traverse. Not an invididual problem: everyone getting DC’d. It’s happening since several days now and it’s getting worse. SE shoud take action and proper mitigation measures.

Getting insane now, took me 5 logins to administer my ten retainers, normally takes less than two minutes, now with the constant disconnects, ten to fifteen minutes.

Can nothing be done to stop whatever is happening, from happening. Need a connection to your service that works without disruption.

45 9002 grr

9 disconnects so far today I think. Kind of a nuisance for crafting.

I just got it and considering the queue to login went to 300+, I assume its not an individual issue and something else at a larger scale.

...really wish there was a way for US to find who's doing this...

Not sure tracing is going to work for random drops. Its just going to show success when its up. You would have to do continuous parallel trace routes to see where that one blip happened that dropped your connection. And even that may not show anything if the game server or routers at the end are dropping packets.

45 9002 grrrr

I wish we could get some information from SE besides the usual copy/paste notices in the news feed.

The fact that thos has been going on, nonstop, for a week straight suggests to me that the attackers intentions might be to destroy this mmo.

If the attacks never stop, and SE can't stop this, we could be looking at the end of this game in NA...

this is reminiscent of the eu and na ddos attacks of the september 2019 wow classic attacks , that guy ended up getting arrested though

Would it be possible for SE to set up their servers so that ONLY traceable connections are allowed?

We know that the DDoS attacker and proxies will use VPNs or some other service to avoid getting caught. Can SE set up their servers to simply not accept any connection that isn't traceable? O know this sounds "big brothery", but it would effectively make it impossible to launch a DDoS attack without getting caught. Might be the only way...