Another thread about NTT America's 204.2.229.234 address causing issues

**rowbear31** · 08-15-2019 05:38 AM

So, after over a month straight of getting 90002 errors and poor routing causing my internet to completely crash, and more than 10 different fix attempts, I want to make tech support aware that the IP 204.2.229.234, which, from what I've seen, is tied to NTT America, is still a culprit of packet loss and disconnects in the NA servers.

Ran this tracert right after the DC (after my internet was able to reconnect):

Tracert:
Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RAC2V1S [192.168.1.1]
2 13 ms 10 ms 9 ms 142.254.237.25
3 31 ms 23 ms 33 ms agg61.mnvyca4302h.socal.rr.com [76.167.26.245]
4 17 ms 14 ms 15 ms 72.129.7.36
5 16 ms 22 ms 23 ms agg21.tustcaft01r.socal.rr.com [72.129.5.2]
6 17 ms 22 ms 15 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
7 18 ms 20 ms 17 ms 66.109.5.247
8 18 ms 21 ms 16 ms las-b24-link.telia.net [62.115.156.224]
9 59 ms 19 ms 17 ms ntt-ic-326358-las-b24.c.telia.net [213.248.103.171]
10 18 ms 16 ms 16 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
11 28 ms 29 ms 29 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
12 31 ms 32 ms 40 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 29 ms 29 ms 33 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 34 ms 36 ms 32 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 29 ms * 30 ms 204.2.229.234
16 33 ms 33 ms 32 ms 204.2.229.10

Trace complete.

I plan to call my ISP to see if they can assist with this, but this is really a persistent issue SE needs to address (there are threads from several years ago for this same issue).

I have allowed ALL FFXIV applications and executables through my firewall, I have all virus/malware protection turned off. I have reinstalled the game, run it in compatibility mode for Win7 (running on Win10), cleared my IE cache, lowered IE security settings, got a new router, set UPNP to 0 AND 1 in the config file, ensured all UPNP settings on my router were on, and then attempted port forwarding (which I couldn't leave active because my wife plays the game as well. She experiences the same disconnect issues).

Can someone please report this to SE as yet another instance of NTT America's 204.2.229.234 address losing packets and causing the game to crash (as well as my internet)?

Thanks for any assistance you can provide; this is extremely frustrating for a subscription game (especially one which isn't having trouble making money at the moment), when all other games and applications on my PC work with no issue.

**EDIT** After contacting my ISP, they cannot do anything to assist with the routing, as NTT America's address is outside their network (I expected this to be their answer based on other people's experiences).

**rowbear31** · 08-15-2019 06:04 AM

Another tracert shows another NTT IP address (129.250.3.237) losing packets:

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RAC2V1S [192.168.1.1]
2 11 ms 8 ms 10 ms 142.254.237.25
3 28 ms 26 ms 36 ms agg61.mnvyca4302h.socal.rr.com [76.167.26.245]
4 20 ms 18 ms 17 ms 72.129.7.36
5 21 ms 22 ms 21 ms agg21.tustcaft01r.socal.rr.com [72.129.5.2]
6 22 ms 29 ms 22 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
7 17 ms 17 ms 17 ms 66.109.5.247
8 19 ms 17 ms 24 ms las-b24-link.telia.net [62.115.156.224]
9 18 ms 19 ms 17 ms ntt-ic-326358-las-b24.c.telia.net [213.248.103.171]
10 19 ms * 15 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
11 31 ms 35 ms 31 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
12 81 ms 43 ms 54 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 30 ms 29 ms 31 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 36 ms 31 ms 35 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 30 ms 35 ms 31 ms 204.2.229.234
16 138 ms 34 ms 32 ms 204.2.229.10

Trace complete.

**rowbear31** · 08-15-2019 07:36 AM

Another traceroute, same 204.2.229.234 packet loss. These are all done at different times of the day.

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RAC2V1S [192.168.1.1]
2 64 ms 23 ms 10 ms 142.254.237.25
3 54 ms 24 ms 33 ms agg61.mnvyca4302h.socal.rr.com [76.167.26.245]
4 17 ms 14 ms 19 ms 72.129.7.36
5 137 ms 21 ms 22 ms agg21.tustcaft01r.socal.rr.com [72.129.5.2]
6 17 ms 31 ms 22 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
7 19 ms 17 ms 27 ms 66.109.5.247
8 26 ms 58 ms 33 ms las-b24-link.telia.net [62.115.156.224]
9 16 ms 17 ms 17 ms ntt-ic-326358-las-b24.c.telia.net [213.248.103.171]
10 18 ms 14 ms 15 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
11 38 ms 26 ms 29 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
12 31 ms 34 ms 30 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 32 ms 30 ms 31 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 41 ms 34 ms 41 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 39 ms 32 ms * 204.2.229.234
16 33 ms 36 ms 37 ms 204.2.229.10

Trace complete.

**rowbear31** · 08-15-2019 08:20 AM

Another traceroute, won't even get through 204.2.229.234. Packet loss is so bad that it's been sitting on that IP for almost 10 minutes.

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RAC2V1S [192.168.1.1]
2 12 ms 21 ms 13 ms 142.254.237.25
3 108 ms 31 ms 30 ms agg61.mnvyca4302h.socal.rr.com [76.167.26.245]
4 14 ms 18 ms 17 ms 72.129.7.36
5 21 ms 21 ms 23 ms agg21.tustcaft01r.socal.rr.com [72.129.5.2]
6 17 ms 21 ms 30 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
7 18 ms 27 ms 34 ms 66.109.5.247
8 16 ms 17 ms 16 ms las-b24-link.telia.net [62.115.156.224]
9 15 ms 17 ms 18 ms ntt-ic-326358-las-b24.c.telia.net [213.248.103.171]
10 15 ms 19 ms 16 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
11 26 ms 31 ms 32 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
12 32 ms 36 ms 32 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 32 ms 30 ms 30 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 33 ms 32 ms 34 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * 32 ms *

**hynaku** · 08-15-2019 09:04 AM

Wish they go with another server provider than NTT America. Ever since they went them ones has been disconnecting all the time and not on our ends that causes them.

**Dynratygus** · 08-15-2019 09:17 AM

Good afternoon and thank you for posting in the Final Fantasy XIV Technical Support Forums.

We apologize for any inconvenience that has occurred. The information provided, will be collected and sent the appropriate party. To further assist with the issue, we would need more information. A ticket has been sent to the email associated with the SQUARE ENIX ID. Please respond with the requested information.

This thread will be moved to ' Support Center Ticket Created"

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

Thread: Another thread about NTT America's 204.2.229.234 address causing issues

Thread Tools

Search Thread

Display

Another thread about NTT America's 204.2.229.234 address causing issues