My wife and I both play FFXIV, each on our own laptops. I've been using the same system for several years now with almost no problems. My wife had been having issues with her system due to the graphics card being not-so-good, and she would quite routinely be dropped from the game, especially in dungeons. A few days ago I replaced her laptop with a brand new one ... And now the game is entirely unplayable for her.
I've seen quite a few posts about random disconnects with a 90k error, and most point (incorrectly) to a router issue, or a server issue, or a network configuration issue ... However, none of this makes sense. My laptop almost never disconnects.
I removed all forms of AV, updated her drivers, even completely redownloaded and reinstalled FFXIV, but nothing is helping. However, I did some testing today and found something odd. I had a ping test to Sargatanas running in the background. Outside of the odd lag here and there, every single time I switched from the command prompt to the FFXIV window, the ping stream would time out, and then resume when I went back to the command window.
I'm convinced 100% this is a client issue, rather than a pure network issue. Any ideas?
Here's a snip from one of the packet traces. Every single time-out aligns with me switching windows.
Quote:
Pinging 204.2.229.91 with 32 bytes of data:
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=131ms TTL=51
Reply from 204.2.229.91: bytes=32 time=99ms TTL=51
Reply from 204.2.229.91: bytes=32 time=388ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=222ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1213ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=97ms TTL=51
Reply from 204.2.229.91: bytes=32 time=149ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=3422ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1067ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=112ms TTL=51
Reply from 204.2.229.91: bytes=32 time=115ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=121ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=2688ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=1267ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1282ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=107ms TTL=51
Reply from 204.2.229.91: bytes=32 time=1723ms TTL=51
Reply from 204.2.229.91: bytes=32 time=97ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=2314ms TTL=51
Reply from 204.2.229.91: bytes=32 time=99ms TTL=51
Continue reading...
I've seen quite a few posts about random disconnects with a 90k error, and most point (incorrectly) to a router issue, or a server issue, or a network configuration issue ... However, none of this makes sense. My laptop almost never disconnects.
I removed all forms of AV, updated her drivers, even completely redownloaded and reinstalled FFXIV, but nothing is helping. However, I did some testing today and found something odd. I had a ping test to Sargatanas running in the background. Outside of the odd lag here and there, every single time I switched from the command prompt to the FFXIV window, the ping stream would time out, and then resume when I went back to the command window.
I'm convinced 100% this is a client issue, rather than a pure network issue. Any ideas?
Here's a snip from one of the packet traces. Every single time-out aligns with me switching windows.
Quote:
Pinging 204.2.229.91 with 32 bytes of data:
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=131ms TTL=51
Reply from 204.2.229.91: bytes=32 time=99ms TTL=51
Reply from 204.2.229.91: bytes=32 time=388ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=222ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1213ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=97ms TTL=51
Reply from 204.2.229.91: bytes=32 time=149ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=3422ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1067ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=95ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=112ms TTL=51
Reply from 204.2.229.91: bytes=32 time=115ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=121ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=100ms TTL=51
Reply from 204.2.229.91: bytes=32 time=2688ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=93ms TTL=51
Reply from 204.2.229.91: bytes=32 time=1267ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=1282ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=107ms TTL=51
Reply from 204.2.229.91: bytes=32 time=1723ms TTL=51
Reply from 204.2.229.91: bytes=32 time=97ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Reply from 204.2.229.91: bytes=32 time=94ms TTL=51
Reply from 204.2.229.91: bytes=32 time=96ms TTL=51
Request timed out.
Reply from 204.2.229.91: bytes=32 time=2314ms TTL=51
Reply from 204.2.229.91: bytes=32 time=99ms TTL=51
Continue reading...