Really... Frontier.ffiV.com/arr_win/ error again?

[TheSmoo]

Same.

I tried a CMD window, and ipconfig /flushdns - nothing.
Then ipconfig /release and then /renew, and it ran. I rebooted just to be sure.

Same issue again.

Then retried, and it SLOWLY logged in and started updating. So... yeah, just keep trying? This is silly.

[escorpion]

Finally someone helpful said that this error is caused by congestion, I was able to login again, don't go deleting your stuff because it will not help, just keep waiting until the stuff loads and keep on trying.

[Syrellaris]

It is just ridiculous on how often this error has plagued me and probably others since patch 2.2 is out. I do not think it is a congestion problem, it is most likely an error on there server end when it comes to the launcher. A few days earlier I got a License issue with the game on the launcher, which may be related to it. Them being late in updating there licenses?

But the chat support solutions are just hilarious, calling my ISP? like really?

[Raist]

welll.. have you tried maybe running some traces to frontier.ffxiv.com just to see if you indeed are experiencing signs of congestion along your route to the server, just to rule it out?

It HAS been a problem in the past, and congestion still plagues a lot of players... and it often has been found to NOT be within the scope of SE to address but your ISP, as it typically falls on their segments or on segments managed by their routing partners (people your ISP has contracts with for carrying your data to Ormuco, who is SE's ISP in Canada, or the network in Japan that is managed by their government). So... yes, in fact this COULD be something your ISP may need to investigate, depending on just what is actually going on with your specific connection. The same issues can be affecting your route to the actual game servers as well as other services.. so if you find something suspicious, test against some other popular services like Google/YouTube, Netflix, TwitchTV, etc. to see if a pattern exists elsewhere--and forward the details to your ISP's Tier3 support (not the Tier1's that answer the phones... you need specifically Tier3 techs, as they are the ones that know what to look for).

And I am speaking from experience here and not just speculating, as TWC's Tier3 and 4 techs have in fact been working with Level3, TATA, and Cogentco (the partners that finally cleaned things up) on resolving such issues along my routing and has fixed them all except for a problem with an overloaded headend for my city that <hopefully> will be addressed with planned upgrades. They very well may be able to help you IF you in fact find signs of high congestion affecting your route (highly erratic response times/timeouts that may result in elevated packet loss and retransmits)

Tracing route to frontier.ffxiv.com [124.150.157.190]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2   681 ms  3120 ms     *     cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    12 ms    13 ms    12 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    23 ms    26 ms    23 ms  xe-6-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.66]
  5    32 ms    30 ms    32 ms  107.14.19.20
  6    89 ms    90 ms    90 ms  107.14.17.179
  7    88 ms    91 ms    91 ms  ae-4-0.cr0.lax30.tbone.rr.com [66.109.6.2]
  8    88 ms    89 ms    88 ms  ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
  9    91 ms   206 ms   147 ms  unk-426d075a.adelphiacom.net [66.109.7.90]
 10    86 ms    85 ms    86 ms  lajbb002.kddnet.ad.jp [59.128.2.177]
 11   227 ms   194 ms   195 ms  otejbb206.int-gw.kddi.ne.jp [203.181.100.45]
 12   219 ms   202 ms   201 ms  jc-ote301.int-gw.kddi.ne.jp [118.155.197.42]
 13   202 ms   203 ms   204 ms  106.187.28.198
 14   209 ms   209 ms   231 ms  61.195.56.133
 15   200 ms   201 ms   200 ms  219.117.144.74
 16   204 ms   201 ms   202 ms  219.117.144.45
 17   194 ms   196 ms   198 ms  219.117.144.29
 18   201 ms   203 ms   203 ms  219.117.147.186
 19   194 ms   195 ms   195 ms  124.150.157.190

Trace complete.

Now.. can you spot where my connection may be running into trouble on it's path to the server in Japan? Two spots.... my residential gateway under the care of TWC/RR, and another one further down the line in San Diego, CA and managed by Adelphia out of Australia. Neither SE, Ormuco, nor the JP government office that manages the internet there (forget what they call themselves now.. separated from JP-NIC a while back) is responsible for either of those segments.

And to further illustrate the point, here is my new route to my game server (just noticed they switched me up again... now using TATA, was on Cogentco last week):

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   234 ms    30 ms  2129 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    12 ms    14 ms    11 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    24 ms    26 ms    26 ms  24.93.64.128
  5    29 ms    30 ms    36 ms  107.14.19.42
  6    30 ms    30 ms    32 ms  ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
  7    29 ms    31 ms    30 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  8    54 ms    52 ms    52 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
  9    51 ms    53 ms    53 ms  64.86.85.1
 10    52 ms    54 ms    52 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 11    51 ms    52 ms    57 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 12    52 ms    52 ms    54 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 13    51 ms    53 ms    52 ms  66.198.96.50
 14    50 ms    54 ms    52 ms  192.34.76.2
 15    51 ms    54 ms    53 ms  199.91.189.234
 16    54 ms    52 ms    53 ms  199.91.189.31

Trace complete.

Note that these traces are coming from Florence, SC... so that latency to Canada is pretty good for the distance I am covering, as well as to Japan. The problems are not at those endpoints for me, as exhibited in these traces.

Once again, my issues are bound to my first gateway on the TWC/RR network. Once I start seeing the spikes like that at that one hop, I start experiencing lag spikes in game. When it is behaving and staying lower (below 100ms), the game runs smoothly. This is an issue I've been in contact with Tier3 support over... it's basically bound to them using a barely even DOCSIS 2.0 compliant CMTS with only 6 channels, while trying to push out DOCSIS 3.0 connections that really need 8 or more channels to run efficiently. Oversold markets, under-maintained networks. Just can't seem to get them to own up to it... they just keep changing my route up every time I send them a new data dump every couple of weeks on the matter. But, at least they do something that sometimes makes things better for a while, but it eventually goes south again as everyone gets shifted around again and starts clogging the pipes again.

The point is.. there are known and well documented cases where the ISP's have mismanaged their networks for years... I'm talking at least to the days of Diablo (the original) and Freespace (that's when I first started working on issues like this). So, it is not so unreasonable for them to ask us to be in contact with our ISP... it's just that it isn't explained as to why you need to, nor how to properly get them involved. Submitting tracerts to Tier3 support that exhibit potential signs of elevated congestion and packet loss is what you need... and usually gets the ball rolling.