Yet another 90006 thread.

[ZoratG]

As it says, I'm making this because I keep getting error 90006 every three to four hours. I play on PC with windows 7, 64bit, with a wired connection. The last time this happened was 5 minutes ago as of posting this, and the time before that 2 hours ago from posting this. This has been happening since I got the game in December. I play on the Balmung Server in NA, however I am from the UK. But as it says below, I have 0 issues on PS4, so my region I don't believe plays a factor.

For what it's worth, I also have the game on PS4 and have 0 issues with this on there, this is a PC only problem.

I have already tried the copy paste "Fix" with the changing settings, and port forwarding, neither of them helped. I'm basically asking if someone can help me trace exactly where this problem is starting, to see if I can do something to fix it.

[Einmimiria]

Good morning and thank you for posting on the Final Fantasy XIV Technical Support Forums.

If you are only having issues with your PC and not any other device, then there is something localized to that PC that is causing the issue.

You've tried changing the settings in the Internet Explorer web browser and port forwarding, but what else have you tried to resolve the issue?

How is your PC connected to the router? Using a wireless connection or an Ethernet cable?

Have you made an exception for the game in your anti-virus/firewall?

We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

[ZoratG]

I have changed the settings, as well as done the port forwarding which is suggested in other threads.

FFXIV is an exception to both my Anti Virus and Windows Firewall, and is always running as admin.

My PC is connected through an Ethernet cable, while my PS4 is wireless and still has 0 issues.

As for other methods, I've tried using VPNs, and other third party programs to reroute my connection. I've also tried doing a trace route, however I'm not a very tech savvy person, so allot of the results were lost on me.

[Eisig]

Going to weigh in on this thread as well as I've been experiencing horrible packet loss to both of the NA servers starting around 8pm PST, and generally running well after 10pm-midnight. Generally, the packet loss can be mitigated by hopping around various locations until I find a route that does not pass through the troubled link.

pathping 204.2.229.9

Tracing route to 204.2.229.9 over a maximum of 30 hops

0 [192.168.1.X]
1 192.168.1.1
2 10.97.200.1
3 100.127.78.148
4 204.2.229.9

Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.1.X]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.97.200.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% 100.127.78.148
13/ 100 = 13% |
4 54ms 13/ 100 = 13% 0/ 100 = 0% 204.2.229.9

Trace complete.

In the above pathping, you can see that the packet loss(~13%) occurs on the link between 100.127.78.148 (NSlookup unsuccessful), and 204.2.229.9 (the Aether Data Center). Many ping tools will show the packet loss AT the data center itself, but this isn't the whole story. There is a bad, noisy or congested link leading to the data center.

Further detail:
Hop 0 - My PC to my Router
Hop 1 - My Router to my Modem
Hop 2 - My Modem to one of my ISP's nodes. (likely a localized trunk of some sort)
Hop 3 - My ISP node to 100.127.78.148 (This is a bogon IP range... likely a carrier grade NAT. See https://en.wikipedia.org/wiki/Reserved_IP_addresses for more details)
Hop 4 - 100.127.78.148 to Aether Data Center

There is some piece of hardware or cabling starting to go bad either in your data center, or suspiciously close to it.

Final note: This issue was pervasive around Oct/Nov of 2017 for me, and cleared up around Jan/Feb of 2018. I've had a few intermittent cases since, but this has been a sustained period of packet loss for myself and others. Please let me know if there is anything I can do to help your techs troubleshoot.

[ZoratG]

So after doing what you did in the post above, I got very different results. However, as I said I'm not a tech savvy person, so what happened with mine doesn't mean a great deal.


pathping 204.2.229.9

Tracing route to 204.2.229.9 over a maximum of 30 hops

0 zoratG-PC.lan [192.168.1.7]
1 192.168.1.1
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 zoratG-PC.lan [192.168.1.7]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

Trace complete


I'm not really sure why the second line only gives * * *, but it also does the same when I do tracert. If this is a problem on my end, any idea how I could go about fixing it?

[Einmimiria]

Thank you for the update ZoratG.

Based on your pathping, it looks like you are having trouble getting to the server (which falls in line with the issues you are having). The weird part is you can't seem to get past your own network equipment, which can't be the case because you are posting on the forum here. Did you cancel this pathping before it finished? Can you also post the trace route you did?

There may be some configuration with your router that may be giving issues for your computer but not your PS4 (The PS4 will connect to the PSN first, so they aren't taking the same route). Try resetting your router by turning it off then back on after a few minutes.

We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

[ZoratG]

This is the result I got from before turning resetting my router.

C:\Users\zoratG>tracert 204.2.229.9

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 19 ms 19 ms 19 ms host-78-151-229-201.as13285.net [78.151.229.201]

4 23 ms 19 ms 19 ms host-78-151-229-200.as13285.net [78.151.229.200]

5 26 ms 26 ms 26 ms host-78-144-9-43.as13285.net [78.144.9.43]

6 26 ms 27 ms 25 ms 81.25.207.217

7 27 ms 26 ms 26 ms ae-0.r24.londen12.uk.bb.gin.ntt.net [129.250.4.140]

8 92 ms 92 ms 92 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]

9 * 156 ms 156 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]

10 156 ms 157 ms 155 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]

11 174 ms 169 ms 169 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]

12 172 ms 172 ms 173 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]

13 172 ms 172 ms 172 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]

14 173 ms 172 ms 172 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]

15 172 ms 172 ms 172 ms 204.2.229.234

16 172 ms 172 ms 172 ms 204.2.229.9

Trace complete.

Then after resetting my router, I did both tests again and got the same results as above. I've also tried resetting my route a number of times, and master resetting it, but the 90006 errors still happen at the same frequency.

[Eisig]

Zorat,

What do your results look like if you run a pathping or tracert to common providers like google.com or akamai.com? (akamai is a content delivery network and cloud services provider on the east coast that I use as a baseline)

If you get the same request timeout, your ISP may be running that piece of equipment in 'stealth mode'(for lack of a better term) where it doesn't reply to pings, but forwards your data along the path none the less. (For reference, pings are commonly ICMP on windows, and UDP on Linux systems)

Unfortunately, pathping will frequently fail out past a node that doesn't respond to ICMP (ping) packets.

PingPlotter has a free version that could give you some decent results if you want to keep checking for packet loss. Be sure to set the interval to '1 Second' as less may be blocked by your ISP detecting a DDoS attack, and more may not catch the specific packetloss.

By any chance, are you by chance playing off of a university or metered network?

[ZoratG]

This is what I got running it to google, so I think you may be right about it being stealth mode.

C:\Users\zoratG>pathping google.com

Tracing route to google.com [172.217.7.14]
over a maximum of 30 hops:
0 zoratG-PC.lan [192.168.1.7]
1 192.168.1.1
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 zoratG-PC.lan [192.168.1.7]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

Trace complete.

I run from a simple home private network through my provider, like any average home would have. I'm also the only one using it. Not sure if that's a help at all, but I figured I would mention it