Frequent 90002 Error

[NocX7]

I have forwarded all the needed ports,allowed the game through the firewall and I am on a wired connection.I still get this error shortly after logging in and then it keeps happening 2-5 times per hour.

Can i get help with this? Bought the game recently and managed to get to level 50 but participating in long and needed dungeons and raids is becoming difficult as I keep getting this error during boss fights.

I should also mention that I do not have any lag whatsoever when this error happens and I do not have this problem with any other online games or MMO's.

[NjordAkhabali]

Don't worry, I've been getting this for the past 2 months. Final Fantasy support says "It's your ISP's fault!" ISP says "It's the game's fault!"
I'm never going to get a straight answer, so I just have to deal with constantly dc'ing every hour or so.

[Raist]

Most likely an issue at the exchanges between the ISP's that have to work together to get you to Ormuco (SE's ISP). There are known issues concerning routing in general for North America. Much of it has been at the heart of the Net Neutrality debate. Level3 and TATA have been pushing for the FCC to step up their game in the US for years now...but the ISP's just don't want to upgrade their exchanges--even when someone else has even offered to pony up the $$ for the hardware. Level3 not only offered to buy some of the $10,000 port cards for one ISP, but also to install and wire them up...and they STILL refused to upgrade.

Hard to say for certain without some tracert's to look at...but it should be pretty easy to spot if you run them (that link is to an article from Blizzard about it). Getting those reports to your ISP's Tier3 support should help get the ball rolling to clean up the routes a bit. You usually fair better going after them over the web than the phone, so if they have a support portal or twitter/facebook accounts you may get more active support there. You can check the downdetector site to see if they track your ISP--if they do, they usually have links to online support options you can try.

Alternatively, you can try using a VPN/Proxy to route yourself through different regions to see if you can get a cleaner path. Note they don't always pick the best route when they auto-configure--most will have a way for you to pick different locations for your tunnel. I found with some I tested last year that I did a bit better sometimes exiting here in the US rather than exiting in Montreal. IF you do try a VPN and it clears things up for you--you NEED to get in touch with your ISP, as that is pretty much proof positive your ISP has issues with the route(s) they are assigning you.

[NocX7]

Another patch and the problem still persists.I still get the 90002 error every 20-30 minutes.I love this game so far but no other MMO has this problem for me.

I pay for access to this game and that is getting blocked by this error happening so frequently.Can someone from SE finally say something on this matter and not just silently collect data on their 18 page sticky thread that has helped nobody so far?

[Raist]

Not much they can say really. If the problem is with Level3, TATA, Cogent, TiNet, or Verizon--SE doesn't have any dealings with them. That is your ISP negotiating with them for routing to Ormuco.

Need to get your route(s) specifically to the FFXIV servers looked at. Just for an example, here is a trace to the server I am currently signed into for Midgard:

C:\Windows\System32>tracert 199.91.189.31

Tracing route to 199.91.189.31 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    33 ms    29 ms    25 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    28 ms    32 ms    29 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    15 ms    15 ms    14 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    25 ms    28 ms    27 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    29 ms    32 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    33 ms    31 ms    33 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    35 ms    33 ms    45 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    55 ms    54 ms    60 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    61 ms    58 ms    55 ms  64.86.85.1
 11    71 ms    68 ms    73 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    78 ms    77 ms    78 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    75 ms    71 ms    73 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    64 ms    63 ms    60 ms  66.198.96.50
 15    55 ms    56 ms    66 ms  192.34.76.2
 16    65 ms    70 ms    71 ms  199.91.189.234
 17    72 ms    73 ms    69 ms  199.91.189.31

Trace complete.

My ISP is directly responsivle for hops 2-8, when I get handed of to one of their routing partners (in this case, TATA). Then TATA takes over to get me to their exchange at hop 14 that puts me on Ormuco (SE's ISP). From there, SE has direct influence for resolving issues.

Prior to that 15th hop--my ISP is the best candidate for resolving any issues along my route. If it is between 2-8, they can address it directly, as it is on their network. If it is between 8 and 15, it is an issue for their routing partner--they can either work with TATA to get it resolved, or they can alter my route to use a different routing partner--there are 4 more that peer directly with Ormuco, and TWC has arrangements with at least two of them because I've been put on them repeatedly when I have problems.

***I should note here that I frequently get changed amongst TATA, Cogent, and Level3 because we have been tracking issues tied into these third party ISP's they are using to get me to Ormuco. It changes up about every 3 weeks on average, but sometimes it may change twice in one week, depending on how bad we see things get. My ISP is making these changes and not SE, as I have been in contact with TWC-SC's Tier3 techs in the past and they have been monitoring things more closely since.

We see the culprit being issues between these third party exchanges the vast majority of the time. So you really should get your route(s) looked at.

[szarina]

Yes it is a UPNP

[szarina]

I have not had this problem until I reformatted my PC. I am on{GULP} Comcast in New Jersey . Since I formatted my PC I get the 90002 error . My husband who sits right next to me and is on the same ISP Has NEVER gotten this error . SOOOO what the heck is going on . Is it as the other posters say ? or is it a setting in windows 7 ? I called FF14 yes all my ports are open . Yes, it is on the allow list yes, yes, yes, to all the questions that were asked . I have a good PC I do not ever lag. I just get this error at least once a day if not more. No warning just 90002 .
It is sooo frustrating to be healing a dungeon and BOOM 90002 !!!! I did buy the expansion and I really want to play this game but sheesh ... I am rethinking my decision.
I have played in the past GW1, GW2, perfect word, forsaken world, WOW, Everquest , Everquest 2, DAOC, pretty much every MMO you can name and NEVER EVER got booted like FF14's 90002 errors
FF needs to at least let us log back in without waiting for the you are still logged in message to disappear

[Raist]

Szarina, just to rule it out, do you know if your router is using UPNP? This has been known to cause random session drops for games in the past. Many routers have on by default.

There should be no need for port forwarding of any kind for this game under normal setups. That is more a mechanic to allow unsolicited inbound connections and not for communication across an established outbound session. A router's native NAT should manage things just fine (though some may have SecureNAT options you might want to try toggling).

[NocX7]

Bought the game,pre ordered the collector's edition of the expansion and now I can't play in peace.
I called my ISP and they refuse (or they don't know what I'm talking about) to put me in contact with higher level techs.They insist that if the internet is fine and only this game disconnects then its not their fault to fix.I even paid for WTFast to try to get around the problem but then I still get either the 90002 or 90003 error.

This is exactly what I expected to happen.And i bet if i call SE,they'll just blame my ISP.

Someone answer me this...Why make a sticky thread on collecting data on the 90k problems if SE cant do anything about it and won't even say anything on the matter?To make it look like they're doing something?

IF this doesn't get resolved soon I'm might try to get my money back.I pay for access and I'm not getting access.

[Raist]

Bought the game,pre ordered the collector's edition of the expansion and now I can't play in peace.
I called my ISP and they refuse (or they don't know what I'm talking about) to put me in contact with higher level techs.They insist that if the internet is fine and only this game disconnects then its not their fault to fix.I even paid for WTFast to try to get around the problem but then I still get either the 90002 or 90003 error.

This is exactly what I expected to happen.And i bet if i call SE,they'll just blame my ISP.

Someone answer me this...Why make a sticky thread on collecting data on the 90k problems if SE cant do anything about it and won't even say anything on the matter?To make it look like they're doing something?

IF this doesn't get resolved soon I'm might try to get my money back.I pay for access and I'm not getting access.

well... have you looked at your route to see if perhaps there is an issue along the way? It is a very common thing for people to find issues between their ISP and SE's, and once you can confirm this it makes it much easier to get it addressed.

You say you tried a VPN. Did you use the automatic settings, or did you try picking a tunnel manually? Sometimes the auto config can still put you on a congested path. There are around a dozen or so corridors amongst 5 ISP's for the final leg into Ormuco. Thousands upon thousands of routes are all funneled into these limited access points, so you have roughly a 1 in 10 chance (or worse) of hitting a bad one during primetime when congestion is peaking out (some ISP's have only 3 routes, so if you stick with the same partner, you have a 1 in 3 chance of failure).

That is the real beauty of a VPN service. If it connects you to Montreal and it craps out, you can try maybe Toronto or somewhere in the US to see if it gets you routed through a cleaner path. That is basically the point of using a VPN--to bypass congestion, be that by encrypting data and getting past traffic shaping or directly changing your path.