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

[KellyEwer]

Just a minor update. I got an update from QA and they kicked it back into support. They did say they would pass the message along but they couldn't make any promises. For my part, I promised to put in my best effort to be in touch with my ISP and see if we can re-route. However, the only two ways I can get in touch with my ISP is calling them or using the "Xfinity Assistant"... which isn't helpful to say the least. Trying to get in touch with someone online requires messenger from Facebook (???). I suppose I can try the Xfinity forums? Truly desperate times and measures.

Anyway, I'm still bewildered at why I'm the only one having issues when my SO isn't, but I can say that I'm still seeing substantial packet loss from the NTT servers as I track it. I'm still having this mental back-and-forth of "I'm watching up to 70% packet loss, it can't be on my end" and "my spouse and I are taking the same route, why is he doing fine while I'm constantly 90king, it must be on my end".

I don't know. If anyone can think of something on the client end I haven't tried and should look into, please by all means let me know... otherwise I'm kind of at a state where I'm fresh out of ideas.

EDIT: I just had another 90k2 error... tracking shows only 9% packet loss at the problem node. I don't even know anymore.

[strawhatpenguin]

Just wondering if anyone is also having the problem I am. I am constantly getting disconnects whenever I try to load into an area. For example. Just today I teleported in Lakeland to the Ostall Imperative. In the same area mind you and I still dc'd as soon as I got into the loading screen. Same thing when I try to load into an instance from duty finder right after my queue pops and I accept.

Also, if I have to use a VPN, can anyone give any recommendations for the issue?

[ShaneAlenko]

I posted in another thread about this issue, but it's been happening to me for about a week now. What's really strange is that I can let the game idle for hours (left it on overnight and didn't play for about 17 hours in total - just running borderless windowed while I had browsers open) in a city while people all around me run around and craft and whatnot, I get no disconnects. However, as soon as I start controlling my character and doing something as basic as running, the disconnects start happening.

[strawhatpenguin]

Even after getting a VPN I'm dc'ing. I'm out of ideas.

[ShaneAlenko]

I've also now been able to experience what other users have said here about people playing at the same time in the same household. I've now been disconnected on two different computers - mine and my husband's - while we were both playing at the same time. He was not disconnected while playing on either computer (and has not seen the same disconnect errors at all). There's no way this isn't something on SE's side.

[Gallows]

Im experiencing the same thing...

[KellyEwer]

Another update. I've also tried turning off Large Send Offload as per a recommendation by this guide: https://www.partitionwizard.com/part...xiv-90002.html

Sadly I've had two this morning. I've re-enabled that Mudfish VPN thing everyone in the community appears to swear by. I'll keep posted. I'm hopeful that, if nothing else, this thread and my work helps some poor sod in the future. I know I'd be utterly lost without reading years of forum threads and reddit posts.

[KellyEwer]

The VPN did not protect me from another 90k, sadly. However, it did provide useful information: that at the moment of disconnect, there was congestion that caused a sudden severe spike in packet loss. Something that may not interfere with something that buffers like YouTube, but would definitely impede something as sensitive as FF14. I have passed everything I have collected and done along to a CS agent with Xfinity. And... to my great shock, I found someone who not only read and analyzed, but acknowledged that I had already done everything they would have asked of me and more, and are now submitting a complaint on my behalf to the higher level teams.

Is that going to work? ... I don't know. But they've reassured me that they can tell there are no issues in my personal network or immediate vicinity, and are going to do what they can. Best believe I gave that CS staff a good review. Even if they end up unable to fix it, I'm simply overjoyed to get a human response.

In the meantime, I'll keep playing, keep enjoying the game as I can, and keep an eye out to see if things improve. That said, if by some chance someone in the future does stumble upon this thread having similar issues: I would recommend looking into the things the SE support email out, try their fixes, try the steps I have on this page and the last, before crying out to the ISP.

90k, especially 90002, is a generic disconnect error. It does not have only one solution. Therefore, even though this one ended up getting pushed to ISP level, one of the fixes I've tried might work for you.

[AvengerXZ]

The VPN did not protect me from another 90k, sadly. However, it did provide useful information: that at the moment of disconnect, there was congestion that caused a sudden severe spike in packet loss. Something that may not interfere with something that buffers like YouTube, but would definitely impede something as sensitive as FF14. I have passed everything I have collected and done along to a CS agent with Xfinity. And... to my great shock, I found someone who not only read and analyzed, but acknowledged that I had already done everything they would have asked of me and more, and are now submitting a complaint on my behalf to the higher level teams.

Is that going to work? ... I don't know. But they've reassured me that they can tell there are no issues in my personal network or immediate vicinity, and are going to do what they can. Best believe I gave that CS staff a good review. Even if they end up unable to fix it, I'm simply overjoyed to get a human response.

In the meantime, I'll keep playing, keep enjoying the game as I can, and keep an eye out to see if things improve. That said, if by some chance someone in the future does stumble upon this thread having similar issues: I would recommend looking into the things the SE support email out, try their fixes, try the steps I have on this page and the last, before crying out to the ISP.

90k, especially 90002, is a generic disconnect error. It does not have only one solution. Therefore, even though this one ended up getting pushed to ISP level, one of the fixes I've tried might work for you.

Can you give this a try? You don't need the specific brand's NIC, but basically go through your NIC driver advanced properties and change to match up with what it suggested here ( as basically its generic to be disabled for most gamers ). I have been having 90002 disconnects as well since 5.3 patch, today I actually didn't encountered any ( not sure if just lucky ) or if these NIC driver optimizations actually helped. I applied them this morning.

https://support.killernetworking.com...iver-settings/

I also have both Norton/Malwarebytes, Norton I reinstalled, Malwarebytes I added FF14 in the list of ignored applications, this was also done last night.

[KellyEwer]

Can you give this a try? You don't need the specific brand's NIC, but basically go through your NIC driver advanced properties and change to match up with what it suggested here ( as basically its generic to be disabled for most gamers ). I have been having 90002 disconnects as well since 5.3 patch, today I actually didn't encountered any ( not sure if just lucky ) or if these NIC driver optimizations actually helped. I applied them this morning.

https://support.killernetworking.com...iver-settings/

I also have both Norton/Malwarebytes, Norton I reinstalled, Malwarebytes I added FF14 in the list of ignored applications, this was also done last night.

Well, I set as many as I could, though some of them were incompatible (anything that said to set to 1024, for example, was impossible for my hardware). Might as well try it, because I'm still having issues, and complaining to the ISP didn't produce any tangible results.