Yet another 90006 thread.

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.

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!

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.

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.

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?

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!

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.

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?

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

Thank you for the reply ZoratG.

Do you have any characters on the Chaos Data Center? Do you have any issues with that Data Center? It may be that any issues you have are exacerbated by being further away from the Data Center (The PS4 version will direct you through a different route as it connects to the PSN first).

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

I don't have a character on that Data Center. Due to how random this happens, sometimes within 5 minutes, other times it can take four or more hours. It's a little hard to test for sure, but I can make a character and try it. In the mean time, I did another Trace Route on the Chaos Data Center, and the results are as followed.



C:\Users\zoratG>tracert 195.82.50.9

Tracing route to 195.82.50.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 19 ms 19 ms 19 ms host-78-151-229-196.as13285.net [78.151.229.196]

5 26 ms 24 ms 26 ms host-78-144-9-37.as13285.net [78.144.9.37]
6 * * * Request timed out.
7 35 ms 36 ms 36 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
8 35 ms 35 ms 36 ms 212.162.4.98
9 35 ms 49 ms 42 ms 195.82.60.29
10 35 ms 35 ms 40 ms 195.82.61.14
11 36 ms 40 ms 36 ms 195.82.50.234
12 35 ms 35 ms 35 ms 195.82.50.9

Trace complete.

Edit: I made a character on the Chaos Data Center, Omega server, just to test it out. Within 30 minutes I was given error 90006 again, just like on the Aether Data Center. I'm honestly not sure what I could do to fix this at this point.

Thank you for the update ZoratG.

It would seem that your issue doesn't come from a routing problem then if you have the same issue with the Chaos Data Center. Is it possible to bring your PC to another location (and another internet connection) and try to connect that way? This will help determine whether it's your PC or the connection itself (you can also use another PC on your same connection to test this as well).

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

I'm currently testing it using another internet connection, on the same PC. With it I did another Trace Route. Results below.


C:\Users\zoratG>tracert 204.2.229.9

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 2 ms 1 ms 2 ms 192.168.42.129
2 * * * Request timed out.
3 51 ms 37 ms 47 ms 172.16.214.1
4 46 ms 47 ms 45 ms 172.16.214.10
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 77 ms 57 ms 56 ms 87-194-4-241.bethere.co.uk [87.194.4.241]
14 50 ms 53 ms 49 ms 84.16.6.190
15 64 ms 48 ms 58 ms 84.16.6.189
16 51 ms 50 ms 49 ms 5.53.3.64
17 60 ms 56 ms 51 ms 5.53.3.20
18 101 ms 68 ms 66 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
19 66 ms 66 ms 68 ms ae-8.r25.amstnl02.nl.bb.gin.ntt.net [129.250.3.229]
20 141 ms 128 ms 134 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
21 408 ms 205 ms 196 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
22 200 ms 209 ms 270 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
23 205 ms 198 ms 219 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
24 205 ms 206 ms 206 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
25 264 ms 243 ms 211 ms 204.2.229.234
26 229 ms 209 ms 193 ms 204.2.229.9

Trace complete.

I will update this with results on how the game preforms.

Edit: After using the other connection for a few hours, I got error 90002 a few times, but I think that was due to actual disconnecting as I lagged a little before hand. Then after logging in I got error 90006 again just a few minutes after. I'm currently downloading the game on another device, to see if I get the same issues on that one while connecting to my original source.
Edit 2: The second system I tried to run the game on was unable to load the game, likely due to lack of power. Short of this I can't really test it on another system.

Thank you for the update ZoratG.

This most recent trace route is from a different connection than your normal one, correct? What kind of connection is it?

A lot of your requests are timing out, but I'm not sure whether this is a connection issue with those pieces of equipment or if they are designed to not reply to ping requests. Regardless, you have some high response times pretty early in your route. This will make connecting to another continent a lot more difficult.

Have you contacted your ISP about this?

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

It was a connection used by tethering my phone with 4G, the only other means of a connection I have available at me. As for my ISP Final Fantasy is the only game I have issue with like this, so I never felt the need to. I've played a few different MMOs also playing on NA servers and never get an issue like this. Though at this point I'll try just about anything to fix it within my means.

For what it's worth, I did a test using Ping Plotter, and these were the results, this was using my usual connection.

Target Name: 204.2.229.9
IP: 204.2.229.9
Date/Time: 11/09/2018 02:24:20 - 11/09/2018 02:34:20

Hop Sent PL% Min Max Avg Host Name / [IP]
1 48 8 0.44 4.77 1.20 192.168.1.1 [192.168.1.1]
2 47 100 0 0 0 [-]
3 48 0 19.00 26.56 20.26 host-78-151-229-201.as13285.net [78.151.229.201]
4 48 0 19.00 29.69 20.34 host-78-151-229-200.as13285.net [78.151.229.200]
5 48 0 26.00 67.27 28.95 host-78-144-9-43.as13285.net [78.144.9.43]
6 48 0 25.00 31.23 26.62 81.25.207.217 [81.25.207.217]
7 48 0 25.74 36.55 27.62 ae-0.r24.londen12.uk.bb.gin.ntt.net [129.250.4.140]
8 48 0 97.00 113.76 99.69 ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
9 48 19 160.71 169.03 162.79 ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
10 48 10 160.00 171.05 162.19 ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
11 48 0 174.00 184.95 176.12 ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 48 0 178.00 181.89 179.37 ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 48 0 178.00 185.22 179.42 ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 48 0 178.00 190.22 179.88 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 48 0 178.00 183.20 179.46 204.2.229.234 [204.2.229.234]
16 48 0 178.00 182.83 179.14 204.2.229.9 [204.2.229.9]

Even though I can't run the game itself on my laptop. I decided to run a trace route on it just to see

Laptop is on windows 10 and uses a wifi connection

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 92 ms 100 ms 100 ms host-78-151-229-201.as13285.net [78.151.229.201]
4 45 ms 46 ms 45 ms host-78-151-229-200.as13285.net [78.151.229.200]
5 51 ms 38 ms 38 ms host-78-144-9-43.as13285.net [78.144.9.43]
6 30 ms 30 ms 32 ms 81.25.207.217
7 48 ms 26 ms 28 ms ae-0.r24.londen12.uk.bb.gin.ntt.net [129.250.4.140]
8 121 ms 124 ms 101 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
9 * * 161 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
10 167 ms * 168 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
11 186 ms 187 ms 191 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 195 ms 197 ms 200 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 211 ms 187 ms 193 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 206 ms 207 ms 209 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 202 ms 204 ms 206 ms 204.2.229.234
16 301 ms 202 ms 192 ms 204.2.229.9

Trace complete.

Oof that trace shows a heavy dose of lag. At about 150 Ms of degredation you start to see a decline in game quality. At 200 and better 90ks become more likely the higher you go. Makes sense that you are running in to them.

So I have talked to my ISP, and they have done multiple checks, even had someone come out and check my line directly. No problems on their end, I was told to open my port fully by the the person who came out. To the point everything would have access using port 80. I did this and still got the same error. I also ordered a new Ethernet cable, just on the off chance mine is somehow causing this issue, but short of that I don't know what else I could possibly do.

Having now tried a new ethernet cable, and still getting error 90006. I have tried tracert, and PingPlotter. Both are showing packet loss at hop 9, with the IP 129.250.4.13. If there is something on my end I can do to fix this, by all means please tell me and I'll get right on it, but as of now I really can't see what else I can do to fix the problem I'm having.

This problem is really killing my experience in the game, while it is only every few hours. It means I'm unable to raid in case it goes off at a crucial moment. I'm basically being locked out of half the content for a problem outside of my control.

This sounds alarmingly similar to the problems I've been having for a while. 90006 error, completely random disconnects - sometimes every few minutes, sometimes every hour, or every few hours. Some days will be almost completely fine, others will be completely unusable, some will be in the middle. It's incredibly frustrating, since yeah, it does make it a gamble trying to do anything in a group, since you can lag out at any moment.

I've tried most of the things you have (also coming from Europe, though mainly to the Chaos datacenter), and... yeah, I really hope there's some solution out there that we're missing.