2002 error: Primal cluster + Suddenlink

[Alyx]

SE:

Please help with the 2002 error and the ISP, Suddenlink. I cannot log into the Primal server cluster, I receive a 2002 error and program shutdown.

When I change to the Elemental cluster and log into Atomos, there are no problems at all.

I have changed clusters several times.

All the necessary ports are open on my router.
I have flushed my DNS on Windows.
I have rebooted my PC.

This is a SE problem. Please fix!!!!!

[MatildaMari]

Months of playing without a single problem, didn't change a single setting and suddenly i was disconnected from the game and i can't get back in, get error 2002 followed by a game shutdown.

Moogle here.

[Alyx]

Seems to have cleared up, for now.

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=29ms TTL=55
Reply from 184.107.107.176: bytes=32 time=30ms TTL=55
Reply from 184.107.107.176: bytes=32 time=30ms TTL=55
Reply from 184.107.107.176: bytes=32 time=30ms TTL=55

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms

[Alyx]

I just pinged the 3 data center IP addresses. The EU and JP addresses work just fine, whereas the NA address pings and times out.

It's on SE's end.

NA:

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=69ms TTL=55
Request timed out.
Request timed out.
Reply from 184.107.107.176: bytes=32 time=53ms TTL=55

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 69ms, Average = 61ms

EU:
Pinging 209.130.141.243 with 32 bytes of data:
Reply from 209.130.141.243: bytes=32 time=91ms TTL=54
Reply from 209.130.141.243: bytes=32 time=91ms TTL=54
Reply from 209.130.141.243: bytes=32 time=91ms TTL=54
Reply from 209.130.141.243: bytes=32 time=91ms TTL=54

Ping statistics for 209.130.141.243:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 91ms, Average = 91ms

JP:
Pinging 202.67.53.202 with 32 bytes of data:
Reply from 202.67.53.202: bytes=32 time=193ms TTL=47
Reply from 202.67.53.202: bytes=32 time=183ms TTL=47
Reply from 202.67.53.202: bytes=32 time=193ms TTL=47
Reply from 202.67.53.202: bytes=32 time=193ms TTL=47

Ping statistics for 202.67.53.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 193ms, Average = 190ms

[Raist]

Those addresses aren't the game servers. Canadian servers start with 199 and the Japan ones start with 124.

The 184 address is a webserver run on a different company's network (i-web and not Ormuco) in a different section of Montreal. Think one of those others was a DNS server for SE and might have some bearing if the game looks up addresses directly, but not familiar enough with the coding to verify that.

If you don't know the addresses your client actually uses you would be better off using the lobby servers. Their address are registered in DNS with the naming scheme of neolobbyXX.ffxiv.com with XX being numbers 01 through 06. Even numbers are for Canada and odd are for Japan.