Another 90002 error -_-

[SenahViqqoh]

So as the title says, I'm experiencing the 90002 errors and I don't understand why. I've googled the issue so many times and combed through countless threads of various forums and I haven't been able to find a fix.

This started on July 30th when I began playing that evening around 9pm EST or so. Ever since then I can't sign onto my server (Balmung) no matter what time of day or night it is, unless I'm lucky, in which case I can sign on for 5 to 6 minutes before getting booted off with a 90002 error.

I have been playing for the past month with no issues whatsoever, I have never experienced a crash from this game until the 30th, at which point the game suddenly became unplayable for me. There have been no changes to my modem/router and I'm able to play other games (WoW, Rift, Tera) with no issues whatsoever, it's just FFXIV.

I have reset my router to factory settings, I have disabled UPnP, set the NAT to open, forwarded ports on both UDP and TCP from 55296 to 55551, tried a system restore on my system, uninstalled and reinstalled FFXIV and nothing is working for me.

I'm using a Netgear router and Metrocast is the ISP. Any help at all to this would be greatly appreciated because I'm at my wits end and I don't know what to do anymore.

[Train88]

You may want to confirm this is not a router issue. Try using another router, if you can't try plugging the modem with your computer. If you can play like that for about 2-3 hours you may want to look into a new routers.

Routers are like power bars, they have a life cycle and need replacing about every 2 years. Old ones used to last about 5 years.

Hope this helps.

[SenahViqqoh]

Well that's the thing, I've also tried connecting directly to my modem and it's the same thing, (sorry for not mentioning that in my original post.) I get the same 90002 errors while directly connected to the modem. Also, if this was the router going bad, wouldn't the other games have similar problems as well? Or slower to no web browsing?

At this point my only hope is that maintenance would fix this issue but my expectations aren't very high for that. Short of that, I don't know.

[Raist]

Looks like for the most part Metrocast funnels things through GMP TV, and then that goes to either Cogent or NTT. Not the greatest peering arrangement if I'm looking at the same company.

Sounds like you may need to get your ISP involved to take a closer look at what is going on along your path to the servers. If you aren't comfortable doing the traces and such, they should be able to do some testing of their own if they have a valid address to use. Since you are on Aether, they should be able to use either the DNS name or the actual IP address for the lobby service:

neolobby02.ffxiv.com or 199.91.189.74

[SenahViqqoh]

If you aren't comfortable doing the traces and such, they should be able to do some testing of their own if they have a valid address to use. Since you are on Aether, they should be able to use either the DNS name or the actual IP address for the lobby service:

neolobby02.ffxiv.com or 199.91.189.74

Okay so umm, since networking is really not my thing, I don't really understand what you're saying here and I apologize for that. So basically, I should call my ISP and ask them to do a trace back to neolobby02.ffxiv.com or 199.91.189.74? Is that what you're saying? (I'm sorry for my ignorance, I just wanna make sure that when I get on the phone with them I have the right information.)

[SenahViqqoh]

So nevermind, after this morning's maintenance, I haven't had a single DC all day and everything works fine. A friend told me it's 'cause SE doesn't update it's code enough or something like that. I don't really understand the specifics, just that it was on SE's end, not mine.

Also, I noticed in a lot of these threads with these errors, it usually happens in July and February. I don't know, just food for thought I guess.

[Amiaze]

And now I'm getting them. Haven't gotten a single boot that wasn't client-related since starting Heavensward, but I'm getting constant 90002 errors in Seal Rock.

I'm on AT&T U-Verse.

The issue only occurred post-patch.

[SenahViqqoh]

And now I'm getting them. Haven't gotten a single boot that wasn't client-related since starting Heavensward, but I'm getting constant 90002 errors in Seal Rock.

I'm on AT&T U-Verse.

The issue only occurred post-patch.

Is it only in Seal Rock, also when did it start happening? After last maintenance or before?

[Amiaze]

Is it only in Seal Rock, also when did it start happening? After last maintenance or before?

So far I can only confirm that it's Seal Rock; I didn't run much else today. And it started happening after maintenance.

[SenahViqqoh]

That's really odd...I'm not much of a techie so I couldn't even guess why that would happen, but have you tried using a different pc or internet connection and seeing if it works?