TCP RST packets from server-side when connecting from AT&T, not Verizon

[plasmacutter]

This is an odd one.

The server is sending Reset packets and killing my connection on AT&T Fiber only (west coast).

Examples:

5510 132.888042 204.2.229.102 192.168.1.68 TCP 60 55006 → 50557 [RST] Seq=22273 Win=0 Len=0
6745 507.896761 204.2.229.102 192.168.1.68 TCP 60 55006 → 63307 [RST] Seq=447114 Win=0 Len=0

If I swap connections by tethering through my Verizon mobile device things solidify instantly.

Were tolerances made a little too tight on square's side this patch? I have zero connection stability issues on any other games or net activity as a heavy user.

As it stands my home network is absolutely unplayable.

[Dynratygus]

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

Were any updates or changes made to the network settings at all? Additionally were you able to connect directly to the router?

Thank you for posting in the Final Fantasy XIV Technical Support Forums

[plasmacutter]

No changes to network for about a year.
What had been rock solid for 18 months suddenly went south on patch day.

I'm now disconnected via RST 2-4 times an hour (no lag or freeze.. i've been booted as I take damage in a normal dungeon)

I have since grabbed several more instances of this happening, including a full session pcap from login to RST disconnect if required for diagnostic work.

Latest example running absolutely nothing but FF after applying full connectivity support boilerplate:

15972 523.534874 204.2.229.102 192.168.1.68 TCP 286 55006 → 50083 [PSH, ACK] Seq=2341539 Ack=221873 Win=196736 Len=232
15973 523.541852 192.168.1.68 204.2.229.102 TCP 238 50083 → 55006 [PSH, ACK] Seq=221873 Ack=2341771 Win=262400 Len=184
15974 523.561173 204.2.229.102 192.168.1.68 TCP 190 55006 → 50083 [PSH, ACK] Seq=2341771 Ack=222057 Win=196736 Len=136
15975 523.602176 192.168.1.68 204.2.229.102 TCP 54 50083 → 55006 [ACK] Seq=222057 Ack=2341907 Win=262400 Len=0
15976 523.875019 192.168.1.68 204.2.229.102 TCP 238 50083 → 55006 [PSH, ACK] Seq=222057 Ack=2341907 Win=262400 Len=184
15977 523.896164 204.2.229.102 192.168.1.68 TCP 60 55006 → 50083 [RST] Seq=2341907 Win=0 Len=0
15978 523.900744 192.168.1.68 204.2.229.102 TCP 54 50084 → 55006 [FIN, ACK] Seq=11009 Ack=8770 Win=261376 Len=0

[Packetdancer]

Not Square-Enix support, but I'd be curious how similar/different the two traceroutes are. Intermediary devices are allowed to inject an RST packet as if it came from the destination when a connection 'needs' to be reset, after all; from the endpoints, it looks like the opposite side of the connection sent the RST. So if there's something along the route for AT&T that is throttling connections for some reason, it could likely show up as an RST from the server, while if Verizon doesn't pass through that same device it might not suffer the same issue.

I've seen it happen before, unfortunately. And in those cases, when it's something between Consumer A and Provider B that neither of them technically controls, the usual solution I've seen people go for is just to use a gaming VPN to route around the issue. :/

[plasmacutter]

Intermediary devices are allowed to inject an RST packet

This still requires square to help investigate to confirm one way or the other.

If I simply go to my ISP they'll point me right back to square to confirm their web service is not the one resetting me.

[Rhaervis]

Thank you for posting in the Final Fantasy XIV Technical Support Forums.

This thread will be moved to 'Closed Concerns.' If anyone is still having this particular problem, please create a new thread and we will assist you in any way we can.

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