If you are having 90002/90001/Disconnects please REPLY HERE!

[iamSephiiroth]

I am currently experiencing this same issue right now and it started last Friday, may I know if you already fixed yours? btw, I do not want to use VPN because it is an additional expense for me.

Methods I used to fix:
1. reset router
2. reinstall the game
3. disable large send offload setting
4. flushdns
5. disable upnp usage
6. limit fps to below 120 fps
7. switching to googles DNS on windows

I do not know what to do anymore, is there anyone who can help us here?

[Bloodb]

17% Packet loss
The USA election
Covid-19
Businesses, churches, and schools using video streaming now

I live in the midwest, USA
Here's some pings to google:

Microsoft Windows [Version 10.0.18363.1139]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\brend>ping google.com -t

Pinging google.com [2607:f8b0:4000:812::200e] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=23ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=19ms
Reply from 2607:f8b0:4000:812::200e: time=20ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=35ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=20ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=19ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=38ms
Reply from 2607:f8b0:4000:812::200e: time=34ms
Reply from 2607:f8b0:4000:812::200e: time=16ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=36ms
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=21ms
Reply from 2607:f8b0:4000:812::200e: time=17ms

Ping statistics for 2607:f8b0:4000:812::200e:
Packets: Sent = 34, Received = 28, Lost = 6 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 38ms, Average = 21ms
Control-C
^C
C:\Users\brend>

17% packet loss! Take some deep breathes and go for a short walk. Try and be patient. Packet loss from user overload gets better and worse from time to time

One of the major causes of packet loss is link congestion. A simple analogy is rush hour traffic when there are more cars on the road than the road can sufficiently handle. Another analogy is a 4-lane road merging into 2 lanes. What happens is that there are more packets arriving on a link than that link is designed to handle.

Network congestion is a cause of packet loss that can affect all types of networks. When content arrives for a sustained period at a given router or network segment at a rate greater than it is possible to send through, there is no other option than to drop packets. If a single router or link is constraining the capacity of the complete travel path or of network travel in general, it is known as a bottleneck. In some cases, packets are intentionally dropped by routing routines, or through network dissuasion technique for operational management purposes.

[MelonTropic]

17% Packet loss
The USA election
Covid-19
Businesses, churches, and schools using video streaming now

I live in the midwest, USA
Here's some pings to google:



17% packet loss! Take some deep breathes and go for a short walk. Try and be patient. Packet loss from user overload gets better and worse from time to time

If it just was a temporary disturbance, i (and probably everyone else) wouldn't mind. But you can see a pattern. Everytime characters changing the area or gone through loading sequences, the game disconnect you from the server. This is occurring since patch 5.35. Before then everything went fine. Even on new Add-Ons etc. This is basicly not due to user overload. You can check the other pages on this thread, where people have evidence, that the connection dies next to the last hop reaching the Square Enix Gateway.

So you can't just walk along and give a general call-out for a certainly specific matter.

[Rinkotsumetai]

Still having 90002 error,
2 diff pcs, 2 diff accounts, same network, cable connection.

[sordidgeko]

Still having 90002 error,
2 diff pcs, 2 diff accounts, same network, cable connection.

2 diff pcs, 2 diff accounts, same network, cable connection
My wife is the only one that is having the issue whereas I have never had it.

[AlphaXXI]

Just in case anyone is interrested, in my case the issue was fixed (at least I think it was) by upgrading my network card. I considered the option after noticing the errors didn't happen with an ethernet cable, but this option isn't really practical for me so I looked into buying a better wifi card, and it seems like that worked.

[Squishy325]

I am alternating 90002/90006 issues as well.

[IllusiveMind]

I was able to resolve the 90002 error when connecting to the world server by adding the following tcp ports on my Cisco Firewall.
54992, 54993 and 54994
55006 to 55007
then,
55021 to 55040 (add the whole range, that's 55022... 55023... 55024 and so on)

[plasmacutter]

I've been getting 900002 at the rate of about 2 an hour since maintenance, making endgame unplayable.

EDIT2: Wiresharked this and am seeing RST packets coming from the server causing sudden terminations:

No. Time Source Destination Protocol Length Info
5509 132.877900 192.168.1.68 204.2.229.102 TCP 150 50557 → 55006 [PSH, ACK] Seq=2017 Ack=22273 Win=1025 Len=96
5510 132.888042 204.2.229.102 192.168.1.68 TCP 60 55006 → 50557 [RST] Seq=22273 Win=0 Len=0
5511 132.932779 192.168.1.68 204.2.229.102 TCP 54 50558 → 55006 [FIN, ACK] Seq=769 Ack=769 Win=1025 Len=0

[PinkPanda]

Constant 90002/90006 here aswell and have already opened all ports suggested/ran test/prayed to local eikons and nothing has helped. Ping test so no issues but something has happened since this update. Prior to this I had maybe 2 errors a month?